<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv=Content-Type content="text/html; charset=us-ascii"> <meta name=Generator content="Microsoft Word 12 (filtered medium)"> <style>  </style>  </head> <body lang=EN-US link=blue vlink=purple> <div class=Section1> Hello all,<o:p></o:p> <o:p> </o:p> I’m running Nagios 3.0.6 compiled from unmodified source on CentOS 5.2 x86_64. I noticed that notifications stopped early this morning, and the logs said Nagios caught SIGSEGV, and it was shutting down. Nagios doesn’t appear to go all the way down, though. All the CGIs still work, but no checks are being performed. There is a lock file, and nagios.cmd still exists. The first one I saw happened after Nagios had been running fine for a while, but the same thing happens if I issue a killall –SIGSEGV naigios command, defunct processes and all. This is what I got after I did the killall, then a service nagios start, then another killall.<o:p></o:p> <o:p> </o:p> # ps -fC nagios<o:p></o:p> UID PID PPID C STIME TTY TIME CMD<o:p></o:p> nagios 1469 1 0 10:47 ? 00:00:00 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg<o:p></o:p> nagios 1470 1469 0 10:47 ? 00:00:00 [nagios] <defunct><o:p></o:p> nagios 1918 1 6 10:51 ? 00:02:55 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg<o:p></o:p> nagios 16350 1918 0 11:25 ? 00:00:00 /usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg<o:p></o:p> nagios 16351 16350 0 11:25 ? 00:00:00 [nagios] <defunct><o:p></o:p> <o:p> </o:p> Thanks to Paul Weaver’s suggestion earlier this month, I’ve got a failover Nagios server running. Once a minute, it checks the primary server. I didn’t set the conditions for failing over correctly, so it didn’t take over in this case, though it sometimes does for a moment when I restart the primary Nagios after I’ve updated its object configuration files. The output of its check_nagios command looks like this after the primary Nagios gets a SIGSEGV:<o:p></o:p> <o:p> </o:p> # ./check_by_ssh -H primaryhostname --command='/usr/local/nagios/libexec/check_nagios --filename=/usr/local/nagios/var/status.dat --expires=60 --command=nagios'<o:p></o:p> NAGIOS OK: 3 processes, status log updated 228 seconds ago<o:p></o:p> <o:p> </o:p> When I fixed the expiration, it gave me a warning state and I could’ve failed over on that. However, the way I did things, the failover server thought everything was all right. So, that’s my problem to fix, but shouldn’t Nagios shut all the way down as well?<o:p></o:p> <o:p> </o:p> Thanks!<o:p></o:p> -Chris<o:p></o:p> </div> <html> <head> <meta http-equiv="Content-Language" content="en-us"> <meta name="GENERATOR" content="Microsoft FrontPage 5.0"> <meta name="ProgId" content="FrontPage.Editor.Document"> <meta http-equiv="Content-Type" content="text/html; charset=windows-1252"> <title>New Page 1</title> </head> <body> This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed and may contain information that is non-public, proprietary, privileged, confidential, and exempt from disclosure under applicable law or may constitute as attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, notify us immediately by telephone and (i) destroy this message if a facsimile or (ii) delete this message immediately if this is an electronic communication. Thank you. </body> </html> </body> </html>