Summary:	ASTERISK-28043: Error 4 in app_queue.so
Reporter:	Nikolay (tensor)	Labels:	fax pjsip
Date Opened:	2018-09-06 08:48:09	Date Closed:	2020-01-14 12:03:42.000-0600
Priority:	Major	Regression?
Status:	Closed/Complete	Components:	. I did not set the category correctly.
Versions:	13.21.1	Frequency of Occurrence	Occasional
Related Issues:
Environment:	Intel(R) Core(TM) i3-2120 CPU @ 3.30GHz, 4GB RAM, CentOS Linux release 7.4.1708 (Core), kernel 3.10.0-693.5.2.el7.x86_64,	Attachments:	( 0) core-asterisk-11-5060-5060-1-1535530275-brief.txt ( 1) core-asterisk-11-5060-5060-1-1535530275-full.txt ( 2) core-asterisk-11-5060-5060-1-1535530275-locks.txt ( 3) core-asterisk-11-5060-5060-1-1535530275-thread1.txt
Description:	Asterisk crashes spontaneously
Comments:	By: Asterisk Team (asteriskteam) 2018-09-06 08:48:10.476-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: Joshua C. Colp (jcolp) 2018-09-06 08:51:28.965-0500 Thank you for the crash report. However, we need more information to investigate the crash. Please provide: 1. A backtrace generated from a core dump using the instructions provided on the Asterisk wiki [1]. 2. Specific steps taken that lead to the crash. 3. All configuration information necesary to reproduce the crash. Thanks! [1]: https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace By: Nikolay (tensor) 2018-09-06 08:51:33.311-0500 with ast_coredumper By: Joshua C. Colp (jcolp) 2018-09-06 08:52:26.789-0500 There are no symbols available so these backtraces don't show anything. You need to ensure that you follow the instructions on the wiki to ensure that they are useful. By: Nikolay (tensor) 2018-09-07 07:02:57.434-0500 1 Asterisk already with options DONT_OPTIMIZE and BETTER_BACKTRACES and without COMPILE_DOUBLE. 2 Options DEBUG_THREADS and MALLOC_DEBUG are disabled because they are can seriously impact performance. 3 You wrote "we need more information to investigate the crash". What else should I do? By: Joshua C. Colp (jcolp) 2018-09-11 06:40:01.593-0500 Are you sure that you built Asterisk that way? What process do you use? We can't go any further without a valid backtrace. For an example of a valid backtrace you can look at ASTERISK-28019 and see how it compares to yours. By: Benjamin Keith Ford (bford) 2018-09-12 08:22:44.335-0500 As Josh mentioned, these logs don't contain any information since there are no symbols, meaning there's really nothing we can do until that is done. By: Nikolay (tensor) 2018-09-13 03:29:18.914-0500 Thank you for reply. We compile asterisk with options DONT_OPTIMIZE and BETTER_BACKTRACES and use -g when asterisk starts. Is it enough to see valid backtrace? By: Chris Savinovich (csavinovich) 2018-09-13 13:04:07.433-0500 Nikolay, the problem for not getting the symbols in the back trace maybe in the way you built Asterisk. Could you please provide us with a full step list of how you built Asterisk.  If all steps are correct, you should be able to type a command like: file /usr/lib/asterisk/modules/res_pjsip.so ...and the output should indicate if the the module is stripped or not.  If it says "stripped" then something is not being compiled right for the symbols to show, or perhaps one of the pre-packages was also installed manually. Thanks By: Nikolay (tensor) 2018-09-14 06:56:39.448-0500 Steps of how we build Asterisk: ./configure --with-spandsp --with-pri --with-unixodbc --with-pjproject-bundled --with-crypto --with-ssl=ssl --with-srtp --with-opus --with-ogg --with-vorbis cd menuselect make menuselect cd .. make menuselect-tree menuselect/menuselect --enable codec_opus --enable codec_silk --enable codec_siren7 --enable codec_siren14  --enable app_chanisavail --enable res_fax_spandsp --enable chan_local --enable res_crypto --enable res_http_websocket --enable chan_sip --enable chan_ooh323 --enable app_meetme  --enable res_config_mysql --enable res_odbc --enable pbx_lua --disable BUILD_NATIVE --enable DONT_OPTIMIZE --enable BETTER_BACKTRACES --disable COMPILE_DOUBLE --enable res_srtp --enable res_hep --enable res_hep_pjsip --enable res_hep_rtcp menuselect.makeopts By: Joshua C. Colp (jcolp) 2018-09-14 09:36:37.517-0500 Those are not the complete commands to build Asterisk. What else is done? And what about the output of the "file" command? By: Nikolay (tensor) 2018-09-18 01:19:32.601-0500 Output: [root@tel-pbx1-pre-test-test /]# file /usr/lib64/asterisk/modules/pbx_spool.so /usr/lib64/asterisk/modules/pbx_spool.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=5d690c7a8d317235f21b4d312c35bc6b49e9d8aa, stripped By: Joshua C. Colp (jcolp) 2018-09-18 04:23:17.448-0500 Your build process (or something else) is stripping out all of the symbols from the resulting Asterisk, making backtraces useless. That is not a normal part of the build process we do. By: Nikolay (tensor) 2018-09-24 02:09:13.254-0500 Thank you for help. We find reason why modules was not stipped and fix it. When we get usefull backtrace, we open new issue or update this. By: Sean Bright (seanbright) 2020-01-14 12:03:42.840-0600 If you continue to experience this crash and are able to provide backtraces with debugging information available, you can re-open this issue by commenting on it.