[asterisk-bugs] [JIRA] (ASTERISK-25251) Deadlock in PJSIP

Richard Mudgett (JIRA) noreply at issues.asterisk.org
Thu Jul 16 11:15:32 CDT 2015


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

Richard Mudgett commented on ASTERISK-25251:
--------------------------------------------

I think you are still having DNS resolution issues.  The [^locks-nodns.txt] files show two threads waiting on different channel locks.  When you find the threads that have the locks being waited on and then look in the [^bt-nodns.txt] backtrace file for the threads holding the locks, you see that the stacks are uninformative because there are only two things on the stack with question marks for names.

I think that the time between getting the locks file and the backtrace file the probable DNS query timed out and that specific block eliminated.  Then the slowdown moves to another DNS query involving other threads.

> Deadlock in PJSIP
> -----------------
>
>                 Key: ASTERISK-25251
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25251
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_pjsip
>    Affects Versions: 13.1.1, 13.3.2, 13.4.0
>         Environment: Fedora 22
>            Reporter: Gergely Dömsödi
>            Assignee: Rusty Newton
>         Attachments: bt-nodns.txt, bt.txt, bt.txt, fd.txt, locks-nodns.txt, locks.txt, taskprocessors.txt, threads.txt
>
>
> Using PJSIP, after about 10-20 minutes of SIP traffic between two PJSIP peers, a deadlock occurs and Asterisk cannot serve SIP traffic anymore. Incoming INVITES can be seen with a tcpdump, but it is not even visible in pjsip log.
> The issue is reproducible with both the "vanilla" asterisk package in Fedora 22 (13.1.1), with the package currently in updates-testing (13.3.2), and a custom-built 13.4.0. Tried with PJSIP 2.3 from Fedora and a custom built 2.4, both were affected.
> When in the deadlock, PJSIP commands continue to work (pjsip show *), but asterisk cannot be stopped, core stop now just returns, but nothing happens. Only SIGKILL can pull out asterisk from this state.
> Attached outputs and backtraces are from the custom built 13.4.0, with PJSIP 2.4.



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



More information about the asterisk-bugs mailing list