Thanks, According to the 3.0 documentation, you don't need to re-compile Nagios to get the debug symbols - is this right?
"Debugging information can now be written to a separate debug file, which is automatically rotated when it reaches a user-defined size. This should make debugging problems much easier, as you don't need to recompiled Nagios." I've enabled the "allow Nagios to create core dumps" option (can't remember what it's called atm), and the notes for that directive do say that even with that option enabled, Nagios may not create a core dump, which it doesn't. I'll try strace/ktrace, but how do you get Nagios to run in the foreground, as soon as you start it with "-d" it goes to the background anyway? Thanks, Andy On Sun, 07 Oct 2007 11:32:57 -0400, "Brian A. Seklecki" <[EMAIL PROTECTED]> wrote: > On Sun, 2007-10-07 at 16:00 +0100, [EMAIL PROTECTED] > wrote: >> Hi >> I thought originally it was because the server was running low on > available > > You'll want to compile the binary with debugging symbols so that you can > trace core dumps. You'll also want to run the daemon in the foreground > under strace(8)/ktrace(8) with debugging output. > > ~BAS > >> memory (as it had ~11MB free), but now, it's got 134MB free, and when > you >> run Nagios, it'll verify the configs fine, then when you start it up, it > > > > !DSPAM:37,4708fc2f7681769792324! ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Nagios-users mailing list [email protected] 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
