[asterisk-bugs] [JIRA] (ASTERISK-25653) Deadlock - PJ_ENOMEM errors & high Recv-Q counts when using PJSIP TLS extensions

Richard Mudgett (JIRA) noreply at issues.asterisk.org
Tue Mar 29 11:14:56 CDT 2016


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

Richard Mudgett edited comment on ASTERISK-25653 at 3/29/16 11:14 AM:
----------------------------------------------------------------------

Since changes went in which may have impacted this issue.  New logs with the information would be needed, as well as the specific version of PJSIP and Asterisk in use.


was (Author: jcolp):
Since changes went in which may have impacted this new logs with the information would be needed, as well as the specific version of PJSIP and Asterisk in use.

> Deadlock - PJ_ENOMEM errors & high Recv-Q counts when using PJSIP TLS extensions
> --------------------------------------------------------------------------------
>
>                 Key: ASTERISK-25653
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25653
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: pjproject/pjsip
>    Affects Versions: 13.4.0, 13.5.0, 13.6.0, 13.7.0
>         Environment: CentOS 7 (with Asterisk installed separately), FreePBX 13 (with Asterisk bundled)
>            Reporter: Phi Tran
>            Assignee: Phi Tran
>         Attachments: backtrace-threads.txt, backtrace-threads.txt, core-show-locks.txt
>
>
> Deadlock occurs when PJSIP TLS connections to Asterisk fail after 8-30 hours.  The logs show "PJ_ENOMEM" errors right around the time this happens.  Happens after a variable period of time once Asterisk is started; normally happens when I am moving between Wi-Fi and LTE networks on Bria for iOS v3.5.2.  System has 4GB of RAM.
> Tried first on a FreePBX distro.  When testing on a completely separate CentOS 7 clean install, this issue also happens.  Followed the Asterisk Secure Calling wiki instructions exactly.  Connections are stable when Asterisk is first started and calls can occur successfully over SRTP.
> Telnet to TCP 5061 is successful even after deadlock occurs, but no registrations can occur.  Bria shows "TLS connection errors" in logs.



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



More information about the asterisk-bugs mailing list