I'm having the same problem with my installation of 2.7 on OpenBSD 4.0. It dyes silently.
I do notice in the logs it tries to restart after and can't find the .pid file. [1174798800] LOG ROTATION: DAILY [1174798800] LOG VERSION: 2.0 Then it dies, I have to manually restart it. Sometimes this shows up in the log also [1168546261] /var/run/nagios/nagios.pid does not exist (ENOENT) I then look for the /var/run/nagios/ dir and its not there, so I Mkdir /var/run/nagios/ Chown _nagios:_nagios And restart the daemon. My guess Israel, is that you got the installation from the packages on the OpenBSD website, which has been packaged up as chroot version. I did the same, then upgraded to 2.7, but followed the dir structure of the chroot installation and I'm still having the problem. Does anyone know if there is a problem running Nagios in chroot? Or the fix for our issue here? -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rob Blake Sent: Wednesday, April 04, 2007 3:35 PM To: Israel Brewster Cc: Nagios Users mailinglist Subject: Re: [Nagios-users] Nagios dying On 4/4/07, Israel Brewster <[EMAIL PROTECTED]> 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 As you say not much to go on. Obviously something is causing Nagios to die. I've just had a quick look at the change list for later releases > 2.4 and there are some bug fixes for seg faults which presumably could cause Nagios to die silently. It may be worth updating to the latest and greatest version to see if this solves your issue. If this isn't possible, then I guess an inspection of the Nagios log file to see what it was doing last before it died is in order. cheers Rob ------------------------------------------------------------------------- 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 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
