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

Gergely Dömsödi (JIRA) noreply at issues.asterisk.org
Wed Jul 15 13:02:33 CDT 2015


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

Gergely Dömsödi commented on ASTERISK-25251:
--------------------------------------------

When I was looking at [^bt.txt] I suspected the same, so I made sure that the DNS servers are configured correctly, and they are, and normally both of them can resolve. However, as it is our ISP's server, it could of course be faulty somehow, by not responding to some particular query because of query rate for example. However, Asterisk should handle this condition in a far more user friendly way, as there could be a lot of erroneous DNS servers out there in the wild.

Although, I read somewhere that {{gettaddrinfo()}} and/or {{gethostbyname()}} in glibc is far from perfect, and Fedora is massively [patching|https://fedoraproject.org/wiki/Features/FixNetworkNameResolution] them, but my resources are unfortunately not enough to decide who should fix this.

I am going to try Asterisk without any DNS resolver tomorrow, and see if this fixes the problems. If there is anything else I can help with, please let me know.

> 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
>         Attachments: bt.txt, bt.txt, fd.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