On Tue, 12 Aug 2008 15:53:11 -0500, "Marc Powell" <[EMAIL PROTECTED]> wrote:
>> Hello there, > > >> Aug 12 13:18:09 colorado nagios: Nagios 2.10 starting... (PID=23650) >> >> Aug 12 13:25:58 colorado nagios: LOG VERSION: 2.0 >> >> Aug 12 13:25:58 colorado nagios: Finished daemonizing... (new >PID=23651) >> >> Aug 12 13:26:10 colorado nagios: Caught SIGSEGV, shutting down... >> >> >> >> Why can't I get nagios to monitor itself? In other words, why can't I >get >> nagios to monitor the server that it is running from? > >Getting Nagios to monitor the machine it's running on is actually the >very simplest case and very straight forward. What config changes did >you make between when it was working and not, specifically? The SIGSEGV >is interesting and you might consider running Nagios in debug mode >(you'll need to recompile) to find out generally what it's doing at the >segfault. Alternately, if you're familiar with gdb, you could use that. I've also found strace to be a big help for random crashes. Somebody on the irc channel had an issue with nagios faulting right on start up. strace pointed the issue to be a "big file" issue. The performance data file was 2GB in size, and LFS wasn't enabled in the kernel. strace /usr/local/nagios/bin/nagios /usr/local/nagios/etc/nagios.cfg Adjusting the paths obviously :) -- Jon Angliss ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ 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
