I had a suspicion that the cause might be large numbers of hosts that go
down. Until I get around to them the host checks obviously continue...
perhaps that's what's causing the general slowdown in all of nagios.
Makes me wish again host checks were parallelized.
/eli
Ludwig Pummer wrote:
I had large latencies caused by (1) hosts being down and (2) a host
check that took way too long. Nagios will suspend all service checks
while it performs a host check. In my case, the Nagios config I
inherited made 10 attempts at 30 seconds each attempt before declaring a
host to be down, so if one host went down, the host check took 300
seconds. I typically have 15 hosts down out of 475. I changed my host
checks to 3 attempts at 6 seconds each, and latencies went way down.
--
Ludwig Pummer
System Administrator
Copart Auto Auctions
------------------------------------------------------------------------
*From:* [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] *On Behalf Of
*Blake Krone
*Sent:* Monday, December 05, 2005 2:08 PM
*To:* Nagios Users
*Subject:* [Nagios-users] Huge Service Latencies
Service Check Execution Time: 0.10 / 10.04 / 2.175 sec
Service Check Latency: 21.25 / 483.37 / 224.970 sec
Host Check Execution Time: 0.06 / 10.70 / 4.307 sec
Host Check Latency: 0.00 / 529.15 / 5.137 sec
# Active Host / Service Checks: 103 / 236
# Passive Host / Service Checks: 0 / 1
Machine is a P3 733mhz with 128mb ram running 2.6.11-gentoo-r3
kernel and Nagios 2.03b
Any ideas as to why it has such huge latencies?
-------------------------------------------------------
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@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