[asterisk-bugs] [JIRA] (ASTERISK-26956) Exceptionally long voice > queue length queuing
Ted G (JIRA)
noreply at issues.asterisk.org
Tue Apr 25 14:48:57 CDT 2017
[ https://issues.asterisk.org/jira/browse/ASTERISK-26956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=236689#comment-236689 ]
Ted G commented on ASTERISK-26956:
----------------------------------
Its very difficult to diagnose because all this debugging stuff puts an enormous strain on my system.
Here is what I have noticed. It seems to be mostly local channels, i.e.: Local/s at announce-0000015b
My purpose for these is to play announcements into conferences so that everyone can hear them and thus to create these I do the following:
Create a call file like so and move it to: /var/spool/asterisk/outgoing
Channel: Local/s at announce
Set: ARG1=11
Application: Playback
Data: /opt/sipx/wav/msg1&/opt/sipx/wav/msg2
Which triggers an event in extensions.conf:
[announce]
exten => s,1,NoOp
same => n,Answer
same => n,ConfBridge(${ARG1},bridge,user)
same => n,Hangup
So maybe something with that method is causing these channels to deadlock somehow. Ive been doing this for more than a year and this problem only cropped up a ~week ago.
> 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
> 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)
More information about the asterisk-bugs
mailing list