check-host-alive returns /bin/ping -n -U -c 1 192.168.231.7

[Russ Hubbard]

Th
omas,
The check-host-alive uses check_ping to do it's check. So it is the same 
as yours.  I am having the same issue with nagios reporting a server 
down when it is actually up.

Russ


Thomas Quinlan wrote:

>I am all of a sudden having the same issue, on two
>different Nagios boxes.  The difference for me is that
>I am using check_ping instead of check-host-alive. 
>(Some boxes return ok, other boxes return "bin/ping -n
>-U -c 5 w.x.y.z".)
>
>The additional problem I am having with that is that
>Nagios is actually incorrectly reporting a box as
>down, when in fact it is up.  I can ping it from the
>box (using "bin/ping -n -U -c 5 w.x.y.123") as both
>"root" and "nagios", so there's no reason Nagios
>should see it as not pinging.
>
>  
>
>>-----Original Message-----
>>From: nagios-users-admin at lists.sourceforge.net on
>>behalf of Russ Hubbard
>>Sent: Tue 5/25/2004 10:56 AM
>>To: nagios-users at lists.sourceforge.net
>>Subject: [Nagios-users] check-host-alive returns
>>/bin/ping -n -U -c 1 192.168.231.7
>> 
>>Hello,
>>   Last night I encountered some check-host-alive
>>commands that are 
>>returning some weird information. They return
>>"/bin/ping -n -U -c 1 
>>192.168.231.7" as the output and mark the host as
>>down.  I've gone 
>>through the list archives and mostly I found that
>>this can be caused by 
>>/bin/ping not having permissions of 4755. I have
>>checked this, here is 
>>the verification:
>>
>>-rwsr-xr-x    1 root     root        28724 Sep 11 
>>2003 /bin/ping
>>
>>I am currently running Nagios 1.2. I have been
>>running nagios for about 
>>a year and this is the first occurance of this
>>problem I have had. I 
>>have had a few outages in that time and they all
>>return the appropriate 
>>status information. Here is an example:
>>
>>PING CRITICAL - Host Unreachable (172.21.35.28)
>>
>>Here is my check-host-alive command from
>>checkcommand.cfg:
>>
>># 'check-host-alive' command definition
>>define command{
>>        command_name    check-host-alive
>>        command_line    $USER1$/check_ping -H
>>$HOSTADDRESS$ -w 
>>3000.0,80% -c 5000.0,100% -p 1
>>        }
>>
>>
>>Any help at all in fixing this problem would be
>>great. 
>>
>>Thanks,
>>
>>Russ
>>
>>
>>
>>
>>    
>>
>>>begin:vcard
>>>      
>>>
>>fn:Russ Hubbard
>>n:Hubbard;Russ
>>org:LSI Logic ;Enterprise Operations
>>adr:AL201;;4420 ArrowsWest Drive;Colorado
>>Springs;CO;80907;USA
>>email;internet:russ.hubbard at lsil.com
>>title:UNIX/Linux System Administrator
>>tel;work:(719)533-7973 
>>tel;fax:(719)533-6298
>>tel;pager:(800)260-5085
>>tel;cell:(719)660-8814
>>x-mozilla-html:TRUE
>>url:http://eops.co.lsil.com
>>version:2.1
>>end:vcard
>>
>>
>>    
>>
>
>
>
>	
>		
>__________________________________
>Do you Yahoo!?
>Friends.  Fun.  Try the all-new Yahoo! Messenger.
>http://messenger.yahoo.com/ 
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by: Oracle 10g
>Get certified on the hottest thing ever to hit the market... Oracle 10g. 
>Take an Oracle 10g class now, and we'll give you the exam FREE.
>http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
>_______________________________________________
>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
>
>  
>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: russ.hubbard.vcf
Type: text/x-vcard
Size: 382 bytes
Desc: not available
URL: <https://www.monitoring-lists.org/archive/users/attachments/20040525/094dc13d/attachment.vcf>