Re: [Nagios-devel] Some errors with SIGSEGV
Posted: Wed Mar 28, 2007 7:55 am
Quoting [email protected]:
> Hello developers,
> Hendrik supposed me to build the nagios source without the option '-O2'. I
> have done this, but nothing changed. The SIGSEGV also happens in Version
> 3.0a2 without the '-O2' option.
> Output from gdb:
> #0 0xb7e43e84 in mallopt () from /lib/tls/libc.so.6
> #1 0xb7e42dcb in free () from /lib/tls/libc.so.6
> #2 0x080774ac in my_free ()
> #3 0x08073d4f in clear_volatile_macros ()
> #4 0x0806c92c in log_host_event ()
> #5 0x080706a8 in handle_host_state ()
> #6 0x0805bfa8 in process_host_check_result_3x ()
> #7 0x0805bc42 in handle_async_host_check_result_3x ()
> #8 0x08057533 in reap_check_results ()
> #9 0x0806ac7d in handle_timed_event ()
> #10 0x0806aaea in event_execution_loop ()
> #11 0x080554f1 in main ()
I think this is a problem with glibc6 version (2.3.2.ds1-22sa) in =20
debian sarge and the NPTL. I confirm the situation on a Debian Sarge =20
machine. I got no errors with the following workaround:
export LD_ASSUME_KERNEL=3D2.4.15
/usr/local/nagios/bin/nagios /usr/local/nagios/etc/nagios.cfg
The /debian/FAQ from glibc6 contains the following section:
The application should continue to run for now, but when the warning message
is printed use of the NPTL threading library, and other new kernel-2.6
features, it's worth trying to set environment variable LD_ASSUME_KERNEL=3D2=
.4.1
(switch to LinuxThreads instead of NPTL).
Debian using glibc-2.3 Ubuntu 2.4, RHEL5 glib-2.5. Perhaps this could =20
be a reason? See the debian changelog of glibc6:
http://packages.debian.org/changelogs/p ... exp6/chan=
gelog
Best regards
Herbert Straub
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]
> Hello developers,
> Hendrik supposed me to build the nagios source without the option '-O2'. I
> have done this, but nothing changed. The SIGSEGV also happens in Version
> 3.0a2 without the '-O2' option.
> Output from gdb:
> #0 0xb7e43e84 in mallopt () from /lib/tls/libc.so.6
> #1 0xb7e42dcb in free () from /lib/tls/libc.so.6
> #2 0x080774ac in my_free ()
> #3 0x08073d4f in clear_volatile_macros ()
> #4 0x0806c92c in log_host_event ()
> #5 0x080706a8 in handle_host_state ()
> #6 0x0805bfa8 in process_host_check_result_3x ()
> #7 0x0805bc42 in handle_async_host_check_result_3x ()
> #8 0x08057533 in reap_check_results ()
> #9 0x0806ac7d in handle_timed_event ()
> #10 0x0806aaea in event_execution_loop ()
> #11 0x080554f1 in main ()
I think this is a problem with glibc6 version (2.3.2.ds1-22sa) in =20
debian sarge and the NPTL. I confirm the situation on a Debian Sarge =20
machine. I got no errors with the following workaround:
export LD_ASSUME_KERNEL=3D2.4.15
/usr/local/nagios/bin/nagios /usr/local/nagios/etc/nagios.cfg
The /debian/FAQ from glibc6 contains the following section:
The application should continue to run for now, but when the warning message
is printed use of the NPTL threading library, and other new kernel-2.6
features, it's worth trying to set environment variable LD_ASSUME_KERNEL=3D2=
.4.1
(switch to LinuxThreads instead of NPTL).
Debian using glibc-2.3 Ubuntu 2.4, RHEL5 glib-2.5. Perhaps this could =20
be a reason? See the debian changelog of glibc6:
http://packages.debian.org/changelogs/p ... exp6/chan=
gelog
Best regards
Herbert Straub
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]