Problem with scheduling of 5000 checks

[Matthias Waltsgott]

Hi all,

to be sure if nagios2 can handle a larger number of checks too, I did some
tests with sample configurations of 3000 and 5000 services with 1 service
per host, so also 3000 and 5000 hosts, host checks disabled. 

Everything worked fine with the 3000-services-config. But when I used 5000
services then some strange things happened. First all the checks were
pending and nagios scheduled all in the queue correctly. 
After the first check was performed nagios marked the check with Status OK
and scheduled it again with normal check interval (in this case 20 min.). 
These services were never checked again, which means, after checking all
services the first time nagios stopped checking any services, since all
lines in the scheduling queue had a next checktime which is in the past. And
they never get rescheduled until a restart or reload of nagios.

It seems as if nagios simply forget to check these services. No error
messages in the event or sys log, load < 1, preflight check of the nagios
without any errors. I used Nagios-2b03, the same situation with Nagios-1.1.

Any idea ? It seems that this behavior only happens if a certain number of
services are reached. Is there any kind of limit for services or something
like this?

It would be great if you could help me, since I want to use nagios in a
larger environment, but with this situation I can't.

Thanks in advance.

Regards from Germany,
Matthias Waltsgott




-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
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