Page 1 of 1

strange behavior of check_icmp plugin

Posted: Mon Jul 14, 2014 12:47 am
by pine5514
hi,
I have some attendance devices and want to monitor them via ping.
nagios server and device are in the same network.(no firewall/router hop)
the problem is that although ping command correctly says host is up but check_icmp says it down!!!!
I can not ping non of Attendance device via check_icmp/check_host.I also have no problem with other device type.


Here is ping and check_icmp output,
================
check_icmp v1.5 (nagios-plugins 1.5)
================
ping 172.16.11.9
PING 172.16.11.9 (172.16.11.9) 56(84) bytes of data.
64 bytes from 172.16.11.9: icmp_req=1 ttl=255 time=13.6 ms
64 bytes from 172.16.11.9: icmp_req=2 ttl=255 time=13.6 ms
64 bytes from 172.16.11.9: icmp_req=3 ttl=255 time=13.6 ms
64 bytes from 172.16.11.9: icmp_req=4 ttl=255 time=13.6 ms
64 bytes from 172.16.11.9: icmp_req=5 ttl=255 time=13.7 ms
64 bytes from 172.16.11.9: icmp_req=6 ttl=255 time=13.6 ms
64 bytes from 172.16.11.9: icmp_req=7 ttl=255 time=13.6 ms
^C64 bytes from 172.16.11.9: icmp_req=8 ttl=255 time=13.6 ms
64 bytes from 172.16.11.9: icmp_req=9 ttl=255 time=13.5 ms
^C
--- 172.16.11.9 ping statistics ---
9 packets transmitted, 9 received, 0% packet loss, time 8006ms
rtt min/avg/max/mdev = 13.587/13.638/13.750/0.074 ms

======================

check_icmp -v 172.16.11.9
ttl set to 64
Setting alarm timeout to 10 seconds
packets: 5, targets: 1
target_interval: 0.000, pkt_interval 80.000
crit.rta: 500.000
max_completion_time: 3400.000
crit = {500000, 80%}, warn = {200000, 40%}
pkt_interval: 80000 target_interval: 0 retry_interval: 0
icmp_pkt_size: 76 timeout: 10
time_passed: 401322 final_wait: 2998678 max_completion_time: 3400000
Waiting for 2998678 micro-seconds (2998.678 msecs)
handle_random_icmp(0x7fff3bde9cb0, 0x7fff3bde9c10)
handle_random_icmp(0x7fff3bde9cb0, 0x7fff3bde9c10)
handle_random_icmp(0x7fff3bde9cb0, 0x7fff3bde9c10)
handle_random_icmp(0x7fff3bde9cb0, 0x7fff3bde9c10)
handle_random_icmp(0x7fff3bde9cb0, 0x7fff3bde9c10)
handle_random_icmp(0x7fff3bde9cb0, 0x7fff3bde9c10)
handle_random_icmp(0x7fff3bde9cb0, 0x7fff3bde9c10)
handle_random_icmp(0x7fff3bde9cb0, 0x7fff3bde9c10)
handle_random_icmp(0x7fff3bde9cb0, 0x7fff3bde9c10)
handle_random_icmp(0x7fff3bde9cb0, 0x7fff3bde9c10)
icmp_sent: 5 icmp_recv: 0 icmp_lost: 0
targets: 1 targets_alive: 1
CRITICAL -
172.16.11.9: rta nan, lost 100%|
rta=0.000ms;200.000;500.000;0; pl=100%;40;80;; rtmax=0.000ms;;;; rtmin=0.000ms;;;;
targets: 1, targets_alive: 0, hosts_ok: 0, hosts_warn: 0, min_hosts_alive: -1

Re: strange behavior of check_icmp plugin

Posted: Mon Jul 14, 2014 12:07 pm
by tmcdonald
You might try installing the latest version of the plugins, as there have been some significant changes in 2.0

http://nagios-plugins.org/

Re: strange behavior of check_icmp plugin

Posted: Mon Jul 14, 2014 11:39 pm
by pine5514
TNX for your reply but I have the same error on check_icmp v2.0 (monitoring-plugins 2.0) :?

Re: strange behavior of check_icmp plugin

Posted: Tue Jul 15, 2014 9:17 am
by abrist
Well, we do not support monitoring plugins. We do support Nagios Plugins - I have a suspicion you will still have the issue, but can you try with:
http://www.nagios.org/download/plugins
Can we work with this issue on github?