[Home]

Summary:ASTERISK-28721: Asterisk restarts with core dump
Reporter:Jaco van Niekerk (faqterson)Labels:
Date Opened:2020-01-29 08:31:38.000-0600Date Closed:2020-02-19 12:00:01.000-0600
Priority:MajorRegression?
Status:Closed/CompleteComponents:. I did not set the category correctly.
Versions:13.28.1 Frequency of
Occurrence
Related
Issues:
Environment:Centos 6 HP DL20 Gen9 Attachments:( 0) bt_dump
( 1) bt_full_dump
( 2) core.pbx-eoh.samsung.co.za-2020-01-29T16-05-44+0200-brief.txt
( 3) core.pbx-eoh.samsung.co.za-2020-01-29T16-05-44+0200-full.txt
( 4) core.pbx-eoh.samsung.co.za-2020-01-29T16-05-44+0200-locks.txt
( 5) core.pbx-eoh.samsung.co.za-2020-01-29T16-05-44+0200-thread1.txt
Description:Asterisk randomly restarts and generates core dump. I can't figure out the cause.
Comments:By: Asterisk Team (asteriskteam) 2020-01-29 08:31:39.298-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].

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.
By: Benjamin Keith Ford (bford) 2020-01-30 11:15:30.531-0600

It does look like there's something going on with boundaries, but there's not much information in the backtrace itself. Can you compile with BETTER_BACKTRACES? Information on how to do so can be found here[1] as well as additional options that help provide better information for us to work with.

[1]: https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace
By: Kevin Harwell (kharwell) 2020-01-30 11:32:24.961-0600

Please post the output of the following:
{noformat}
*CLI> core show version
{noformat}

By: Jaco van Niekerk (faqterson) 2020-01-31 06:57:31.096-0600

Please find below:
Asterisk 13.28.1 built by root @ dev.desktop-ns.co.za on a x86_64 running Linux on 2019-09-18 06:02:21 UTC

I have requested with the client time to recompile with BETTER_BACKTRACES, they are a 24 hours call center.
By: Benjamin Keith Ford (bford) 2020-02-04 11:12:31.491-0600

Looking at the backtrace, there appear to be some discrepancies between it and the code in 13.28.1. One example is {{ast_channel_snapshot_get_latest}}, which has this definition in 13.28.1:
{{struct ast_channel_snapshot *ast_channel_snapshot_get_latest(const char *uniqueid);}}
It only asks for a string, but in the backtrace, it has completely different arguments:
{{ast_channel_snapshot_get_latest (chan=0x0, type=0x29bc3f0, blob=0x3de280c490)}}
{{local_attended_transfer}} has the same problem. According to {{git blame}}, this code has not been touched since 2013:
{code:xml}
$ git blame -L 26812,26812 channels/chan_sip.c

cfe32ec1 (Mark Michelson 2013-05-28 15:26:15 +0000 26812) static int local_attended_transfer(struct sip_pvt *transferer, struct ast_channel *transferer_chan, uint32_t seqno, int *nounlock)
{code}
Somehow this backtrace is not in line with what we would expect from 13.28.1. Are there custom patches running on this Asterisk instance? We won't be able to identify the problem with the current information since it differs from the code base. Any more information you can provide would help.
By: Jaco van Niekerk (faqterson) 2020-02-05 00:51:36.232-0600

Attached the asterisk files created by the asterisk core dump script, I hope this provides more information.

I am not running any custom patches. Its clean asterisk install with custom dial plans.

By: Benjamin Keith Ford (bford) 2020-02-05 09:43:45.696-0600

Can you attach a full log leading up to and including the crash?
By: Asterisk Team (asteriskteam) 2020-02-19 12:00:01.064-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