Creeping latency (Greg Vickers)

[Erik Larkin]

I had a somewhat related problem with freshness checks on my central server.
After the first check, latency would creep up and never stop; I'd see
latency of over 30000 seconds for checks that I'd purposely leave stale.
Search back in this list for "Huge delay in scheduling freshness service
check after 3rd try" for full details.  

I've had to treat this problem as a bug, since I couldn't find a fix.
Thankfully, since this is my central server and it's not performing any
active checks, I was able to toss in a kludgy workaround by reloading nagios
every hour, which resets the scheduling queue.  Latency creeps up in that
hour to about 200 seconds or so (if a freshness check is stale for the
duration), but that's bearable.

Erik


Today's Topics:

   1. Creeping latency (Greg Vickers)
--__--__--

Message: 1
From: Greg Vickers <daehenoc at optusnet.com.au>
To: nagios-users at sourceforge.net
Date: Fri, 11 Apr 2003 13:18:23 +1000
Subject: [Nagios-users] Creeping latency

Hi all,

I'm seeing the latency of my checks creep up
and up to about 200-300 seconds after each
restart of Nagios.

Which is weird, cause:
service_reaper_frequency=1
max_concurrent_checks=0

So the checks get reaped every second
(limiting instances of Nagios in memory) and
it spawns as many checks as it wants. Now I
know that my service checks do not take
*that* long to complete. In fact the service
checks are all set to time out after 30 seconds.

Anyone else having this problem???

Greg


-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger 
for complex code. Debugging C/C++ programs can leave you feeling lost and 
disoriented. TotalView can help you find your way. Available on major UNIX 
and Linux platforms. Try it free. www.etnus.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