Re: [Nagios-devel] 3.0b6 crashes with SIGSEGV

Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
Locked
Guest

Re: [Nagios-devel] 3.0b6 crashes with SIGSEGV

Post by Guest »

Boeckman, Matthew wrote:
> Just upgraded to 3.0b6 from what was a stable 3.0b3 install. Check of
> the config files comes back fine, but when starting the deamon I get
> after a few moments:
>
> Caught SIGSEGV, shutting down...
>
> I have debug set pretty high but do not see anything jumping out at me
> from the logs as a cause (brief snippet of nagios.debug final few lines
> below) - is there a known issue, or anything more I can provide? I will
> probably roll back to 3.0b3 shortly.
>
> -Matthew
>
> Nagios.debug:
>
> [1194366930.175483] [2048.0] [pid=28012] UNHANDLED MACRO #149! THIS IS A
> BUG!
> [1194366930.175499] [2048.0] [pid=28012] UNHANDLED MACRO #150! THIS IS A
> BUG!
> [1194366930.175512] [2048.0] [pid=28012] UNHANDLED MACRO #151! THIS IS A
> BUG!
> [1194366930.175526] [2048.0] [pid=28012] UNHANDLED MACRO #152! THIS IS A
> BUG!


Well, this is one bug. :-) I'll get this patched in CVS in a moment.


> [1194366930.184171] [016.2] [pid=28012] Moving temp check result file
> '/usr/local/nagios/var/spool/check
> results/checkZWY3uz' to queue file
> '/usr/local/nagios/var/spool/checkresults/cRAAfPr'...
> [1194366930.192109] [016.2] [pid=28011] Moving temp check result file
> '/usr/local/nagios/var/spool/check
> results/checkbx9gcH' to queue file
> '/usr/local/nagios/var/spool/checkresults/cNf2sxz'...
> [1194366930.424821] [008.1] [pid=27982] ** Event Check Loop
> [1194366930.424845] [008.1] [pid=27982] Next High Priority Event Time:
> Tue Nov 6 09:35:31 2007
> [1194366930.424858] [008.1] [pid=27982] Next Low Priority Event Time:
> Tue Nov 6 09:35:31 2007
> [1194366930.424867] [008.1] [pid=27982] Current/Max Service Checks: 7/0
> [1194366930.424888] [008.2] [pid=27982] No events to execute at the
> moment. Idling for a bit...
> [1194366930.424897] [001.0] [pid=27982] check_for_external_commands()
> [1194366930.424909] [064.1] [pid=27982] Making callbacks (type 8)...
> [1194366930.677126] [008.1] [pid=27982] ** Event Check Loop
> [1194366930.677142] [008.1] [pid=27982] Next High Priority Event Time:
> Tue Nov 6 09:35:31 2007
> [1194366930.677154] [008.1] [pid=27982] Next Low Priority Event Time:
> Tue Nov 6 09:35:31 2007
> [1194366930.677162] [008.1] [pid=27982] Current/Max Service Checks: 7/0
> [1194366930.677172] [008.2] [pid=27982] No events to execute at the
> moment. Idling for a bit...
> [1194366930.677181] [001.0] [pid=27982] check_for_external_commands()
> [1194366930.677191] [064.1] [pid=27982] Making callbacks (type 8)...
> [1194366930.928492] [008.1] [pid=27982] ** Event Check Loop
> [1194366930.928509] [008.1] [pid=27982] Next High Priority Event Time:
> Tue Nov 6 09:35:31 2007
> [1194366930.928521] [008.1] [pid=27982] Next Low Priority Event Time:
> Tue Nov 6 09:35:31 2007
> [1194366930.928530] [008.1] [pid=27982] Current/Max Service Checks: 7/0
> [1194366930.928540] [008.2] [pid=27982] No events to execute at the
> moment. Idling for a bit...
> [1194366930.928548] [001.0] [pid=27982] check_for_external_commands()
> [1194366930.928559] [064.1] [pid=27982] Making callbacks (type 8)...
> [1194366931.179900] [008.1] [pid=27982] ** Event Check Loop
> [1194366931.179941] [008.1] [pid=27982] Next High Priority Event Time:
> Tue Nov 6 09:35:31 2007
> [1194366931.179954] [008.1] [pid=27982] Next Low Priority Event Time:
> Tue Nov 6 09:35:31 2007
> [1194366931.179963] [008.1] [pid=27982] Current/Max Service Checks: 7/0
> [1194366931.179975] [001.0] [pid=27982] handle_timed_event() start
> [1194366931.179985] [064.1] [pid=27982] Making callbacks (type 8)...
> [1194366931.179996] [008.0] [pid=27982] ** Timed Event ** Type: 5, Run
> Time: Tue Nov 6 09:35:31 2007
> [1194366931.180005] [008.0] [pid=27982] ** Check Result Reaper
> [1194366931.180013] [001.0] [pid=27982] reap_check_results() start
> [1194366931.180021] [016.0] [pid=27982] Starting to reap check results.
> [1194366931.180197] [064.1] [pid=27982] Making callbacks (type 9)...
>

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

...[email truncated]...


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