| Summary: | ASTERISK-26650: Asterisk 13.12.0 Crash | ||
| Reporter: | Olivier Divel (odivel) | Labels: | |
| Date Opened: | 2016-12-08 07:39:29.000-0600 | Date Closed: | 2020-01-14 11:13:28.000-0600 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | |
| Versions: | 13.12.0 | Frequency of Occurrence | Occasional |
| Related Issues: | |||
| Environment: | Debian 8 stable 2 CORE 2GB RAM | Attachments: | |
| Description: | Hi,
We are using the 13.12.0 version of Asterisk as a Class4 softswitch This morning we had a crash that already happened randomly in the past ( in 13.5 and 13.8 too ) The only thing I can see is a segfault : asterisk[15907]: segfault at 7fbc00000002 ip 000000000051a470 sp 00007fbd3320dc98 error 4 in asterisk[400000+2a0000] Unfortunately I don't have any Coredump Have you any advice ? Or Can I give you something for an analyse ? | ||
| Comments: | By: Asterisk Team (asteriskteam) 2016-12-08 07:39:31.233-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-12-08 07:49:18.092-0600 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 You'll need to get a core dump in order to do the above, that's what is needed to investigate a crash. Otherwise it is like looking for a needle in a haystack. By: Asterisk Team (asteriskteam) 2016-12-22 12:00:01.978-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 | ||