Freshness checking and a distributed Nagios system.

[Jonathan Call]

I did read through that section thoroughly. I set up the check on the
central server and then disabled the check on the distributed server. I
waited for the time limit to expire. I watch the central server set the
next active check time to ~10 minutes after the last check time. But
that time came and went and nothing happened.

Perhaps this is because I have active checks disabled globally (via
nagios.cfg) on my central server instead of on a per host basis?

-----Original Message-----
From: Tom Ammon [mailto:tom.ammon at utah.edu] 
Sent: Friday, August 15, 2008 12:03 PM
To: Jonathan Call
Cc: nagios-users at lists.sourceforge.net
Subject: Re: [Nagios-users] Freshness checking and a distributed Nagios
system.

Nagios forces active checks to be run when used in conjuction with 
freshness checking, even when active checks for that service are 
disabled. The docs describe it pretty well at 
http://nagios.sourceforge.net/docs/2_0/distributed.html under the 
"Freshness Checking" section. You have to read it carefully, though.

Tom

Jonathan Call wrote:
> Correct me if I'm wrong:
> In order to run a distributed system, the central server should have
> active service checks disabled. But freshness checking executes the
> check command when it doesn't receive a passive response in a timely
> manner. This means the freshness check never runs.
>
> How do you get around that?
>
>
> This email message is intended for the use of the person to whom it
has been sent, and may contain information that is confidential or
legally protected. If you are not the intended recipient or have
received this message in error, you are not authorized to copy,
distribute, or otherwise use this message or its attachments. Please
notify the sender immediately by return e-mail and permanently delete
this message and any attachments. Verio, Inc. makes no warranty that
this email is error or virus free.  Thank you.
>
>
------------------------------------------------------------------------
-
> This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
> Build the coolest Linux based applications with Moblin SDK & win great
prizes
> Grand prize is a trip for two to an Open Source event anywhere in the
world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> 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
>   

-- 
-------------------------------------
Tom Ammon
Network Engineer

Business Card at http://tomsbox.net/bizcard_TomAmmon.jpg

Center for High Performance Computing
University of Utah
http://www.chpc.utah.edu



This email message is intended for the use of the person to whom it has been sent, and may contain information that is confidential or legally protected. If you are not the intended recipient or have received this message in error, you are not authorized to copy, distribute, or otherwise use this message or its attachments. Please notify the sender immediately by return e-mail and permanently delete this message and any attachments. Verio, Inc. makes no warranty that this email is error or virus free.  Thank you.

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
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