Nagios 1.2 - Load Issue

[Tom Brown]

Hi

I'm currently monitoring around 40 hosts and 200 services using a box 
with 2xp3 1Ghz CPU's and 1agig RAM. Everything works OK, bar trending 
but need to look at that seperately.

I have noticed that the load on this box steadily increased until the 
nagios process is either restarted or reloaded. Please see graph link 
for an example.

http://www.ng23.net/graph.png

has anyone else seen this type of behaviour and is there a memory leak 
or some other such issue with 1.2 ?

an exapmle of a top would be

CPU states:  cpu    user    nice  system    irq  softirq  iowait    idle
            total    2.2%    0.0%   64.8%   0.0%     0.0%    0.8%   31.8%
            cpu00    1.1%    0.0%   64.8%   0.0%     0.1%    0.0%   33.7%
            cpu01    3.3%    0.0%   64.8%   0.0%     0.0%    1.7%   29.9%
Mem:  1025392k av,  952196k used,   73196k free,       0k shrd,   65360k 
buff
                     715184k actv,  151796k in_d,   21488k in_c
Swap: 2048276k av,  881904k used, 1166372k free                  709040k 
cached

   PID USER     PRI  NI  SIZE  RSS SHARE STAT %CPU %MEM   TIME CPU COMMAND
26216 nagios    20   0  894M  76M  1884 S     7.2  7.6 264:55   0 nagios
24549 nagios    24   0  894M  76M  1884 S     2.3  7.6   0:00   0 nagios
24554 nagios    24   0  894M  76M  1884 S     2.3  7.6   0:00   1 nagios
24557 nagios    24   0  894M  76M  1884 S     2.1  7.6   0:00   0 nagios
24552 nagios    24   0  894M  77M  2024 S     1.7  7.7   0:00   1 nagios

any ideas ?

thanks


-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
_______________________________________________
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