Summary: | ASTERISK-26345: Asterisk freeze/Crash | ||
Reporter: | Ali Raza (a.raxa1) | Labels: | |
Date Opened: | 2016-09-07 15:21:46 | Date Closed: | 2016-09-07 17:10:05 |
Priority: | Critical | Regression? | |
Status: | Closed/Complete | Components: | |
Versions: | Frequency of Occurrence | Frequent | |
Related Issues: | |||
Environment: | Centos 5.7 | Attachments: | ( 0) Asterisk-Crash-potenetial-cause.txt ( 1) Asterisk-Crash-potenetial-cause.txt |
Description: | Asterisk freeze /crashes -- for last few week I am having this issue with my server. Asterisk stop responding to all incoming request looks like chan_sip has some issue. Nothing was installed on the system it just started and day by day its getting worse.
Please have a look at the attached backtrace. | ||
Comments: | By: Asterisk Team (asteriskteam) 2016-09-07 15:21:46.683-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) 2016-09-07 15:31:00.500-0500 I believe you attached your backtrace as a "contribution" and since you have no license it isn't showing up. However, it shouldn't be marked as a contribution - since it isn't a code or documentation contribution. Please re-attach your backtrace so that it will be easily visible. By: Rusty Newton (rnewton) 2016-09-07 15:31:17.340-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) 2016-09-07 15:31:32.182-0500 We require additional debug to continue with triage of your issue. Please follow the instructions on the wiki [1] for how to collect debugging information from Asterisk. For expediency, where possible, attach the debug with a '.txt' file extension so that the debug will be usable for further analysis. Thanks! [1] https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information By: Ali Raza (a.raxa1) 2016-09-07 15:47:00.606-0500 I have attached the backtrace(filename: Asterisk-Crash-potenetial-cause.txt), can you see it now? I followed that provided link[1] to take Backtrace. I will enable the debug log today -- by tomorrow I will provide you that logs. Thankyou. [1]: https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace By: Joshua C. Colp (jcolp) 2016-09-07 16:15:03.746-0500 What version of Asterisk is this? By: Ali Raza (a.raxa1) 2016-09-07 16:21:45.901-0500 Asterisk 1.8.9.2 By: Rusty Newton (rnewton) 2016-09-07 17:10:05.596-0500 https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions I'm going to go ahead and close this out, as Asterisk 1.8.X went End of Life in 2015-10-21. If you can reproduce the issue in one of the currently supported versions (see the wiki page referenced) then please open a new issue with a backtrace and log from the crash in the supported version. Preferably the latest release of version 13, which is the latest LTS release and will give you the greatest length of support currently. Thanks! |