[asterisk-bugs] [JIRA] (ASTERISK-27417) Endpoints not getting registered

[Richard Mudgett (JIRA)]

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

Richard Mudgett commented on ASTERISK-27417:
--------------------------------------------

You appear to have a deadlock associated with res_hep_rtcp.c.  [^core_show_taskprocessors.txt] shows that {{subm:rtp_topic-000000cc}} is blocked from processing messages in its queue.  This is why {{subm:rtp_topic-000000cc}} shows a large number of tasks in its queue but the max queue depth is lower.  Thread 62 is the dedicated thread processing {{subm:rtp_topic-000000cc}}.  That thread is waiting on Thread 84 which is handling the session serializer to process the request.  Thread 84 is blocked waiting for a bridge lock.  However, I am not able to find which thread is holding the bridge lock to continue the blocking chain.

You need to enable DEBUG_THREADS in menuselect [1][2] to enable lock tracking.

[1] https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace
[2] https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace#GettingaBacktrace-GettingInformationForADeadlock

Also, if you don't need the Homer (HEPv3 logger) functionality you shouldn't load the res_hep* modules as it seems to be triggering your deadlock.

> Endpoints not getting registered
> --------------------------------
>
>                 Key: ASTERISK-27417
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27417
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: pjproject/pjsip
>    Affects Versions: 13.18.2
>         Environment: Ubuntu 16.04,PJSIP_2.6,webrtc
>            Reporter: shaurya jain
>            Severity: Critical
>         Attachments: core_show_channels_concise.txt, core_show_taskprocessors.txt, ERROR_logs.txt, sterling.txt
>
>
> Endpoints were not getting registered after the attached error,and after that we need to restart the asterisk to make the things working.
> Attached are the GDB and other relevant logs,



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