Problem with Distributed Monitoring (Freshness Checking)

[Naman Latif]

Hi,
We have NAGIOS in a distributed monitoring setup. Everything works fine
until "The remote NAGIOS box goes down OR link to that box goes down",
in this case Central NAGIOS starts executing "Active Checks" for the
specific services, which is fine.
The problem is that when the Remote Box comes back up, NAGIOS keeps on
executing the Active checks with the reason "Results are stale", instead
of switching back to Passive checking. I am assuming that in this
situation a loop gets created in which, the remote results will always
be stale ?

Is there some sort of rule that I can follow to avoid this ? I am
assuming that this requires some tuning of the "freshness_threshold"
parameter ?

I have already set it as "800 seconds", while the Normal Check Interval
on the External Box (and on central box) is "180 seconds".
The "freshness_check_interval" in nagios.cfg is set at 60 sec.

Thanks \\ Naman


-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
>From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
_______________________________________________
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