On Mon, 3 Jul 2006, Michael T. Halligan wrote: > Nagios seems to have been very unstable the past couple of weeks. The > only change I've made is upgrading from 2.2 to 2.4. It could just be > that I have > some bad configuration options, but I'm not sure. I just had a server > go down for an hour, and Nagios never caught it. In general, since > upgrading to 2.0 > Nagios seems very slow on catching broken services/hosts, but usually > checks them (not always). I look at my status overview right now, and > Nagios > says Last Check for almost every service is two days old. Any ideas > on what I'm doing wrong? > > Here's my Nagios log without comments or blank lines
Unfortunatly there is no log. That happened to be a config file. Go over the logs and start looking for odd things. First thing first. Is Nagios actually running? Then check if there is just one nagios daemon. <voiceover>There can be only one!</voiceover> Hugo. -- I hate duplicates. Just reply to the relevant mailinglist. [EMAIL PROTECTED] http://hvdkooij.xs4all.nl/ Don't meddle in the affairs of magicians, for they are subtle and quick to anger. 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 Nagios-users@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