Notification Timing Problem

Marc Powell marc at ena.com
Thu Oct 30 13:48:52 CET 2008


On Oct 29, 2008, at 5:11 PM, MJK Nagios wrote:

> The problem I'm seeing is that it takes
> Nagios 15-20 minutes to send a notification that the host is again
> down.  This would be useless to me in a production environment; if the
> host drops again -- I need to know about it immediately.


> October 29, 2008 16:00
> Host Down[10-29-2008 16:58:05] HOST ALERT: TEST-01;DOWN;HARD;10;(Host
> Check Timed Out)

I agree with Sascha, you've got your max_check_attempts (10?) and  
retry_check_interval (2?) set higher than you want them to be. 10x2 =  
20 minutes before notification.

--
Marc

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
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





More information about the Users mailing list