[Nagiosplug-devel] How do we report a possible bug (in check_ping)?

[Holger Weiss]

* Eddie F <bigedd at gmail.com> [2008-06-20 23:20]:
> # /usr/local/nagios/libexec/check_ping -vvv -H nagios.org -w 300,10% -c
> 1000,50% -p 5 -t 60
> CMD: /bin/ping -n -U -w 60 -c 5 nagios.org
> Output: PING nagios.org (66.118.156.22) 56(84) bytes of data.
> Output: 64 bytes from 66.118.156.22: icmp_seq=1 ttl=45 time=435 ms
> Output: 64 bytes from 66.118.156.22: icmp_seq=2 ttl=45 time=395 ms
> Output: 64 bytes from 66.118.156.22: icmp_seq=3 ttl=45 time=345 ms
> Output: 64 bytes from 66.118.156.22: icmp_seq=4 ttl=45 time=435 ms
> Output: 64 bytes from 66.118.156.22: icmp_seq=5 ttl=45 time=435 ms
> Output:
> Output: --- nagios.org ping statistics ---
> Output: 5 packets transmitted, 5 received, 0% packet loss, time 4000ms
> Output: rtt min/avg/max/mdev = 345.846/409.540/435.725/35.383 ms
> PING WARNING - Packet loss = 0%, RTA = 409.54
> ms|rta=409.540009ms;300.000000;1000.000000;0.000000 pl=0%;10;50;0
> 300.000000:10% 1000.000000:50%
> 
> 
> Yes... That's better, but why is it that I don't have the problem with a
> system ping to a domain name?

Is there some identifiable point during the execution of the above
plugin command where the plugin or ping(1) seems to be really slow?  Is
running the command

$ /bin/ping -n -U -w 60 -c 5 nagios.org

manually significantly faster?

> dig nagios.org returns -> Query time: 3 msec

dig(1) queries a name server directly while your system's resolver might
use stuff like nscd(8) or whatever.

Holger