[Home]

Summary:ASTERISK-28190: Asterisk Crashing
Reporter:IT Support (s2gsupport)Labels:
Date Opened:2018-11-29 09:52:21.000-0600Date Closed:2020-01-14 11:13:36.000-0600
Priority:MajorRegression?
Status:Closed/CompleteComponents:. I did not set the category correctly.
Versions:13.22.0 Frequency of
Occurrence		Frequent
Related
Issues:
Environment:Single Node - Production Server (no HA Stack) OS: Sangoma (Derived from Red Hat Enterprise Linux 7.5-0.11 (Source)) FreePBX: 14.0.3.25 RAM: 16GB HDD: 2TB CPU: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz (4 Cores) Usual Call volumen at the time of the crash 90-100 Calls No transcoding (g711 both call legs)Attachments:( 0) core.HA1-B-2018-11-26T11-13-11-0600-brief.txt
( 1) core.HA1-B-2018-11-26T11-13-11-0600-full.txt
( 2) core.HA1-B-2018-11-26T11-13-11-0600-locks.txt
( 3) core.HA1-B-2018-11-26T11-13-11-0600-thread1.txt
( 4) core.HA1-B-2018-11-28T10-56-27-0600-brief.txt
( 5) core.HA1-B-2018-11-28T10-56-27-0600-full.txt
( 6) core.HA1-B-2018-11-28T10-56-27-0600-locks.txt
( 7) core.HA1-B-2018-11-28T10-56-27-0600-thread1.txt
Description:Asterisk's core crash randomly.
Comments:By: Asterisk Team (asteriskteam) 2018-11-29 09:52:22.909-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: IT Support (s2gsupport) 2018-11-29 09:54:10.796-0600

Find attached the backtrace of 2 crashes.
By: Benjamin Keith Ford (bford) 2018-11-29 13:25:13.978-0600

The attached logs have don't have symbols. Refer to the wiki [1] on how to get the correct output, and if possible, explain what is happening that causes the crash, e.g. if there is a common denominator that triggers the crash, call load, etc.

[1]: https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace
By: IT Support (s2gsupport) 2018-11-29 15:55:03.994-0600

Find attached backtrace files with more details, we were able to add a few more debug libraries.
By: IT Support (s2gsupport) 2018-11-29 16:01:24.159-0600

The crash happens when there is a peak in calls, around 100-120 active calls. It has happened two days in a row, around the same time 10-11 AM CST. No other common denominator has been identified.
By: Benjamin Keith Ford (bford) 2018-11-30 09:18:57.294-0600

These backtraces still aren't very helpful, unfortunately. Are you compiling with DONT_OPTIMIZE and BETTER_BACKTRACES?

Also, can you get logs with at least verbose and debug turned up all the way at the time of the crash?
By: Asterisk Team (asteriskteam) 2018-12-14 12:00:01.859-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