[asterisk-bugs] [JIRA] (ASTERISK-26956) Exceptionally long voice > queue length queuing

[Ted G (JIRA)]

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

Ted G commented on ASTERISK-26956:
----------------------------------

Im still watching.  Some of my users were reporting their keys would suddenly stop responding and the system would go silent.  Playing around with a simply C script (https://community.asterisk.org/t/c-issue-wait-for-digit/70493) I noticed that I would not receive any results back from key presses so I was thinking maybe the user getting locked up and not able to do anything caused a cascade that led to a lockup.   When I fixed the open ports to match rtp.conf the issues went away so I'm hoping the 'Exceptionally long voice queue' issues will go away as well.  So far I have not seen any since I have made the change.  Once I'm at at least 3 days without issue I will consider the matter solved.


>  Exceptionally long voice > queue length queuing
> ------------------------------------------------
>
>                 Key: ASTERISK-26956
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26956
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 14.4.0
>         Environment: Debian GNU/Linux 8.7 (jessie)
>            Reporter: Ted G
>            Assignee: Ted G
>         Attachments: backtrace-threads.20170423.txt, core-show-locks.20170423.txt
>
>
> Hello,
>   I am getting tons of these messages in my logs a few times a day which causes my system to be completely dead:
> [Apr 20 21:39:15] WARNING[24491][C-00000197]: channel.c:1162 _astqueue_frame: Exceptionally long voice queue length queuing to Local/s at announce-0000015b;1
> [Apr 23 15:32:06] WARNING[20645] channel.c: Exceptionally long voice queue length queuing to CBAnn/12-000001f0;1
> I am having a very difficult time figuring out what is causing it other than 'its a channel deadlock' which doesn't really tell me how to fix the issue.  This just started happening around ~6 days ago.
> This problem is extremely catastrophic as the only fix is to completely restart the asterisk system.
> Included are backtrace and core-show-locks logs.  Please assist this desperate fool. :)



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