[asterisk-bugs] [JIRA] (ASTERISK-22857) Deadlock: Locked Here: chan_iax2.c line 9756 (socket_read)

[David Brillert (JIRA)]

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

David Brillert commented on ASTERISK-22857:
-------------------------------------------

I enabled verbose to file and iax2 set debug on.
Then ran a couple of iax2 commands to see why the maxcallnumber limit exceeded.
Issuing the IAX2 commands resulted in a deadlock in IAX2
core show locks didn't respond and other CLI commands did not respond.
So I attached with GDB

Attached messages file and gdb output.

So it looks like I can reproduce by running the IAXy for a little while and then executing some iax2 CLI commands.
                
> Deadlock: Locked Here: chan_iax2.c line 9756 (socket_read)
> ----------------------------------------------------------
>
>                 Key: ASTERISK-22857
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22857
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_iax2
>    Affects Versions: SVN, 11.6.0
>         Environment: 64 bit CentOS, 4GB RAM
>            Reporter: David Brillert
>            Assignee: David Brillert
>            Severity: Critical
>         Attachments: core show locks_gdb thread apply all bt full.txt
>
>
> Full deadlock no call processing, no SIP traffic.
> GDB output DONT_OPTIMIZE DEBUG_THREADS BETTER_BACKTRACES thread apply all bt full.txt attached.  The deadlock occurred overnight while the system was idle.
> It is happening on multiple production servers.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira