Ad Widget

Collapse

How do I solve - zabbix_get conntection refused [111]?

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • frymor
    Junior Member
    • Mar 2021
    • 9

    #1

    How do I solve - zabbix_get conntection refused [111]?

    On an Ubuntu machine we installed the zabbix server monitor multiple ubuntu and windows machines.

    When I try to execute zabbix_get from the zabbix server to call for information from one of my machines I get he following error:

    Code:
    # zabbix_get -s 10.33.0.155 -p 10050 -k agent.ping
    zabbix_get [931258]: Get value error: cannot connect to [[10.33.0.155]:10050]: [111] Connection refused
    ​
    I have already disabled the firewall (ufw) and restarted the agent

    What Do I need to do next in order for the zabbix_get command to retrieve the information and be able to reach the machine I'm calling for?

    Thanks for the help

    Assa


    P.S.
    We're running zabbix 6.0.8 with agent 5.0.17 on ubuntu 22.0.4
  • yau
    Junior Member
    • Dec 2023
    • 16

    #2
    Another 2 cents:
    1. tcpdump tcp port 10050
    2. grep -r ^Server /etc/zabbix

    Comment

    • santosra02
      Junior Member
      • May 2023
      • 21

      #3

      Hi,

      1 - First check the zabbix agent status in the client machine, in Linux you can run the following command:

      # systemctl status zabbix-agent

      2 - In the client machine, check the status of 10050 tcp port ,it must be in Listen status, in Linux you can run the following command:

      # netstat -ntpl | grep zabbix

      2.1 - From the client machine try to connect the local tcp port 10050 and check if the connection is successfully established, in in Linux you can run the following command:

      $ telnet 127.0.0.1 10050


      If the above is everything OK, let's start the troubleshooting from the Zabbix Server side:

      1- In the Zabbix Server machine, try to connect the 10050 port in the client machine, in in Linux you can run the following command:

      $ ping -c 5 <client machine IP>

      $ telnet <client machine IP> 10050



      With the above output we can have a better idea where is the issue in your environment.

      Comment

      Working...