Services go stale after HARD state change

[Demetri Mouratis]

On Wed, 15 Oct 2003, James Harrison wrote:

> List,
>
> I have recently migrated from a central only to central and distributed
> environment.
>
> I was having some trouble with freshness, but as my distributed box
> polls every 5 minutes I have set my central server's freshness_threshold
> at 330 seconds (5.5 mins.)  This seems to have calmed down my central
> server and things seem ok.
>
> Now I'm noticing that my services seem to be going stale after I have a
> HARD state change and notices are sent out.  (I'm using email and
> qpage[local modem] notifications)
>
> Is this because notices(dialing a local modem, etc) is CPU intense?  I
> just had an outage my loads are .73,.51,.45.  I had a boat load of
> services go stale on the state changes.
>
> What could be causing my services to go stale?  Anything I can do to
> mitigate this problem?
James,

Edit your services.cfg file to set freshness_threshold higher.  On a hard
state change, Nagios will always check the host so there's not really a
way around that without dropping freshness checking altogether.
---------------------------------------------------------------------
Demetri Mouratis
dmourati at linfactory.com



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
_______________________________________________
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