Marc Powell wrote: > check returns non-OK, the service is immediately put into a hard state > and no further retries are attempted. Nagios would then fall back to the > normal_check_interval for the service check. Beyond the fact that > services on down hosts are still checked, your scenario WRT > retry_check_interval doesn't appear to happen. > > Just for clarification, as long as you're within max_check_attempts for > your service, then nagios operates with your more frequent check > interval. As soon as you reach max_check_attempts or your host check > returns a non-OK state, the service falls back to normal_check_interval. > Aha, thanks for clearing that up, it must have been a misinterpretation on my part that the retry check interval is not for all retries but only for those up to max check attempts, so if the max check attempts is low then retry interval only affects how quickly it will go into a hard failure state.
Thanks for the clarification. -h ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ 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
