Summary:	ASTERISK-26892: pbx_dundi: Asterisk segfaults when run in Kickstart, in destroy_peer at pbx_dundi.c
Reporter:	Michael Newton (miken32)	Labels:
Date Opened:	2017-03-22 11:38:29	Date Closed:
Priority:	Major	Regression?
Status:	Open/New	Components:	PBX/pbx_dundi
Versions:	13.14.0	Frequency of Occurrence	Constant
Related Issues:
Environment:	Scientific Linux 7.3 x86_64	Attachments:	( 0) astbuild.log ( 1) backtrace.txt ( 2) debuglog.txt ( 3) dundi.conf
Description:	Asterisk will only run for a few seconds before crashing in the Kickstart post-install environment. Once the machine reboots into normal operation, Asterisk is stable. I've compiled with DONT_OPTIMIZE and BETTER_BACKTRACE, will attach the output from gdb.
Comments:	By: Asterisk Team (asteriskteam) 2017-03-22 11:38:30.521-0500 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. By: Michael Newton (miken32) 2017-03-22 16:01:58.781-0500 After inspecting the backtrace, I tried adding {{noload => pbx_dundi.so}} to {{modules.conf}}. It prevents the segfault. Updating component... By: Rusty Newton (rnewton) 2017-03-24 09:12:28.376-0500 Thanks. Also, I'm not extremely familiar with kickstart installs, but if you can configure Asterisk to produce a debug log on startup that could be helpful as well. https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information It would be helpful to have a log on startup with warning,error,notice,verbose and debug, with both verbose and debug turned up to level 5. By: Rusty Newton (rnewton) 2017-03-24 09:45:46.685-0500 [~miken32] , in addition, can you provide your extensions.conf and dundi.conf if they are not simply the sample/default files. By: Michael Newton (miken32) 2017-03-24 12:36:28.955-0500 {{dundi.conf}} attached; my {{modules.conf}} at that point is nothing but "autoload => yes". I'll get a debug log attached later today, the VM has since been wiped out. I did look at it and didn't see any sort of pattern to when it would crash, but only had verbosity to 3 at that point. By: Rusty Newton (rnewton) 2017-03-24 14:17:16.214-0500 Alrighty, and so extension.conf was blank, or default? By: Michael Newton (miken32) 2017-03-24 17:09:22.969-0500 Debug log attached. Startup at 18:02 is after Kickstart has completed and machine has rebooted. Everything before that is within the Kickstart post-install environment. {{extensions.conf}} is completely empty when the crashes occur.