| Summary: | ASTERISK-27111: Coredump with Asterisk 13.16.0 | ||
| Reporter: | Travis Ryan (darkunderlord) | Labels: | |
| Date Opened: | 2017-07-07 09:33:16 | Date Closed: | 2020-01-14 11:14:11.000-0600 |
| Priority: | Critical | Regression? | |
| Status: | Closed/Complete | Components: | |
| Versions: | 13.16.0 | Frequency of Occurrence | Occasional |
| Related Issues: | |||
| Environment: | Ubuntu 16.04 server, PJSIP (built-in version). | Attachments: | ( 0) core-brief.txt ( 1) core-full.txt ( 2) core-locks.txt ( 3) core-thread1.txt |
| Description: | Ok, so a few years ago, when 13 first came out, I was having a core dump (crash) issue with asterisk 13. I worked with Josh some and even used my Digium subscription for support. Never was able to get it fixed at that time so let it go. Well now I am trying on the same server, after a completely fresh install of Ubuntu, Asterisk, etc. Some of the config files are the same.
Issue years ago and until a fresh install recently, was when a phone registered with PJSIP, it would crash the server immediately. Now, after a fresh install, everything seems fine but I came in this morning to a crashed server, and a core dump file. Can someone help me figure out why it’s coredumping now? I have the core dump and ran the ast_coredumper against it and have the saved files from the results. I am on Asterisk 13.16.0. Thanks, Travis | ||
| Comments: | By: Asterisk Team (asteriskteam) 2017-07-07 09:33:18.241-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: Travis Ryan (darkunderlord) 2017-07-07 09:36:18.899-0500 coredump info attached. By: Rusty Newton (rnewton) 2017-07-07 18:27:49.058-0500 I'm not a dev, but it looks like it is crashing during the destruction of a subscription possibly. The developers will typically need more than just the trace itself. Please attach a debug log for the next crash when it happens. https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information You can also go ahead and attach any log you had running for the last crash. To avoid confusion make sure the log you posts only shows what is going on right up to the crash. If you can provide dialplan and describe the general setup of the system, that helps as well. By: Richard Mudgett (rmudgett) 2017-07-07 18:37:36.778-0500 MALLOC_DEBUG may be able to help find the problem. https://wiki.asterisk.org/wiki/display/AST/MALLOC_DEBUG+Compiler+Flag By: Asterisk Team (asteriskteam) 2017-07-22 12:00:01.566-0500 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 | ||