Ping timeouts

[Raful Mr Mitchell H]

I had to change the timout for warning and critical in the services
definition for ping.  Why is that?  Also, in the hosts detail I get this
message:

 (3000.000000) cannot be larger than  (1000.000000) 

Thanks,

Mitch


-----Original Message-----
From: Torleiv Ringer [mailto:tringer at mpr.org]
Sent: Tuesday, June 14, 2005 9:43 AM
To: Raful Mr Mitchell H
Cc: 'nagios-users at lists.sourceforge.net'
Subject: Re: [Nagios-users] Ping timeouts


On Tue, 2005-06-14 at 09:22 -0400, Raful Mr Mitchell H wrote:
> Is there anyway to extend the 500ms maximum for ping timeouts in
> either nagios 1.x or 2.x. I have satellite backup connections and the
> delay is definitely above that for some locations.

For your check_command on your hosts you can make your own ping command
in checkcommands.cfg.

I use something like this:

# 'check_wan_alive' command definition
define command{
	 command_name    check_wan_alive
	 command_line    $USER1$/check_ping -H $HOSTADDRESS$ -w 3000.0,80%
-c
10000.0,100% -p 5 -t 30
        }		 

This has a 30 second timeout, a 3000ms until warning with 80% packet
loss and a 10000ms latency and 100% packet loss before critical. Works
for almost all of my connections (SatIP, Frame, DSL).
-- 
Torleiv Ringer
Broadcast Systems Administrator
Minnesota Public Radio
http://www.mpr.org


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&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