Plugins timing out

[misc at viceconsulting.co.nz]

Hi All,

On a server with 400 service checks I have about 10 service checks that
are timing out.  My timeout value is set to 25 seconds.  While I am trying
to resolve the timeout issues, I am keen to find out how Nagios reacts
when waiting for service check results.

What happens when Nagios is waiting for the result of a service check? 
Will Nagios continue to happily schedule service checks even when waiting
for a result, or will it await the result of a service check before
scheduling another?  If it does schedule multiple service checks
simultaneously, is there a limit to the maximum number of service checks
that Nagios will check at a given time?

My average check Latency for this Nagios server (as per "Performance
Info") is 132.551 seconds.  Would I be correct in assuming that this high
latency value could be caused by these few rogue service checks that are
timing out?

Also, this is a distributed Nagios server which results to the Central
Nagios server.  I am getting quite a few "Stale Results" from this
distributed result.  Is it possible for a few rogue service checks which
are timining out to throw out the remaining service checks from this
distributed Nagios server causing stale results?  The stale results being
reported by the Central Nagios server are not exclusively the rogue
timeout services but also regular checks that don't time out.

Any insight into any of this would be much appreciated.

Alex.


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
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