Distributed monitoring with nrpe_nt and freshness

[Jeff Shumard - DefenseWeb Technologies]

Everything works fine checking the hosts if I force an active check for
all services on a host.  We are not doing host checks at all on your
servers just service checks.  The only time I have a problem is when the
freshness threshold is reached and it tries to force a check on a lot of
services at once.  It is almost like nrpe_nt is only able to process a
set amount of checks at one time.  There is no resource issue at the
time this is happening on the Nagios server and on the Windows server
running the checks.

Has anyone else had this problem?

Thank you,
Jeff


-----Original Message-----
From: Thomas Guyot-Sionnest [mailto:dermoth at aei.ca] 
Sent: Sunday, November 04, 2007 1:36 PM
To: Jeff Shumard - DefenseWeb Technologies
Cc: nagios-users at lists.sourceforge.net
Subject: Re: [Nagios-users] Distributed monitoring with nrpe_nt and
freshness

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 02/11/07 01:11 PM, Jeff Shumard - DefenseWeb Technologies wrote:
> We have our monitoring configured and everything is working great
> checking all our windows servers through a single windows server
running
> nrpe_nt.  The problem we are having is when one of our Linux Nagios
> servers goes down and doesn't send any results to the master Nagios
> server.  When this happens and our 5 minute freshness hits it's
> threshold.  We start running active checks because we didn't receive
any
> passive updates from the server that went down.  This sends a bunch of
> checks to the windows server to run tests and we start getting unknown
> status reports back to the master server with the result of "No output
> available from command".  Does anyone know if there is a max
connection
> on nrpe_nt or something else that maybe causing this?

While I can't answer your question, I can suggest using check_dummy to
set an UNKNOWN status to hosts not monitored. Is especially make sense
if some of the hosts can't be monitored directly from the central
server.

Also are you sure the central server is allowed to talk to your nrpe_nt
(IP access list)?

Thomas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHLjsw6dZ+Kt5BchYRAq6pAKDHXC7fjtgFNNTQUnJXrDXJxMDKAQCfftsa
OTu41Chzk37uyYHRCU3x+eM=
=VZZn
-----END PGP SIGNATURE-----

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
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