[asterisk-bugs] [JIRA] (ASTERISK-28643) Deadlock, possibly in Parking, maybe in combination with AMI status messages.

[Steve Sether (JIRA)]

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

Steve Sether commented on ASTERISK-28643:
-----------------------------------------

It looks like you've found this is a known issue, already in your internal tracking system.  

Does that mean it'll be fixed in a future release?  Is there any expectation on when?  Also, what conditions will this happen under?  Are there any ways to mitigate the problem?

 We'd like to put Asterisk 16 in production, but are rather leery of doing so with this bug since it locks up SIP, and requires a reboot to fix. 

> Deadlock, possibly in Parking, maybe in combination with AMI status messages.
> -----------------------------------------------------------------------------
>
>                 Key: ASTERISK-28643
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28643
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: PBX/General
>    Affects Versions: 16.6.1
>         Environment: Centos 6.10
>            Reporter: Steve Sether
>            Assignee: Unassigned
>            Severity: Critical
>         Attachments: core_show_locks-2019-11-14-crash1.txt, full-asterisk-crash.gz
>
>
> Asterisk creates a deadlock, and stops responding to any SIP messages when I park a call. No new incoming calls are accepted, no outgoing calls are accepted, etc.  Some initial investigation using gdb and the core file show this might indicate it's related to generating STATUS messages from the AMI.  This happened when only one or maybe two calls were on the system.  Looking through the lock file it looks like it's a simple deadlock between two threads, each of which holing locks the other needs.   One of which is in parking code.
> I was able to reproduce it initially a couple times, (and got some debug information out of it, including from a version where core show locks was compiled in).  For whatever reason, I can't seem to reproduce it again, even under the same conditions.



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