| Summary: | ASTERISK-25303: Error 4 in app_queue.so in 13.1-cert2 | ||||
| Reporter: | Max Hofmann (mhofmann) | Labels: | |||
| Date Opened: | 2015-08-05 02:46:41 | Date Closed: | 2015-08-13 09:37:33 | ||
| Priority: | Critical | Regression? | |||
| Status: | Closed/Complete | Components: | Applications/app_queue | ||
| Versions: | 13.1.0 | Frequency of Occurrence | One Time | ||
| Related Issues: |
| ||||
| Environment: | Virtual System Ubuntu 14.04.2 LTS Kernel: 3.16.0-41-generic | Attachments: | ( 0) backtrace.txt | ||
| Description: | Our customer reported that his system crashed. He had hold a caller in musiconhold and called a queue. After that he wanted to transfer the caller to a queue but then the system crashed.
{noformat} kernel: [2397965.541135] show_signal_msg: 27 callbacks suppressed Aug 5 09:05:58 kernel: [2397965.541139] asterisk[1185]: segfault at 10 ip 00007febd71897cc sp 00007febcc127cc0 error 4 in app_queue.so[7febd7178000+34000] [Aug 5 09:05:58] VERBOSE[1696][C-00001298] bridge_channel.c: Channel SIP/17-000024ff left 'native_rtp' basic-bridge <150318bd-e8fa-4609-b099-d32616b9524f> [Aug 5 09:05:58] VERBOSE[1696][C-00001298] bridge_channel.c: Channel SIP/22-00002501 left 'simple_bridge' basic-bridge <c6454213-945c-4638-a22d-24cfc848504c> [Aug 5 09:05:58] VERBOSE[1696][C-00001298] bridge_channel.c: Channel SIP/17-000024ff swapped with SIP/22-00002501 into 'simple_bridge' basic-bridge <c6454213-945c-4638-a22d-24cfc848504c> [Aug 5 09:05:58] VERBOSE[1696][C-00001298] bridge.c: Bridge 150318bd-e8fa-4609-b099-d32616b9524f: switching from native_rtp technology to simple_bridge [Aug 5 09:05:58] VERBOSE[1230][C-00001298] bridge_channel.c: Channel SIP/22-00002500 left 'simple_bridge' basic-bridge <150318bd-e8fa-4609-b099-d32616b9524f> [Aug 5 09:05:58] VERBOSE[1231][C-00001299] pbx.c: Spawn extension (intern, 12, 3) exited non-zero on 'SIP/22-00002501' [Aug 5 09:05:58] VERBOSE[1229][C-00001298] res_musiconhold.c: Stopped music on hold on SIP/17-000024ff [Aug 5 09:12:55] Asterisk 13.1-cert2 built by root @ *** on a x86_64 running Linux on 2015-07-06 08:00:25 UTC {noformat} | ||||
| Comments: | By: Asterisk Team (asteriskteam) 2015-08-05 02:46:42.634-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: Rusty Newton (rnewton) 2015-08-05 13:18:17.479-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: Rusty Newton (rnewton) 2015-08-05 13:19:32.771-0500 We need the full backtrace, and if you can reproduce the issue a debug log captured showing the time right before the crash. https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information By: Max Hofmann (mhofmann) 2015-08-13 08:33:39.420-0500 In the attachment you can find the backtrace. Whate we done for the crash: A called B, B hold A in MOH an called a Queue. C is logged in in Queue and answered. B hold C in MOH and pressed Transfer. Crash. Phones are SNOM VoIP Phones By: Rusty Newton (rnewton) 2015-08-13 09:28:43.728-0500 Are you able to reproduce the crash at will? If so, can you recompile with the compiler flags recommended in the wiki article? Also, if you can reproduce it would be good to test with the latest Asterisk 13 release (and git branch) if possible to see if the issue still occurs. By: Joshua C. Colp (jcolp) 2015-08-13 09:37:33.382-0500 After looking at the provided backtrace this appears to be a duplicate of ASTERISK-25185. | ||||