I am currently upgrading from Netsaint 0.0.7 to Nagios 1.0, and I=20
am finding that after Nagios runs for an hour or so, lots of=20
services start getting orphaned. The resources on this box aren't=20
exhausted at all (that I can tell). It tried lowering the=20
max_concurrent_checks from 306 to 200, which helped for a little while. =20
Now it's exhibiting the same behaviour.
The specs for the box are Debian Linux, kernel 2.4.20, PIII 650, 250M. I=
=20
don't go into swap and the load generally stays between 1 and 5. I am=20
montoring 620 services on 95 boxes.
While the services are getting orphaned, the load is pretty low (around=20
1.2). The check latency average shoots way up to 46, and the max to 111.
Another thing I've noticed is that though the max_concurrent_checks is se=
t=20
to 200, the number of processes named "nagios" is greater than that durin=
g=20
the periods when it reports orphans.
Has anyone else experienced this? I searched the FAQ and this mailing=20
list, and didn't find anything.
Please copy my address in replies as I am not currently subscribed.
Thanks,
Geoff
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]