A large number down hosts will adversely affect the scheduling of active checks.
This is because host checks: -supercedes all other scheduled activiy -are performed serially -includes a host check of the device's parent(s) -are performed for every failed service check You can minimize this effect a little by disabling all active checks except one for hosts that you know will be remain down for a while. (that way it's not host-checked after every one of it's services, just the one) -----Original Message----- From: Phil Manuel [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 12, 2006 3:05 PM To: [email protected] Subject: [Nagios-users] Scheduler not running Hi, We are running Nagios 2.3.1 on Solaris, downloaded from blastwave. Recently we have noticed that the scheduler halts and doesn't process any commands. We can see events going into the log still. Our network isn't very big, only comprising 20 devices. So it should be handling this easily. The load on the box at the time was 1.2. The service checks are split equally between active and passive checks. We have however taken down half of the network to rebuild it. What is the likely cause ? I admit i haven't looked int he Nagios log file yet for any errors. Thanks ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Nagios-users mailing list [email protected] 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
