Nagios Support Forum

Hi,

I'm experiencing a segfault w/ Nagios 3.0rc1 in
process_check_result_queue(), it dies just a few seconds after starting
up the Nagios daemon. Backtrace attached.

tia,
Tobias


(gdb) r
Starting program: /usr/sbin/nagios3 /etc/nagios3/nagios.cfg
Failed to read a valid object file image from memory.
[Thread debugging using libthread_db enabled]
[New Thread 1077336608 (LWP 3529)]

Nagios 3.0rc1
Copyright (c) 1999-2007 Ethan Galstad (http://www.nagios.org)
Last Modified: 12-17-2007
License: GPL

Nagios 3.0rc1 starting... (PID=3529)
Local time is Thu Jan 03 16:01:09 CET 2008
[New Thread 1081805744 (LWP 3533)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1077336608 (LWP 3529)]
0x0808450c in process_check_result_queue (dirname=0x80d4078
"/var/spool/nagios3/checkresults") at utils.c:2244
2244 utils.c: No such file or directory.
in utils.c
(gdb) bt
#0 0x0808450c in process_check_result_queue (dirname=0x80d4078
"/var/spool/nagios3/checkresults") at utils.c:2244
#1 0x08062749 in reap_check_results () at checks.c:149
#2 0x08070227 in handle_timed_event (event=0x80f1c20) at events.c:1235
#3 0x080708a8 in event_execution_loop () at events.c:941
#4 0x08058a29 in main (argc=Cannot access memory at address 0xf0
) at nagios.c:795
(gdb) kill
Kill the program being debugged? (y or n) y
(gdb) q







This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]