[ZBX-1061] Agents behind a proxy are shown as "unreachable" ('status' parameter works not as expected) Created: 2009 Sep 25  Updated: 2017 May 30  Resolved: 2012 Jun 18

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Proxy (P), Server (S)
Affects Version/s: 1.6.5
Fix Version/s: 1.8, 2.0.0

Type: Incident report Priority: Major
Reporter: Christoph Haas Assignee: Unassigned
Resolution: Fixed Votes: 2
Labels: proxy
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Debian GNU/Linux 5 ("Lenny")


 Description   

Usually the "status" item (as in "status.last(0)=...) is handled correctly if a system is monitored directly.

But a system behind a proxy is shown as "unreachable" all the time. A possible workaround is to change the trigger from

status.last(0)=2

to

agent.ping=0

I had rather expected that the 'status' parameter shows that a system is reachable - even when being located behind a proxy.

 Comments   
Comment by Christoph Haas [ 2009 Sep 30 ]

Regarding agent.ping:

Correction to my description above. It's supposed to be:

agent.ping.nodata(120)=1

In my opinion this is not the best solution because it will take at least 120 seconds before a system is detected as unvailable.
Please make agent.ping not only return 1 (success) or nothing (=nodata) but also 0 (failure). If the "TCP ping" to an agent fails then I would expect a proper response (e.g. "0").

  • * *

Regarding "status":

I understand that the "status" is calculated by the server depending on whether the server receives data. So it doesn't work through a proxy. (This was very confusing for me.)
Please (if possible) fix the calculation of "status" on the server so that it becomes 'unreachable' (2?) in case the proxy determins the system isn't available.

  • * *

My problem is that I'm not sure how to monitor systems for general availability correctly.

  • status.last(0)=2 does not work through a proxy
  • agent.ping.nodata(120)=1 is artificially delayed (although the proxy/server knows that the agent is unreachable)
  • icmpping.last(0)=1 would detect whether the system is down (possible workaround)
  • tcp,port[10050].last(0)=1 would detect whether the agent is listening (possible workaroung)
Comment by richlv [ 2010 Aug 13 ]

i believe host status is passed by proxies since 1.8 -> fixed

Comment by Stefan Sabolowitsch [ 2010 Oct 15 ]

i have exactly the same problem, as described here. V1.8.3
http://www.zabbix.com/forum/showthread.php?t=19592

Comment by Christoph Haas [ 2010 Oct 15 ]

See comment from Stefan Sabolowitsch

Comment by Alexander Vladishev [ 2012 Jun 18 ]

Handling of status check has been fully refactored in 2.0.0. Please reopen if it does not work.

Generated at Sun Mar 16 17:10:24 EET 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.