On Mon, 12 Dec 2005, Subhendu Ghosh wrote:
On Mon, 12 Dec 2005 [EMAIL PROTECTED] wrote:
>
> Is it possible for us to set the threshold for host_check_alive
> command time out to 2 minutes? We will considered the server is really
> down after 2 minutes.
2 minutes is a long time for a ping response.
If you really want the 2 minutes, consider your retry-interval and max
retry setting rather than the command timeout.
For a service check you can use retry_check_interval and
max_check_attempts, but as soon as a service check fails a host check will
be done and the number of host_checks defined to run is executed in one
series without any delay, so there is no real good way of making nagios
"hold" for 2 minutes before considering it down. You could of cource make
the host_check_alive script hold for two minutes before returning if the
host is not responding, but that is probably not such a good idea as it
will stall all other checks during that time.
You may however use escalations to suppress one or more notifications, to
add a delay before a notification is accually sent even if the host is
considered down immediatly when it doesn't respond to a number of pings.
I've also written a patch that adds a new host option,
first_notification_delay that can be used to specify the time we want
Nagios to wait before sending any notifications for a given host. You can
find it in the last month archive of the nagios-devel list if you're
interested.
//Mathias
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Nagios-users mailing list
Nagios-users@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
