| Summary: | ASTERISK-27916: Error 4 in app_queue.so in 13.18-cert3 | ||
| Reporter: | Aleksandr Chuvaldin (Aleksandr Chuvaldin) | Labels: | |
| Date Opened: | 2018-06-13 07:52:06 | Date Closed: | 2020-01-14 11:13:50.000-0600 |
| Priority: | Critical | Regression? | |
| Status: | Closed/Complete | Components: | Applications/app_queue |
| Versions: | 13.18.3 | Frequency of Occurrence | Frequent |
| Related Issues: | |||
| Environment: | Physical Server Centos 7 Kernel 3.10.0-693.5.2.el7.x86_64 | Attachments: | ( 0) core-asterisk-11-5060-5060-1-1528532482-brief.txt ( 1) core-asterisk-11-5060-5060-1-1528532482-full.txt ( 2) core-asterisk-11-5060-5060-1-1528532482-locks.txt ( 3) core-asterisk-11-5060-5060-1-1528532482-thread1.txt |
| Description: | Asterisk crashes spontaneously:
[Jun 9 11:21:18] VERBOSE[30602][C-00005264] app_dial.c: Called PJSIP/89600464042@pstn1-1 [Jun 9 11:21:22] VERBOSE[30572][C-0000525d] bridge_channel.c: Channel PJSIP/core2-0000fcc1 left 'simple_bridge' basic-bridge <ad5b9962-e279-4b03-94e2-9aa59120bfda> [Jun 9 11:21:22] VERBOSE[30596][C-0000525d] bridge_channel.c: Channel PJSIP/6523-0000fcd0 left 'simple_bridge' basic-bridge <ad5b9962-e279-4b03-94e2-9aa59120bfda> [Jun 9 11:21:38] Asterisk certified/13.18-cert3 built by root @ srv-platforma1.testregion.tensor.ru on a x86_64 running Linux on 2018-04-09 07:19:06 UTC [Jun 9 11:21:38] VERBOSE[1] config.c: Parsing '/etc/asterisk/pjproject.conf': Found [Jun 9 11:21:38] VERBOSE[1] message.c: Message handler 'dialplan' registered. [Jun 9 11:21:38] VERBOSE[1] pbx_functions.c: Registered custom function 'MESSAGE' | ||
| Comments: | By: Asterisk Team (asteriskteam) 2018-06-13 07:52:07.848-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-06-13 07:57:51.098-0500 Certified Asterisk only receives changes and bug fixes as a result of commercial support agreements, if you have one then you need to go through Digium support to receive support. If you do not have one you will need to update to the latest version of Asterisk to ensure the problem still exists and to also ensure your Asterisk is built[1] so that backtraces are valid (your backtraces contain nothing). As well 13.18 certified is no longer supported, 13.21 has been released. [1] https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace By: Aleksandr Chuvaldin (Aleksandr Chuvaldin) 2018-06-13 08:11:36.185-0500 Thank you for reply. By: Asterisk Team (asteriskteam) 2018-06-27 12:00:01.622-0500 Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1]. [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines | ||