Retry interval on hard states

[Tom Sommer]

Would this feature not be best served being in the core?

Marcel wrote:
> here it is:
> 
> http://nagios.sourceforge.net/docs/3_0/adaptive.html
> 
> 
> 
> On Fri, Mar 7, 2008 at 3:10 PM, Marcel <webknowledge at gmail.com 
> <mailto:webknowledge at gmail.com>> wrote:
> 
>     I guess that in 3.0rc3 you can modify service check configuration
>     on-demand.
> 
>     Not implemented yet, but you should be able to do something like
>     changing normal_check_interval until it reaches an OK state.
> 
>     Anyone here already come up with a solution to this problem?
> 
>     Cheers
> 
> 
>     On Fri, Mar 7, 2008 at 10:44 AM, Tom Sommer <mail at tomsommer.dk
>     <mailto:mail at tomsommer.dk>> wrote:
> 
>         Hi,
> 
>         I wish to setup the following check interval:
> 
>         Check the service every 5 minutes
>          -> If down then check the service every 1 minute for 3
>         minutes/times
>           -> If still down, notify and continue to check the service every 1
>         minute until it recovers.
> 
>         I'm having a few problems with the last condition. Basically
>         once the
>         notification is sent, Nagios seems to revert to the "normal" check
>         interval, which is 5 minutes - resulting in a substantial delay
>         for the
>         recovery notification to be sent.
> 
>         My settings are:
>         max_check_attempts 3
>         check_interval 5
>         retry_interval 1
> 
>         Did I miss anything or is the above simply not possible?
> 
>         Using 3.0rc3


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
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