what if event handler failed?

[Kelvin Wu]

thanks Jason,

it's a good idea to fix the problem on CRITICAL SOFT state, and next
question is, does nagios has enough time to finish the event handler?
because some event handlers may take 1 or 2 mins to finish.

i have 3000 services right now, 
interval_length=60
max_concurrent_checks=100
inter_check_delay_method=s

normal_check_interval 5
retry_check_interval 1
max_check_attempts 4

CRITICAL SOFT 1: do nothing, just want a double check
CRITICAL SOFT 2: event handler, fix the problem
CRITICAL SOFT 3: do nothing, give enough time to event handler
CRITICAL SOFT 4: OK, means problem fixed by event handler, or
CRITICAL, means event handler is not finished or failed, send alert.

how does nagios schedule retry_checks taskes? does event handler has
exactly 2mins or more(less) to execute accroding to my configuration?

thanks.


On Wed, 25 Aug 2004 08:16:08 -0700, Jason Martin <jhmartin at toger.us> wrote:
> The general idea is to configure the event handler to fix the
> problem during the 'SOFT' state, and if the handler fails to
> resolve the problem then the sevice will go into a HARD error
> state and send a notification. If your staff gets a notification
> about the file size being too large, the implication is that the
> automated fix did not work.
> 
> -Jason Martin


-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
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