Host Down - no packets lost, just a rta higher than 10 ms

[Terry Simons]

Katie,

The problem appears to be in your command_line option:

command_line   /opt/apps/nagios/libexec/check_ping -H $HOSTADDRESS$ -w 
5,1% -c 10,5% -p 5 -t 1000

You're telling it to send a critical notification if you have 10ms of 
latency, or 5% packet loss.

You had 14 ms of latency, thus it sent out a critical notification.

Hope that helps,

- Terry

On Monday, August 12, 2002, at 12:41 PM, katherine.elliott at autodesk.com 
wrote:

> Hi,
>
> I am having a problem with getting host down notifications when the 
> hosts are not down. There are not any packets lost just a higher rta. 
>  I set a high rta of 1000 in the command line. It appears to actually 
> be ms and not seconds, so I set it this high in hopes that I would 
> never get a Host Down error because of a high rta. However I still got 
> a host down notication:
>
>  
>
> * Nagios *
>
>  
>
> Notification Type: PROBLEM
>
> Host: kermit
>
> State: DOWN
>
> Address: 144.111.2.51
>
> Info:PINGCRITICAL - Packet loss = 0, RTA = 14.00 ms
>
>  
>
> Date/Time: Sat Aug 1006:11:13 GMT2002
>
>  
>
> commands.cfg:
>
> command_line   /opt/apps/nagios/libexec/check_ping -H $HOSTADDRESS$ -w 
> 5,1% -c 10,5% -p 5 -t 1000
>
>  
>
> Ideally I would like it to never notify unless just packets are lost. 
>   I am using check_ping (netsaint-plugins 1.2.9-4) 1.41.2.3
>
> Usage: check_ping -H <host_address> -w <wrta>,<wpl>% -c <crta>,<cpl>%
>
>       [-p packets] [-t timeout] [-L].
>
>  
>
> Any help will be much appreciated!
>
>  
>
> Thanks,
>
> Katie
>



-------------------------------------------------------
This sf.net email is sponsored by: Dice - The leading online job board
for high-tech professionals. Search and apply for tech jobs today!
http://seeker.dice.com/seeker.epl?rel_code1