Process checks

[Rob Nelson]

How are process checks handled by Nagios? What I mean is if I set the max 
concurrent checks to 10, why do I only ever see 4-5 checks running at a 
time? Also, when I run into one bad check (i.e. failed ping), all the other 
checks stop until this one bad check times out three times in a row.

It doesn't make any sense, but I'm able to get a repeatable pattern out of 
this by stopping nagios, removing the .log and .sav file and restarting. 
Every time it gets to a downed host, it slows to a crawl. I am running 
Nagios 1.06b.

I have some other questions on things like latency (it says 1 / 2781 / 
2643.1 seconds on the tactical overview. What the heck does that mean?) and 
why service checks take soooo looong to process, but I have a feeling the 
bottleneck is in failing checks. I still have 60 checks out of 150 that 
haven't processed because of this in *three hours*.

Rob Nelson
Network Administrator, Capitol Broadband
C: 919-369-1874
rob at capband.net 



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
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