I guess that in 3.0rc3 you can modify service check configuration on-demand. <br><br>Not implemented yet, but you should be able to do something like changing normal_check_interval until it reaches an OK state.<br><br>Anyone here already come up with a solution to this problem? <br>
<br>Cheers<br><br><div class="gmail_quote">On Fri, Mar 7, 2008 at 10:44 AM, Tom Sommer <<a href="mailto:mail@tomsommer.dk">mail@tomsommer.dk</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br>
<br>
I wish to setup the following check interval:<br>
<br>
Check the service every 5 minutes<br>
-> If down then check the service every 1 minute for 3 minutes/times<br>
-> If still down, notify and continue to check the service every 1<br>
minute until it recovers.<br>
<br>
I'm having a few problems with the last condition. Basically once the<br>
notification is sent, Nagios seems to revert to the "normal" check<br>
interval, which is 5 minutes - resulting in a substantial delay for the<br>
recovery notification to be sent.<br>
<br>
My settings are:<br>
max_check_attempts 3<br>
check_interval 5<br>
retry_interval 1<br>
<br>
Did I miss anything or is the above simply not possible?<br>
<br>
Using 3.0rc3<br>
<br>
Thanks<br>
--<br>
Tom Sommer<br>
<br>
-------------------------------------------------------------------------<br>
This SF.net email is sponsored by: Microsoft<br>
Defy all challenges. Microsoft(R) Visual Studio 2008.<br>
<a href="http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/" target="_blank">http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/</a><br>
_______________________________________________<br>
Nagios-users mailing list<br>
<a href="mailto:Nagios-users@lists.sourceforge.net">Nagios-users@lists.sourceforge.net</a><br>
<a href="https://lists.sourceforge.net/lists/listinfo/nagios-users" target="_blank">https://lists.sourceforge.net/lists/listinfo/nagios-users</a><br>
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue.<br>
::: Messages without supporting info will risk being sent to /dev/null<br>
</blockquote></div><br>