On Apr 4, 2007, at 1:45 PM, Israel Brewster wrote: > A while ago I installed Nagios 2.4 on a somewhat minimal (don't > remember the specs, but old) OpenBSD 4.0 box. For the most part, it > appears to work fine- latency is a nice low .328 seconds on average, > with an average execution time of 4 seconds. The execution time might > be a bit high, but it doesn't appear to cause any issues. The only > problem is that, from time to time, Nagios will simply die. The logs > show normal operation right up to the time it dies, and there is no > real indication that it isn't running, except that the last check > times don't change and a look at the process list shows no Nagios > processes. Now, I have written a script that checks for this and > restarts Nagios if necessary, but it would of course be preferable to > stop it from dying in the first place. I realize that this isn't much > information to go on (more presumably available on specific request), > but I was wondering if anyone had seen similar behavior and could > give me an idea as to how to fix it? Thanks
You wouldn't happen to be running it with a database back-end would you? I had an identical problem on Debian while using the Nagios/ Postgres package. There seems to be some kind of bug somewhere in this Debian package that causes Nagios to frequently and silently die. Once I removed the Postgres back-end, Nagios became stable again. -- Kurt Yoder The Richard Group ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ 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
