Nagios3.0b4 : shutdown after a few minutes

hindrek murdsalu hindrek.murdsalu at tallink.ee
Fri Sep 28 15:36:47 CEST 2007


There you go:

Program received signal SIGABRT, Aborted.
[Switching to Thread 47740967242496 (LWP 29865)]
0x00002b6b8ef2c535 in raise () from /lib64/libc.so.6
(gdb) bt
#0  0x00002b6b8ef2c535 in raise () from /lib64/libc.so.6
#1  0x00002b6b8ef2d990 in abort () from /lib64/libc.so.6
#2  0x00002b6b8ef636db in __libc_message () from /lib64/libc.so.6
#3  0x00002b6b8ef688fe in malloc_printerr () from /lib64/libc.so.6
#4  0x00002b6b8ef6b60d in _int_realloc () from /lib64/libc.so.6
#5  0x00002b6b8ef6c8b8 in realloc () from /lib64/libc.so.6
#6  0x0000000000430192 in grab_servicegroup_macros (sg=0x72f820) at
../common/macros.c:581
#7  0x00000000004304d1 in grab_service_macros (svc=0x7a6f80) at
../common/macros.c:515
#8  0x00000000004175cc in run_async_service_check (svc=0x7a6f80,
check_options=<value optimized out>, latency=0.129,
    scheduled_check=1, reschedule_check=1, time_is_valid=<value
optimized out>, preferred_time=0x7fff1c6e44c8)
    at checks.c:393
#9  0x00000000004192b8 in run_scheduled_service_check (svc=0x7a6f80,
check_options=0, latency=0) at checks.c:250
#10 0x0000000000427379 in handle_timed_event (event=0x6e6a10) at
events.c:1170
#11 0x0000000000427b8e in event_execution_loop () at events.c:1055
#12 0x000000000041059c in main (argc=<value optimized out>, argv=<value
optimized out>) at nagios.c:788

-----Original Message-----
From: nagios-devel-bounces at lists.sourceforge.net
[mailto:nagios-devel-bounces at lists.sourceforge.net] On Behalf Of Ethan
Galstad
Sent: 28. september 2007. a. 15:53
To: Nagios Developers List
Subject: Re: [Nagios-devel] Nagios3.0b4 : shutdown after a few minutes

These are the symptoms of Nagios segfaulting.  The process dies, but the

status file remains behind, so the CGIs think everything is fine.

Can either or you run the unstripped nagios binary (as a foreground 
process) under gdb, like so:

gdb --args /path/to/unstripped/nagios /usr/local/nagios/etc/nagios.cfg

Type 'r' in gdb to start the program running.  When it segfaults you 
should be able to use 'bt' to get a backtrace.  Send me that output, as 
it will help me solve the problem.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/




More information about the Developers mailing list