host shows down but it is not [check_icmp]

[Joe Konecny]

On 10/14/2009 2:24 PM, Marc Powell wrote:
>
> On Oct 14, 2009, at 12:44 PM, Joe Konecny wrote:
>
>> I did some testing on the command line and check_icmp fails
>> every time if -n>  1.  So this...
>>
>> check_icmp -n 1 70.62.24.79
>>
>> ...works.
>>
>> To me it looks like a bug in check_icmp.
>
> Not impossible but that would be surprising. check_icmp is known to be
> stable and has less than 10 bugs logged against it since 2004 (mostly
> for compile problems on various OS's).
>
> What OS are you running?

Ubuntu 9.04


> How did you install the plugins (package or
> source?

source

> Using the same architecture as your OS, 1386 or _64?).
>

i386

> What output do you receive when running it from the command line for
> your problem host with verbose flags? Be sure you test using the same
> command_line as the check_icmp command definition, just adding two -
> v's like --
>
> /path/to/check_icmp -H<yourhost>  -n5 -v -v
>
> --
> Marc
>

The output is below.   Also I just installed Nagios on a different
machine and get the same results.

root at 3px:~# /usr/local/nagios/libexec/check_icmp -v -v 70.62.24.79
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: 64  timeout: 10
received 84 bytes from 70.62.24.79
1.029 ms rtt from 70.62.24.79, outgoing ttl: 64, incoming ttl: 63
recvfrom_wto() timed out during a 80000 usecs wait
recvfrom_wto() timed out during a 40000 usecs wait
recvfrom_wto() timed out during a 40000 usecs wait
recvfrom_wto() timed out during a 26666 usecs wait
recvfrom_wto() timed out during a 26666 usecs wait
recvfrom_wto() timed out during a 26666 usecs wait
recvfrom_wto() timed out during a 20000 usecs wait
recvfrom_wto() timed out during a 20000 usecs wait
recvfrom_wto() timed out during a 20000 usecs wait
recvfrom_wto() timed out during a 20000 usecs wait
time_passed: 322696  final_wait: 3077304  max_completion_time: 3400000
Waiting for 3077304 micro-seconds (3077.304 msecs)
recvfrom_wto() timed out during a 769326 usecs wait
recvfrom_wto() timed out during a 769326 usecs wait
recvfrom_wto() timed out during a 769326 usecs wait
recvfrom_wto() timed out during a 769326 usecs wait
finish(0) called
icmp_sent: 5  icmp_recv: 1  icmp_lost: 0
targets: 1  targets_alive: 1
CRITICAL -
70.62.24.79: rta 1.029ms, lost 80%|
rta=1.029ms;200.000;500.000;0; pl=80%;40;80;;
targets: 1, targets_alive: 1, hosts_ok: 0, hosts_warn: 0, min_hosts_alive: -1

*******  and just for kicks...

root at 3px:~# /usr/local/nagios/libexec/check_icmp -n 1 -v -v 70.62.24.79
ttl set to 64
Setting alarm timeout to 10 seconds
packets: 1, targets: 1
target_interval: 0.000, pkt_interval 80.000
crit.rta: 500.000
max_completion_time: 1080.000
crit = {500000, 80%}, warn = {200000, 40%}
pkt_interval: 80000  target_interval: 0  retry_interval: 0
icmp_pkt_size: 64  timeout: 10
received 84 bytes from 70.62.24.79
1.045 ms rtt from 70.62.24.79, outgoing ttl: 64, incoming ttl: 63
finish(0) called
icmp_sent: 1  icmp_recv: 1  icmp_lost: 0
targets: 1  targets_alive: 1
OK -
70.62.24.79: rta 1.045ms, lost 0%|
rta=1.045ms;200.000;500.000;0; pl=0%;40;80;;
targets: 1, targets_alive: 1, hosts_ok: 1, hosts_warn: 0, min_hosts_alive: -1

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
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