[asterisk-bugs] [JIRA] (ASTERISK-28472) Asterisk Crash

Asterisk Team (JIRA) noreply at issues.asterisk.org
Sat Jul 6 12:07:47 CDT 2019


    [ https://issues.asterisk.org/jira/browse/ASTERISK-28472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=247537#comment-247537 ] 

Asterisk Team commented on ASTERISK-28472:
------------------------------------------

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.

> Asterisk Crash
> --------------
>
>                 Key: ASTERISK-28472
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28472
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: . I did not set the category correctly.
>    Affects Versions: 16.4.0
>         Environment: Amazon Linux 2, running on 
>            Reporter: Jonas Swiatek
>            Severity: Critical
>
> We're seeing this crash every now and then - last time was around 3 weeks ago, on Asterisk 16.3, though we've upgraded to 16.4 since then, and enabled BETTER_BACKTRACES and DONT_OPTIMIZED to try and get to the bottom of it.
> I'm at a loss for what might be causing it. When this server crashed it was serving 6 channels, and the only exotic thing being used by any of them were ARI, but I don't believe any of the active channels were actually in the Stasis application.
> I'm not really qualified to read the crash dump, but there is some mention of libsrtp in one of the files, so I've included which version of that we're using (1.5.4, as recommended on the wiki).
> Any insight would be greatly appreciated, and I can provide whatever else information might be valuable.



--
This message was sent by Atlassian JIRA
(v6.2#6252)



More information about the asterisk-bugs mailing list