<tt>nagios-users-bounces@lists.sourceforge.net schrieb am 02.09.2008 15:37:47: > # of Hosts Monitored: 322 > # of Services Monitored: 35 > > The localhost.cfg comes with a default process check with the values > 250+ for warnings and 400+ for critical. Usually about twice an > hour from checking the event log I get this message: > > [09-02-2008 07:02:48] SERVICE ALERT: NAGIOS;Total Processes;WARNING; > SOFT;1;PROCS WARNING: 370 processes with STATE = RSZDT > > It seems to me the machine itself is powerful enough to execute this > many checks without even breaking a sweat. Were these defaults > configured in the thinking that there should never be that many processes? > > I'm by no means a Linux or Nagios expert and I was hoping someone > could explain more of the thinking behind this check than what I > see. I can obviously just bump the numbers up but I want to make > sure that I'm not ignoring something obvious that may have unwanted > results after the fact. Should I use these numbers I see here as > the basis for my new thresholds? </tt> <tt>These thresholds were never meant to be any upper limit, the maximum number</tt> <tt>of concurrent checks your box can handle solely depends on your hardware.</tt> <tt>See it more like an "if you have a nagios installation which produces</tt> <tt>that many concurrent checks - then you should know by now how to</tt> <tt>change this behaviour" ;-)</tt> <tt>But then - I fail to see how your setup with 322 host and only 35(?) service</tt> <tt>checks could produce that many processes. Maybe it'll be a good idea to</tt> <tt>doublecheck what's going on there.</tt> <tt>S</tt> GFKL Financial Services AG Vorstand: Dr. Peter Jänsch (Vors.), Jürgen Baltes, Dr. Till Ergenzinger, Dr. Tom Haverkamp Vorsitzender des Aufsichtsrats: Dr. Georg F. Thoma Sitz: Limbecker Platz 1, 45127 Essen, Amtsgericht Essen, HRB 13522