I am running Nagios 2.9 with ndoutils 1.4b3 an experiencing reproducable problems when scheduling downtimes. After scheduling a HOSt downtime either from CGI of echo-to-nagios.cmd everything is ok. But after, if I either: - restart nagios - or submit a further host-downtime Nagios crashes with a SEGFAULT.
The only workaround to get nagios running again, is to delete the lines from downtime.dat (which have been added correctly). The worst thin on my problem is, that this behaviour can be reproduced every time on the production system, but I've not been able to reproduce it on a test-system with exactly the same versions. Since it's not possible to do very excessive debugging on the production system, the following gdb-trace is all I have: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1208759520 (LWP 31380)] 0x004c2963 in strlen () from /lib/tls/libc.so.6 (gdb) (gdb) bt #0 0x004c2963 in strlen () from /lib/tls/libc.so.6 #1 0x00f5f8e5 in ndo_escape_buffer () from /usr/lib/nagios/ndoutils/ndomod.o #2 0x00f59505 in ndomod_broker_data () from /usr/lib/nagios/ndoutils/ndomod.o #3 0x0805660a in neb_make_callbacks () #4 0x08055f0b in broker_timed_event () #5 0x0806581b in add_event () #6 0x0806590a in schedule_new_event () #7 0x080978f1 in register_downtime () #8 0x08097cf6 in schedule_downtime () #9 0x08062ca2 in cmd_schedule_downtime () #10 0x08063efb in check_for_external_commands () #11 0x08066f7e in event_execution_loop () #12 0x0805477b in main () any suggestions ? thx in advance, Wolfgang Powisch ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Nagios-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null
