How do we report a possible bug (in check_ping)?

Eddie F bigedd at gmail.com
Fri Jun 20 08:25:33 CEST 2008


System ping work fine...

# /bin/ping -n -U -w 10 -c 5 nagios.org
PING nagios.org (66.118.156.22) 56(84) bytes of data.
64 bytes from 66.118.156.22: icmp_seq=1 ttl=45 time=431 ms
64 bytes from 66.118.156.22: icmp_seq=2 ttl=45 time=461 ms
64 bytes from 66.118.156.22: icmp_seq=3 ttl=45 time=451 ms
64 bytes from 66.118.156.22: icmp_seq=4 ttl=45 time=441 ms
64 bytes from 66.118.156.22: icmp_seq=5 ttl=45 time=452 ms
--- nagios.org ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 3999ms
rtt min/avg/max/mdev = 431.271/447.571/461.284/10.243 ms



On Fri, Jun 20, 2008 at 4:20 PM, Mathieu Gagné <mgagne at iweb.com> wrote:
> Eddie F wrote:
>>
>> See the two examples below, running check_ping on our system. Firstly
>> using the domain name, then using IP address...
>>
>> # /usr/local/nagios/libexec/check_ping -H nagios.org -w 300,10% -c
>> 1000,50% -p 5
>> CRITICAL - Plugin timed out after 10 seconds
>>
>> # /usr/local/nagios/libexec/check_ping -H 66.118.156.22 -w 300,10% -c
>> 1000,50% -p 5
>> PING WARNING - Packet loss = 0%, RTA = 709.87
>> ms|rta=709.869019ms;300.000000;1000.000000;0.000000 pl=0%;10;50;0
>>
>
> If you execute ping manually, what's the result?
>
> /bin/ping -n -U -w 10 -c 5 nagios.org
>
> --
> Mathieu
>

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null





More information about the Users mailing list