agent.ping.nodata returns up, but trigger reports down

[elvar]

One of the Ubuntu 9.10 servers I'm monitoring via 1.8 agent and 1.8 server keeps showing unreachable via the trigger 'agent.ping.nodata(300)}=1', however when I keep looking at the latest 500 values all I see are UP. Check out http://pastebin.com/m7c286447 to see the latest 500 I posted. This is the only agent I'm having this problem on and I've made sure to specify which IP to listen on. One thing I should mention is that if I restart the agent it will show as available for approximately 5-10 mins then it goes back to unreachable.

Any suggestions would be great!


Regards,
Elvar

[elvar]

I'd also like to add that I've had constant pings going from the Ubuntu server the Agent is running on to the zabbix server and haven't dropped any icmps even though the agent keeps reporting unreachable on & off.

[MrKen]

Looking at your pastebin it's difficult to determine the update interval for your agent.ping

1. 2009.Dec.22 08:19:13 Up (1)
2. 2009.Dec.22 07:23:06 Up (1)
3. 2009.Dec.22 05:44:35 Up (1)
4. 2009.Dec.22 04:15:07 Up (1)
5. 2009.Dec.22 04:11:05 Up (1)
6. 2009.Dec.22 04:10:35 Up (1)
7. 2009.Dec.22 04:03:06 Up (1)
8. 2009.Dec.22 03:07:04 Up (1)
9. 2009.Dec.22 02:33:05 Up (1)
10. 2009.Dec.22 02:06:05 Up (1)
11. 2009.Dec.22 01:10:05 Up (1)
12. 2009.Dec.22 00:37:05 Up (1)

But looking at your trigger expression, it is going to be True if there is no value returned within 5 minutes, so most of the above update intervals are more than 5 minutes meaning that the trigger will fire. Also, it's not surprising that all is well for 5 - 10 minutes after restarting the agent.

MrKen

[elvar]

Looking at your pastebin it's difficult to determine the update interval for your agent.ping

1. 2009.Dec.22 08:19:13 Up (1)
2. 2009.Dec.22 07:23:06 Up (1)
3. 2009.Dec.22 05:44:35 Up (1)
4. 2009.Dec.22 04:15:07 Up (1)
5. 2009.Dec.22 04:11:05 Up (1)
6. 2009.Dec.22 04:10:35 Up (1)
7. 2009.Dec.22 04:03:06 Up (1)
8. 2009.Dec.22 03:07:04 Up (1)
9. 2009.Dec.22 02:33:05 Up (1)
10. 2009.Dec.22 02:06:05 Up (1)
11. 2009.Dec.22 01:10:05 Up (1)
12. 2009.Dec.22 00:37:05 Up (1)

But looking at your trigger expression, it is going to be True if there is no value returned within 5 minutes, so most of the above update intervals are more than 5 minutes meaning that the trigger will fire. Also, it's not surprising that all is well for 5 - 10 minutes after restarting the agent.

MrKen

Hrm, any suggestions on figuring out why agent.ping is getting results more than 5 mins apart? I looked at my other hosts and none of them are showing results that far apart.

Also, thanks for the reply!

[elvar]

MrKen: Looks like I'm experiencing the same thing you mention here in this thread http://www.zabbix.com/forum/showthre...ght=agent.ping

[MrKen]

Yes it does look like the same problem. But why it happens, I don't know.

MrKen

[elvar]

Solved

I fixed my problem by raising Timeout=3 to Timeout=5 in my zabbix_server.conf. The default was fine for all hosts but this one. Such an easy fix I wish I had tried that a long time ago.

[avijit.dhar]

agent.ping.nodata returns up, but trigger reports down

Hi all ,

I am new in zabbix, using Zabbix 2.0.5 server and facing the problem

Trigger: Zabbix agent on host is unreachable for 5 minutes
Trigger status: PROBLEM
Trigger severity: Average
Trigger URL:

Item values:

1. Agent ping (host:agent.ping): Up (1)
2. *UNKNOWN* (*UNKNOWN*:*UNKNOWN*): *UNKNOWN*
3. *UNKNOWN* (*UNKNOWN*:*UNKNOWN*): *UNKNOWN*

I have configure (Timeout=3 to Timeout=5 in my zabbix_server.conf) but
the problem till remain. I am very confuse, what should i do? please any one suggest me.
thanking in advance .

[elvar]

Hi all ,

I am new in zabbix, using Zabbix 2.0.5 server and facing the problem

Trigger: Zabbix agent on host is unreachable for 5 minutes
Trigger status: PROBLEM
Trigger severity: Average
Trigger URL:

Item values:

1. Agent ping (host:agent.ping): Up (1)
2. *UNKNOWN* (*UNKNOWN*:*UNKNOWN*): *UNKNOWN*
3. *UNKNOWN* (*UNKNOWN*:*UNKNOWN*): *UNKNOWN*

I have configure (Timeout=3 to Timeout=5 in my zabbix_server.conf) but
the problem till remain. I am very confuse, what should i do? please any one suggest me.
thanking in advance .

Have you tried raising the timeout higher than 5? Are you still having this issue?

[Paladinemishakal]

Hi All,

I am facing the same issue and it is very annoying to keep receiving the email alerts. I have increased the Timeout to 30 and still no effect.

I would like to ask what does the agent.ping does? Is it the same as doing an icmp ping to the target server? Is the purpose of agent.ping trying to check if the agent is not responding? What is the agent.ping suppose to respond to (eg. connect request or response or whatever?)

Regards.

[Gilmar.Souza]

agent.ping.nodata returns up, but trigger reports down

I have the same problem:

Trigger: Server is unreachable
Trigger status: PROBLEM
Trigger severity: High
Trigger URL:

Item values:

1. Agent ping (Server:agent.ping): Up (1)
2. *UNKNOWN* (*UNKNOWN*:*UNKNOWN*): *UNKNOWN*
3. *UNKNOWN* (*UNKNOWN*:*UNKNOWN*): *UNKNOWN*

Original event ID: 63470


I have configure Timeout=30 in my zabbix_server.conf but the problem still remain.
Someone fix this?

[jorioux]

I have the same issue.

When I execute zabbix_get:

zabbix_get -s 192.168.1.1 -p 10050 -k agent.ping

If the host is not responding I should get "0", but I get this:

zabbix_get [26727]: Get value error: cannot connect to [[192.168.1.1]:10050]: [113] No route to host

What is wrong?

[aib]

"Cannot connect" means:
- there is Firewall
- there is some routing issue
- SElinux is active

Please, check all security products which can stop your zabbix_agent from connecting to zabbix_server.