Huge Service Latencies

Eli Stair estair at ilm.com
Mon Dec 5 23:31:46 CET 2005


Just for comparison, I'm having a very similar issue.  Currently it's 
better, but latency last week was around the same area.  I'm running 
with the perlcache, most checks are quick SNMP gets.  System is a dual 
Opteron 246, 4GB RAM and currently doing nothing but this.

Check Execution Time:  	0.02 sec	30.02 sec	6.020 sec
Check Latency:	0.09 sec	79.02 sec	69.122 sec
Percent State Change:	0.00%	15.86%	0.03%

/eli

PS - I'm moving the SNMP checks to Cacti, and pulling them with 
check_rrd_data.pl due to the huge delay (and load) in the perl wrapper 
to snmpwalk.




Hugo van der Kooij wrote:
> On Mon, 5 Dec 2005, Blake Krone wrote:
> 
> 
>>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
> 
> 
> A bare website with 128MB is not too generous. Add nagios to it and it
> becomes cramped. And you must run CGI scripts, check scripts and the lot.
> I would say you're running out of RAM.
> 
> You can use tools like top, vmstat, free, .... to check your machine.
> 
> Hugo.
> 



-------------------------------------------------------
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





More information about the Users mailing list