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

[Andrew Nagy (JIRA)]

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

Andrew Nagy commented on ASTERISK-26019:
----------------------------------------

Debug prior to not responding.
{code}
[2016-05-12 14:14:46] WARNING[2017]: pjproject:0 <?>:   tsx0x7feecc06b .Error sending Request msg OPTIONS/cseq=21777 (tdta0x3120a20): Transport not available for use (PJSIP_ETPNOTAVAIL)
[2016-05-12 14:14:46] WARNING[2017]: pjproject:0 <?>:   tsx0x7feecc06b .Transport error, terminating transaction. Err=171065 (Transport not available for use (PJSIP_ETPNOTAVAIL))
{code}

> 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
> {code}
> lgaetzdev2*CLI> core reload
>     -- The previous reload command didn't finish yet
> {code}



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