sghosh at sghosh.org
Fri Aug 23 12:05:16 CEST 2002
try running with "-v" option to see what is executed
try strace to see if there are any delays in loading and libraries..
alternately, try using check_fping.
On 23 Aug 2002, Darren wrote:
> We are monitoring a wireless customer and noticing some strange results
> from just this one customer. From the Nagios box I can run:
> [root at chief libexec]# ping 204.xxx.xxx.67:
> PING 204.xxx.xxx.67 (204.xxx.xxx.67) from 204.xxx.xxx.3 : 56(84) bytes
> of data.
> 64 bytes from 204.xxx.xxx.67: icmp_seq=1 ttl=254 time=8.668 msec
> 64 bytes from 204.xxx.xxx.67: icmp_seq=2 ttl=254 time=9.026 msec
> 64 bytes from 204.xxx.xxx.67: icmp_seq=3 ttl=254 time=8.088 msec
> 64 bytes from 204.xxx.xxx.67: icmp_seq=4 ttl=254 time=35.096 msec
> 64 bytes from 204.xxx.xxx.67: icmp_seq=5 ttl=254 time=12.498 msec
> Works like a charm. Now I'm going to run CHECK_PING:
> [root at chief libexec]# ./check_ping -H 204.xxx.xxx.67 -w 3000,80% -c
> 5000,100% -p 1
> CRITICAL - Plugin timed out after 10 seconds
> Hmm, this happens EVERY single time I run it...now I'm going to change
> it to 5 pings.
> [root at chief libexec]# ./check_ping -H 220.127.116.11 -w 3000,80% -c
> 5000,100% -p 5
> PING OK - Packet loss = 20%, RTA = 20.32 ms
> These results cause the host to always be down, yet the ping service to
> show it as up. Does CHECK_PING use a large packet size? I don't have a
> clue what is causing this. Does anyone have any ideas?
> I'm running the newest version of Nagios(1.0b5) and Plugins (1.3beta1).
> Thanks in advance,
> - Darren
> This sf.net email is sponsored by: OSDN - Tired of that same old
> cell phone? Get a new here for FREE!
> Nagiosplug-help mailing list
> Nagiosplug-help at lists.sourceforge.net
More information about the Help