nagios.cmd denial of service

[Marcel]

Hi list,

I'm a huge nagios fan, using it about 3 years now. Need to know how to get
around a problem.

This is for my central nagios instance alone. (nagios 2.9 + ndomod)

The problem appears to be related to the number of passive result checks
being cached at CHKBUF variables. When the problem occurs,
USEDCHKBUF=HIGHCHKBUF=TOTALCHKBUF=40960(40KB), then a restart would bring
back Nagios to it's normal operation. Also, for diagnostic's relevancy sake,
it was found that a malign script was flooding Nagios with 450 to 500
passive check results per minute.

If I'm making the correct assertions, Nagios configured with
command_check_interval=-1, and with LOTS of passive checks coming through
nagios.cmd, there is a conjunction of factors still unknown to me that
causes Nagios to hang, perhaps because of Nagios not being able to reaper
services frequently enough (service_reaper_frequency=1. Could not set it to
0, though), Nagios CMD Buffers remains stable, not reaching TOTBUFs, and not
increasing HIGHBUFs. As a initial troubleshooting, I've unset sleep_time
variable. Could it be done to service_reaper_frequency as well or it would
use default values?

Well, I'm just writing this down to see if someone had the same problems
regarding CHKBUFs not being consumed.

Thanks you in advance,

Marcel Mitsuto.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20080616/d9c3ef0d/attachment.html>
-------------- next part --------------
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
-------------- next part --------------
_______________________________________________
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