Date: Thu, 24 Sep 2009 16:14:59 -0500 From: Scott Lambert <lambert@lambertfam.org> To: Tim Kientzle <kientzle@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: Nagios SIGSEGV on FreeBSD 8 Message-ID: <20090924211459.GD4858@sysmon.tcworks.net> In-Reply-To: <4ABAF113.9030904@freebsd.org> References: <20090922212905.GA77503@sysmon.tcworks.net> <4ABAF113.9030904@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Sep 23, 2009 at 09:09:55PM -0700, Tim Kientzle wrote: > Scott Lambert wrote: > >I've posted this to FreeBSD-ports and Nagios-Users without a nibble. > > > >[New Thread 28326280 (LWP 100051)] > >[New Thread 28301140 (LWP 100222)] > >(gdb) bt > >#0 0x0807fe8b in get_next_comment_by_host () > >#1 0x08080940 in delete_host_acknowledgement_comments () > >#2 0x28331180 in ?? () > >#3 0x4aaac053 in ?? () > >#4 0x080cc394 in __JCR_LIST__ () > > Build with debug symbols and try again; maybe you can get > more detail. Also, check a couple of core dumps to > see if it's crashing in the same place; that might > also give a clue. I rebuilt nagios and did not strip the installed binaries to get that backtrace. What else would I need to do? Rebuild the OS with a knob in /etc/src.conf? I suppose I would also need to rebuild and reinstall any ports on which nagios depends. > Do the "New Thread" messages mean that Nagios is running > multiple threads? If so, I wonder what the other > thread is doing? I have theorized that to be the case. I really don't know how to find out what the other thread is doing. With my backlog of work at the moment, I'm probably just going to be happy with the workaround/bandaid of disabling "J" in malloc options. Maybe I will be able to get back to it in a month or three. I really do appreciate the replies I have gotten. -- Scott Lambert KC5MLE Unix SysAdmin lambert@lambertfam.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090924211459.GD4858>