Multiple Nagios proccesses running.

[Brian Murphy]

Andreas Ericsson <ae <at> op5.se> writes:


> Most definitely not. There's room for one method of processing checks, 
> and one only (each method is quite complex and requires a fair amount of 
> code). When (or if) the change is made, the old system of processing 
> checks will be dropped entirely.
> 
> > Do I need to find a way to stop the results coming through in clumps?
> > 
> 
> Not necessarily, no. You can probably get fairly good results by 
> decreasing the service_reaper_frequency in nagios.cfg. Decrease it in 
> steps of 2 until processes stop queuing up (that's when Nagios empties 
> the pipe often enough for checks to get through).
> 
> If it doesn't work, you'll need to split your nagios setup in smaller 
> chunks or pay me a fat load of money to implement the thread-based or 
> multiplexing checking model. Either way should work, really. ;)
> 


Currently trying 3 as the service reaper frequency, will try 1 on both the
collectors and the central node and see how that goes.

Are there other config file settings that I should be changing to optimise the
central servers processing of checks?



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
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