[Home]

Summary:ASTERISK-29127: SIGABRT Asterisk crash occurred with Asterisk 13.36
Reporter:Joseph Hayhoe (jhayhoe)Labels:
Date Opened:2020-10-15 17:17:24Date Closed:2020-10-30 12:00:01
Priority:MajorRegression?
Status:Closed/CompleteComponents:General
Versions:13.36.0 Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) core.dc3-freepbx1.int.liquidweb.com-2020-10-15T21-09-37+0000-brief.txt
( 1) core.dc3-freepbx1.int.liquidweb.com-2020-10-15T21-09-37+0000-full.txt
( 2) core.dc3-freepbx1.int.liquidweb.com-2020-10-15T21-09-37+0000-info.txt
( 3) core.dc3-freepbx1.int.liquidweb.com-2020-10-15T21-09-37+0000-locks.txt
( 4) core.dc3-freepbx1.int.liquidweb.com-2020-10-15T21-09-37+0000-thread1.txt
Description:We experienced a crash in Asterisk today that generated a core dump. This crash appears to be the result of a SIGABRT instead of a segmentation fault. We recently upgraded this server to 13.36 from 13.32 in order to fix another bug that was experienced in the earlier version.

I will attach files from ast coredumper to this issue.
Comments:By: Asterisk Team (asteriskteam) 2020-10-15 17:17:25.396-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. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed.

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].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/].
By: Kevin Harwell (kharwell) 2020-10-15 17:42:43.391-0500

Unfortunately the backtrace is missing needed information [1]. Please install the Asterisk debug symbols, and attach a new backtrace after another occurrence.

Also attach the relevant log data leading up to the crash.

[1] https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace

Thanks!
By: Joseph Hayhoe (jhayhoe) 2020-10-15 18:09:46.832-0500

I did ensure asterisk13-debuginfo and pjproject-debuginfo packages were updated before running the ast cordumper command. There were updates available to both at the time. Do the debug symbols need to be up to date and in place before the crash happens to ensure the core dump contains helpful information? In turn do we need to then wait for another crash to provide a useful core dump file?

I also checked asterisk logs and journalctl on the server and found no identifiable information at the time of the crash. Only information logged is the normal restart of services triggered by our scripts after the crash.
By: Joshua C. Colp (jcolp) 2020-10-16 05:06:55.294-0500

You should not need to install the symbols before a crash occurs, but they should match the underlying Asterisk package that was in use when the crash occurred. Was this met?

I should also point out that Asterisk 13 is going security fix only on October 24th, after which no bug fixes will be placed into it.
By: Asterisk Team (asteriskteam) 2020-10-30 12:00:00.872-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