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

[Phi Tran (JIRA)]

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

Phi Tran edited comment on ASTERISK-25653 at 2/1/16 1:25 PM:
-------------------------------------------------------------

Sorry - this is still happening.  It seems like it takes longer (a couple of weeks), but it deadlocks again.  The Recv-Q for the connections that were open are in the thousands.  What other information should I submit?


was (Author: pixel):
Sorry - this is still happening.  It seems like it takes longer (a couple of weeks), but it deadlocks again.  The Recv-Q for the connections that were open are in the hundreds and the thousands.  What other information should I submit?

> 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: Unassigned
>         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)