[asterisk-bugs] [JIRA] (ASTERISK-26019) Deadlock after 'core reload'

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-26019:
------------------------------------------

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

> Deadlock after 'core reload'
> ----------------------------
>
>                 Key: ASTERISK-26019
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26019
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 13.8.0, 13.8.1, 13.8.2, 13.9.0
>            Reporter: Andrew Nagy
>         Attachments: backtrace-threads-lgaetzdev2-2016-05-12.txt
>
>
> This is a sporadic issue. Which makes it all the more fun.
> Occasionally while running "core reload" Asterisk will just up and stop all transactions. Extensions will unregister and calls will be dropped.
> When trying to run "core reload" again sometimes Asterisk will say "previous reload not finished" but if you try to run "core reload" again after that it just wont say anything.
> The CLI is still active at this point and there's been much debate about how to track down the bug.
> It's only an issue in Asterisk 13. I have attached GDB logs to this ticket for further analysis



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