<br><br><div><span class="gmail_quote">On 4/4/07, <b class="gmail_sendername">Israel Brewster</b> <<a href="mailto:israel@frontierflying.com">israel@frontierflying.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
A while ago I installed Nagios 2.4 on a somewhat minimal (don't<br>remember the specs, but old) OpenBSD 4.0 box. For the most part, it<br>appears to work fine- latency is a nice low .328 seconds on average,<br>with an average execution time of 4 seconds. The execution time might
<br>be a bit high, but it doesn't appear to cause any issues. The only<br>problem is that, from time to time, Nagios will simply die. The logs<br>show normal operation right up to the time it dies, and there is no<br>
real indication that it isn't running, except that the last check<br>times don't change and a look at the process list shows no Nagios<br>processes. Now, I have written a script that checks for this and<br>restarts Nagios if necessary, but it would of course be preferable to
<br>stop it from dying in the first place. I realize that this isn't much<br>information to go on (more presumably available on specific request),<br>but I was wondering if anyone had seen similar behavior and could<br>
give me an idea as to how to fix it? Thanks</blockquote><div><br>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.
<br><br>cheers<br><br>Rob<br></div><br></div>