3.0b6 crashes with SIGSEGV

Boeckman, Matthew mboeckman at servicemagic.com
Tue Nov 6 18:53:48 CET 2007


 
> -----Original Message-----
> From: Ethan Galstad [mailto:nagios at nagios.org] 
> Sent: Tuesday, November 06, 2007 10:52 AM
> To: Boeckman, Matthew
> Subject: Re: [Nagios-devel] 3.0b6 crashes with SIGSEGV
> 
> Boeckman, Matthew wrote:
> [snip]
> >> Can you run the unstripped nagios binary under gdb and do 
> a backtrace 
> >> when it segfaults?  That will help track down the source of the 
> >> segfault.
> >>
> >>
> >> cd <nagios-src>/base
> >> gdb --args ./nagios /usr/local/nagios/etc/nagios.cfg r
> >>
> >> When it segfaults, do a backtrace...
> >>
> >> bt
> >>
> >> and send the output.
> >>
> > 
> > Sure can!
> > 
> > Warning: Host 'xxxxx' has no services associated with it!
> > [New Thread -1208861808 (LWP 3432)]
> > 
> > Program received signal SIGSEGV, Segmentation fault.
> > [Switching to Thread -1208858416 (LWP 3429)] 0x08082ddb in 
> > process_check_result_queue (dirname=0x9994090
> > "/usr/local/nagios/var/spool/checkresults")
> >     at utils.c:2195
> > 2195            while((dirfile=readdir(dirp))!=NULL){
> > (gdb) bt
> > #0  0x08082ddb in process_check_result_queue (
> >     dirname=0x9994090 "/usr/local/nagios/var/spool/checkresults") at
> > utils.c:2195
> > #1  0x08060670 in reap_check_results () at checks.c:145
> > #2  0x0806e470 in handle_timed_event (event=0x99b95a0) at 
> > events.c:1238
> > #3  0x0806eaf8 in event_execution_loop () at events.c:944
> > #4  0x0805629c in main (argc=Cannot access memory at address 0x1d8
> > ) at nagios.c:779
> > 
> >>
> 
> That's an odd place to have an error.  I don't see a problem 
> with the code, as dirp is being checked for errors (NULLness) 
> before it is used in readdir().
> 
> What OS/kernel are you running Nagios under?  Has anyone else 
> run into this?
> 

This is a stock Centos5 install 5.0.0.el5.centos.2 with 2.6.18-8.el5.
Single processor 2 GB ram dell box. 

Anything else I can dig into for you? I was thinking of pulling down
3.0b5 and seeing if I have the same issue (if that helps/make sense?).

3.0b6 was configured with: 

/configure --prefix=/usr/local/nagios --with-cgiurl=/nagios/cgi-bin
--with-htmurl=/nagios -with-command-group=nagcmd
--with-htppd-conf=/usr/local/apache2/conf/ --enable-perlcache
--enable-embedded-perl --disable-statusmap

-------------------------------------------------------------------------
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/




More information about the Developers mailing list