Ad Widget

Collapse

Cannot Connect Device to Proxy

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • stevefxp
    Senior Member
    • Aug 2020
    • 168

    #1

    Cannot Connect Device to Proxy

    Hello all,

    I have a remote Linux server that I want to monitor passively. I have setup a Zabbix proxy on the remote side, so the proxy will only talk to my main Zabbix server. For some reason I cannot seem to get the Zabbix Server to Proxy to Linux Server working. If I reconfigure the Linux server, to go directly to the main Zabbix server I get a connection almost immediately. I do not understand what is not working. What I am seeing in the proxy logs are as follows:

    2024-04-09T19:40:28 32363 temporarily disabling Zabbix agent checks on host "app1test.rics.prod": interface unavailable
    2024-04-09T19:40:13 32363 Zabbix agent item "system.swap.size[,free]" on host "app1test.rics.prod" failed: another network error, wait for 15 seconds
    2024-04-09T19:39:58 32363 Zabbix agent item "vm.memory.size[pavailable]" on host "app1test.rics.prod" failed: another network error, wait for 15 seconds
    2024-04-09T19:39:43 30850 Zabbix agent item "vm.memory.size[available]" on host "app1test.rics.prod" failed: first network error, wait for 15 seconds

    I have validated that the proxy can connect to the Linux server via UDP port 10050. I can ping the FQDN of the Linux server from the proxy. I do not know what else to look into. I am running 6.4.13 at the server, proxy, and Linux agent.

    Thanks,
    Steve
  • stevefxp
    Senior Member
    • Aug 2020
    • 168

    #2
    OK a little bit more information, as I am continuing to tshoot this.

    Once I enable the proxy I get an error that I cannot agent.ping the device: Zabbix agent item "agent.ping" on host "app1test.rics.prod" failed: first network error, wait for 15 seconds

    Is this a standard ICMP ping, as I have tested this from the proxy and it resolves the FQDN? Is this a ping using the Zabbix port?

    Comment

    • stevefxp
      Senior Member
      • Aug 2020
      • 168

      #3
      Well it really helps to have the logs when you are going through this. I found that the agent on the Linux server could not accept the connection from its gateway, so I just added the gateway to the list of IP on the agent and voila it works! That is really strange that it needed the gateway!

      Now that I got passive working I wanted to see if I could get active working. So when I change everything to active its failing on the Zabbix server side with the following: cannot accept connection from proxy "RICS Proxy - Prod" at "10.11.0.1", allowed address: "10.0.3.1": connection is not allowed

      10.11.0.1 is my remote VPN address. Do I just added this to the ListenIPs on the Zabbix server?

      Comment

      • solution
        Senior Member
        • Jun 2020
        • 269

        #4
        When in Active Mode, define which IPs are allowed.
        Or leave it blank to accept from any source.
        Read more at:



        Wellington

        Comment

        • stevefxp
          Senior Member
          • Aug 2020
          • 168

          #5
          I have a new one...my proxy and agent are on the same system. On the proxy I am getting: cannot send list of active checks to "Y": host [X] not found. On the agent I am getting: no active checks on server [Y:10051]: host [X] not found. Since they are both on the same system I shouldnt have to worry about ports being open. Has anyone seen this? When I ran zabbix_get -s X -k agent.hostname I got the right fqdn back as defined in both the proxy and agent.

          Comment

          • cyber
            Senior Member
            Zabbix Certified SpecialistZabbix Certified Professional
            • Dec 2006
            • 4807

            #6
            Is your agent monitored by that proxy? Seems you configured agent to turn to proxy, but maybe forgot to configure it in Zabbix to be monitored by that proxy?

            Comment

            • stevefxp
              Senior Member
              • Aug 2020
              • 168

              #7
              Exactly what was happening...thanks!

              Comment

              Working...