Re: [Nrpent-users] Distributed monitoring with nrpe_nt and freshness

[Jeff S. - D. T. <jef...@de...>]

Thanks for your reply.  Here are the answers to your questions.

1) The master server is allowed to talk to the nrpe_nt.  We have two
servers running nrpe_nt which are checking different services then each
other.  We are having this error when the master doesn't receive updates
anymore and then it sends it's checks to the other server running
nrpe_nt.  This way we don't have a period of services not being checked
because one of the nrpe_nt servers is down.  When the freshness is hit
it's threshold and the check is sent to the nrpe_nt server sometimes it
works and sometimes we get the error "No output available from command".
The resources are not high on the master or the nrpe_nt server at that
time.

2)  We are not getting any access denied errors in windows.

3)  We are not seeing a high load on any of the servers during this
time.  This is what I am trying to figure out if it's nrpe_nt or
something else.

I don't think we are hitting any type of socket limit because we are not
running enough checks at one time to hit a limit.  Do you have any other
ideas or if there maybe a limit on how many wmi tests can be run at a
time?

Thank you,
Jeff

-----Original Message-----
From: mic...@mi... [mailto:mic...@mi...]=20
Sent: Monday, November 12, 2007 9:25 AM
To: Jeff Shumard - DefenseWeb Technologies
Subject: RE: [Nrpent-users] Distributed monitoring with nrpe_nt and
freshness

Jeff,

Without a logfile I have to guess, but here are some things to check
for:

- Are the upstream/master servers allowed to talk to nrpe_nt at all
(firewalling, nrpe.cfg allowed hosts etc)?
- Does the logfile on windows show any signs of Error 5 (Access denied)
or the like?
- Is the problem really with nrpe_nt itself, or are the checks starting
to timeout because of the sudden high load?

There is no coded limit to what nrpe_nt handles, except for availability
of network sockets and process handles needed.
The only limit in connections seems to be from win itself. There is no
real documentation on it, but from my testing I found the limit of
concurrent connection to be in the area of 100+ to serveral 100s,
depending on the hardware. But usually, this should result in
"Connection refused by host" or timeout errors, no the message you are
seeing.


Regards
Michael Wirtgen

-----Original Message-----
From: nrp...@li...
[mailto:nrp...@li...] On Behalf Of Jeff
Shumard - DefenseWeb Technologies
Sent: Thursday, November 08, 2007 6:52 PM
To: nrp...@li...
Subject: [Nrpent-users] Distributed monitoring with nrpe_nt and
freshness

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?

Thank you,
Jeff

--------------------------------------------
Jeff Shumard
UNIX Administrator
=20
DefenseWeb Technologies, Inc.
4150 Mission Blvd., Suite 220
San Diego, CA 92109
=20
Office:   858-272-8505 x5897
Mobile:   619-997-5560
Fax:      858-228-3667
=20
Email:    jef...@de...
WWW:      www.defenseweb.com

----------------------------------
NOTICE: This email message is for the sole use of the intended
recipient(s) and may contain confidential and privileged information.
Any unauthorized review, use, disclosure or distribution is prohibited.=20
If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.

To contact our email administrator directly, send to
pos...@de....
----------------------------------


------------------------------------------------------------------------
-
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/
_______________________________________________
Nrpent-users mailing list
Nrp...@li...
https://lists.sourceforge.net/lists/listinfo/nrpent-users