<table cellpadding=3 cellspacing=0 border=0 width=100% bgcolor=white><tr valign=top><td width=100%><font size=2 color=black>Greetings,<BR><BR>I am experiencing a strange behaiviour for nagios and apan.<BR>I'de run nagios for a long time, using the standard plugins (check_host_alive for 50 services), and my system<BR>(CPU 1GHz, RAM 512, swap 512) was very stable.<BR>not untill I've installed apan (155 services) that the server starts chewing memory so fast that the system becomes cloged and the only way to regain control for the system is to REBOOT.<BR>I've read and practiced a lot with the tunning paramers of nagios, and reached a level where these parameters<BR>max_concurrent_checks (for concurrency)<BR>service_reaper_freq<BR>size of rrd files (to prevent caching of large databse files)<BR>added the -m to snmp_get (based on a recommendation of one of the users) to disable the loading of the mib with each call<BR><BR>but all with no help. I can't put my hands on the problem.
<BR>the system starts memory usage in almost a linear fashion, untill the free section of buffers/cache starts comming down, and the systems goes to swap till it exhast all system Memory.<BR>it is only the difference between the concurrency factor (max_concurrent_checks) that slows down the rate at which memory is lost.<BR><BR>its a production system, and I really appriciate help<BR><BR>thanks,<BR><BR><BR><BR><BR><br></font></td></tr></table><p><hr><a href=http://www.smileycentral.com/?partner=ZSeef003 target=_blank><img src=http://imgfarm.com/images/funwebproducts/ads/20030808_smiley_sig4.gif width=430 height=72 border=0></a>