I checked it out and after a restart of nagios, it checks everything right away. Then it stops checking for 30 minutes (before I noticed it had stopped again). Then I restarted it again and it is currently checking everything again.
-----Original Message----- From: Terry [mailto:[EMAIL PROTECTED] Sent: Thursday, October 11, 2007 2:51 PM To: David Fulton Cc: [email protected] Subject: Re: [Nagios-users] Nagios Problem OK, in the web interface, check out the scheduling queue. Here is the relative URL if you have modified the web interface at all: /nagios/cgi-bin/extinfo.cgi?&type=7 On 10/11/07, David Fulton <[EMAIL PROTECTED]> wrote: > I can send command and it works via the web interface. I turned off > performance monitoring globally. I make extensive use of templates. We > have configured 864 service checks on 114 hosts. > > -----Original Message----- > From: Terry [mailto:[EMAIL PROTECTED] > Sent: Thursday, October 11, 2007 2:39 PM > To: David Fulton > Cc: [email protected] > Subject: Re: [Nagios-users] Nagios Problem > > Interesting, how many services (checks)? Did you turn off perf > globally in nagios.cfg or just for a particular service? Can you send > nagios commands via the web interface and have it update the next > schedule service check? > > On 10/11/07, David Fulton <[EMAIL PROTECTED]> wrote: > > I already tried that, It simply stops checking. Once in a while it > > copies the status info from the /tmp directory, but other than that is > > is just a bump on a log. I even thought it could be because I was > > sending performance data to Perfparsed via named pipe and a short perl > > script. But even with that off, it just stops. > > > > -----Original Message----- > > From: Terry [mailto:[EMAIL PROTECTED] > > Sent: Thursday, October 11, 2007 2:11 PM > > To: David Fulton > > Cc: [email protected] > > Subject: Re: [Nagios-users] Nagios Problem > > > > Do the logs show that checks are being performed? Might want to turn > > debugging on in nagios.cfg to get some more information. > > > > On 10/11/07, David Fulton <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > > > I am having serious problems with Nagios v3.04b. For some reason it > > simply > > > stops checking services and hosts. I have looked into this and been > > unable > > > to figure out why. I have played with the check times, service > reaper > > times, > > > timeperiods. I even re-compiled PERL to be non-threading (not a > simple > > task > > > on a system that is already up and running). I am getting frustrated > > and was > > > wondering if anyone out there had similar problems with it. This > > didn't crop > > > up until recently but I am unable to point to any one event that > could > > have > > > caused the problem. > > > > > > > > > > > > Please help > > > David Fulton > > > > > > ------------------------------------------------------------------------ > > - > > > This SF.net email is sponsored by: Splunk Inc. > > > Still grepping through log files to find problems? Stop. > > > Now Search log events and configuration files using AJAX and a > > browser. > > > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > > _______________________________________________ > > > 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 > > > > > > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ 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
