<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <TITLE>Re: [Nagios-users] Segmentation Fault</TITLE> </HEAD> <BODY>  Have you tried running the plugins in question from the command line as the nagios user? As host checks are never run _until_ a service on that host fails, there could be something inherently wrong with the execution of the plugin. If you see segfaults when running it from the command line then I would suggest using truss with -fea to dig deeper. Chances are it can't open or find a file or library it needs when run as the nagios user. -- Marc -----Original Message----- From: Jake Burns <jburns@sag.org> To: nagios-users@lists.sourceforge.net <nagios-users@lists.sourceforge.net> Sent: Tue Nov 11 17:38:58 2003 Subject: [Nagios-users] Segmentation Fault Hi, I'm running Nagios 1.1 with Nagios Plugins 1.3.1 under Solaris 8/SPARC. Host/service checks run fine until a check fails. When the host/service becomes available again Nagios never reports it as being UP. Instead it keeps reporting it as DOWN and I get Segmentation Fault messages every time the plugin runs from Nagios (running in the foreground). This behavior happens using both a standard Nagios plugin (check_http) and with a custom plugin I wrote. I've searched the documentation and FAQ but found no mention of this particular problem. Any suggestions, information, or advice would be greatly appreciated. Thanks JB ------------------------------------------------------- This SF.Net email sponsored by: ApacheCon 2003, 16-19 November in Las Vegas. Learn firsthand the latest developments in Apache, PHP, Perl, XML, Java, MySQL, WebDAV, and more! <A HREF="http://www.apachecon.com/">http://www.apachecon.com/</A> _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net <A HREF="https://lists.sourceforge.net/lists/listinfo/nagios-users">https://lists.sourceforge.net/lists/listinfo/nagios-users</A> ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null </BODY> </HTML>