| Summary: | ASTERISK-26585: Asterisk certified 13.8-cert1 & 13.8-cert2 & 13.8-cert3 : freeze on 'sip reload' | ||||
| Reporter: | Jonas Kellens (jonaskellens) | Labels: | |||
| Date Opened: | 2016-11-12 03:45:54.000-0600 | Date Closed: | 2016-11-12 05:24:20.000-0600 | ||
| Priority: | Major | Regression? | Yes | ||
| Status: | Closed/Complete | Components: | Channels/chan_sip/General | ||
| Versions: | 13.11.2 | Frequency of Occurrence | Constant | ||
| Related Issues: |
| ||||
| Environment: | Linux 2.6.32-642.4.2.el6.x86_64 #1 SMP Tue Aug 23 19:58:13 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux | Attachments: | ( 0) backtrace-threads.txt ( 1) core-show-locks.txt | ||
| Description: | My original question on the mailinglist : http://asteriskfaqs.org/2016/10/11/asterisk-users/asterisk-13112-13111-13100-and-certified-138-cert3-freeze-on-sip-reload.html
I was asked to post a backtrace. I followed instructions on https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace#GettingaBacktrace-GettingInformationForADeadlock My Asterisk always freezes after issuing 'sip reload' a few times. I can easily re-generate this every time again and again. backtrace-threads.txt and core-show-locks.txt attached. I want to know why my Asterisk always freezes. | ||||
| Comments: | By: Asterisk Team (asteriskteam) 2016-11-12 03:45:55.997-0600 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) 2016-11-12 05:24:20.686-0600 This has already been fixed as of 13.12.0 By: Joshua C. Colp (jcolp) 2016-11-12 05:24:59.436-0600 As well Asterisk certified 13.8 only [receives changes as a result of issues run into by commercial customers|https://www.digium.com/products/asterisk/certified-asterisk]. If you are a commercial customer please contact Digium support. | ||||