OS is FreeBSD (5.4 i think?) and Nagios version is 2.0b4....not using any extra plugins or anything.<br><br>
<div><span class="gmail_quote">On 3/8/06, <b class="gmail_sendername">Marc Powell</b> <<a href="mailto:marc@ena.com">marc@ena.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><br><br>> -----Original Message-----<br>> From: <a href="mailto:nagios-users-admin@lists.sourceforge.net">
nagios-users-admin@lists.sourceforge.net</a> [mailto:<a href="mailto:nagios-users-">nagios-users-</a><br>> <a href="mailto:admin@lists.sourceforge.net">admin@lists.sourceforge.net</a>] On Behalf Of Ryan Whalen<br>> Sent: Wednesday, March 08, 2006 7:39 AM
<br>> To: <a href="mailto:nagios-users@lists.sourceforge.net">nagios-users@lists.sourceforge.net</a><br>> Subject: [Nagios-users] HOST ALERT: hostabc;DOWN;SOFT;1;Segmentation<br>fault<br>><br>> Last night I received three alerts from devices that were down. The
<br>only<br>> service I am monitoring is ping. Instead of how it normally indicates<br>it<br>> didnt receive a response, or timed out, the problem was identified as<br>a<br>> "Segmentation Fault":<br>>
<br>><br>> [03-08-2006 00:37:50] HOST ALERT: host_1;DOWN;SOFT;1;Segmentation<br>fault<br>><br>><br>> Any ideas what a segmentation fault means? it seems like a problem<br>with<br>> the nagios box and not the monitoring host..
<br><br><a href="http://www.google.com/search?hs=NoO&hl=en&lr=&client=firefox-a&rls=org.m">http://www.google.com/search?hs=NoO&hl=en&lr=&client=firefox-a&rls=org.m</a><br>ozilla%3Aen-US%3Aofficial&q=segmentation+fault&btnG=Search
<br><br>Consider it a program crash. What OS, plugin and nagios versions are you<br>using? This could be interesting to troubleshoot. My feeling is that<br>it's /bin/ping that is segfaulting when the site is down. I would have
<br>expected nagios to report a different kind of error if the plugin<br>crashed (i.e. check of service foo on host bar did not exit properly). I<br>think the only way you're going to be able to narrow it down is to try<br>
the check_ping command and using /bin/ping directly when you see this to<br>see which it is.<br><br>The only seemingly relevant mention I can find of a check_ping segfault<br>is at the bottom of this thread --<br><br><a href="http://64.233.179.104/search?q=cache:Svba1PNB27oJ:www.nagiosexchange.org">
http://64.233.179.104/search?q=cache:Svba1PNB27oJ:www.nagiosexchange.org</a><br>/nagiosplug-devel.31.0.html%3F%26tx_maillisttofaq_pi1%255Bmode%255D%3D1%<br>26tx_maillisttofaq_pi1%255BshowUid%255D%3D15650+nagios+check_ping+segfau
<br>lt&hl=en&gl=us&ct=clnk&cd=1&client=firefox-a<br><br>Andreas Ericsson was troubleshooting a segfault issue but it isn't clear<br>whether that was check_ping segfaulting or /bin/ping.<br><br>Not much help I know but it's all I can offer.
<br><br>--<br>Marc<br><br><br>-------------------------------------------------------<br>This SF.Net email is sponsored by xPML, a groundbreaking scripting language<br>that extends applications into web and mobile media. Attend the live webcast
<br>and join the prime developer group breaking into this new coding territory!<br><a href="http://sel.as-us.falkag.net/sel?cmdlnk&kid0944&bid$1720&dat1642">http://sel.as-us.falkag.net/sel?cmdlnk&kid0944&bid$1720&dat1642
</a><br>_______________________________________________<br>Nagios-users mailing list<br><a href="mailto:Nagios-users@lists.sourceforge.net">Nagios-users@lists.sourceforge.net</a><br><a href="https://lists.sourceforge.net/lists/listinfo/nagios-users">
https://lists.sourceforge.net/lists/listinfo/nagios-users</a><br>::: Please include Nagios version, plugin version (-v) and OS when reporting any issue.<br>::: Messages without supporting info will risk being sent to /dev/null
<br></blockquote></div><br>