| Summary: | ASTERISK-25496: Random lockups using ARI | ||
| Reporter: | Colin Dixon (cdx) | Labels: | |
| Date Opened: | 2015-10-26 11:39:58 | Date Closed: | 2020-01-14 11:13:38.000-0600 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | |
| Versions: | 13.2.0 13.6.0 | Frequency of Occurrence | Frequent |
| Related Issues: | |||
| Environment: | Running as one of two VMs on a single server under VMWare Ubuntu Linux 3.19.07 Asterisk V13.2 VMWare configuration: 8GB RAM, 4CPUs, Hyperthreading mode: Any | Attachments: | ( 0) bt01.txt ( 1) btfull.txt |
| Description: | We are driving this Asterisk installation from a conference proxy server we have written in .Net, using the ARI interface. Everything is fine, except that at random intervals - between 2 days and 2 weeks - Asterisk locks up. We've been unable to find any consistent accompanying event.
This backtrace is from our original 13.2 installation, using chan_sip. We recently rebuilt the VM using 13.6 and pjsip, and had a similar lockup, but unfortunately we weren't running Asterisk with the -g option. This version has other issues, however, so we reverted to our original 13.2, which is running now. | ||
| Comments: | By: Asterisk Team (asteriskteam) 2015-10-26 11:40:01.645-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: Colin Dixon (cdx) 2015-10-26 11:42:35.056-0500 Backtrace files By: Rusty Newton (rnewton) 2015-10-30 17:22:25.780-0500 Please follow the instructions on the wiki [1] for obtaining debug relevant to a deadlock. Once you have that information, attach it to the issue. Be sure the instructions are followed exactly as the debug may otherwise not be useful. Thanks! [1] https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace#GettingaBacktrace-GettingInformationForADeadlock By: Rusty Newton (rnewton) 2015-10-30 17:23:47.261-0500 Recompile with the appropriate compiler flags and hopefully the traces will be more useful. If you can include a debug log including SIP and ARI traffic during the time of the lockup that will be helpful as well. https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information By: Asterisk Team (asteriskteam) 2015-11-14 12:00:21.411-0600 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 | ||