[Fwd: Re: soft state turns to hard state after a delay]

[Marc Powell]

Yes, those options work the same for active or passive checks, kinda. If
you have a remote nagios daemon sending back the results then it will of
course respect all three (normal_check_interval, retry_check_interval,
and max_check_attempts), presuming they're configured the same on the
remote nagios host. If you have some other process sending the results
back then of course nagios has no control over normal_check_interval
_or_ retry_check_interval but it will wait for max_check_attempts before
alerting...

--
Marc

> -------- Original Message --------
> Subject: 	Re: [Nagios-users] soft state turns to hard state after
a
> delay
> Date: 	Mon, 14 Mar 2005 20:19:20 +0100
> From: 	Matthias Bertschy <matthias at echotech.ch>
> To: 	Andreas Ericsson <ae at op5.se>
> References: 	<4235D080.2020409 at echotech.ch> <4235E1AD.5010308 at op5.se>
> 
> 
> 
> Marc Powell and you are right, I must be fool not to use these config
> options.
> 
> However, I wonder whether these are still working for a service
> passively checked?
> 
> Anyway, thx for your help :-)
> 
> Matthias
> 
> Andreas Ericsson wrote:
> 
> > Matthias Bertschy wrote:
> >
> >> Hello,
> >>
> >> Right now I am evaluating Nagios for an extensive use within our
> >> company. I have a question about soft/hard state transformation.
> >>
> >> On the page:
> >> http://nagios.sourceforge.net/docs/2_0/statetypes.html
> >> I read:
> >> Hard states occur (...) (w)hen a service check results in a non-OK
> >> state and it has been (re)checked the number of times specified by
> >> the </max_check_attempts/> option in the service definition.
> >>
> >> Would it be possible to specify a time period allowed for the
service
> >> to recover instead of a number of checks? For example, I would like
> >> to let a service (such as apache) try to recover from its own
during
> >> 30min before warning the administrator. Is that possible (ideally
> >> without tweaking the </max_check_attempts/> and the delay between
> >> checks)?
> >>
> >
> > As this is the only reason for the retry_check_interval and
> > max_check_attempts to exist, I see no reason why you would possibly
> > want to do it witouth tweaking them.
> >
> > Set retry_check_interval to 2 and max_check_attempts to 15, and
you're
> > good to go.
> >
> > If you absolutely cannot stand tweaking those two variables (why, oh
> > why?!) there is still a way out. Read up on escalations. It's in the
> > docs.
> >



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id396&op=click
_______________________________________________
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