Summary:	ASTERISK-20190: WARNING messages spammed :"channel.c: Exceptionally long voice queue length queuing to ..." CPU usage spikes and all extensions enter InUse or OnHold
Reporter:	Alexander Cruz (chandero)	Labels:
Date Opened:	2012-08-02 10:25:20	Date Closed:	2012-08-29 09:01:26
Priority:	Major	Regression?
Status:	Closed/Complete	Components:
Versions:	1.8.11.1 1.8.14.1	Frequency of Occurrence	Occasional
Related Issues:
Environment:	Linux CentOS 6 kernel 2.6.32-71.el6.x86_64, 2GB RAM, 5 queues, 3 with strategy=ringall, 2 with strategy=roundrobin, error message in queue with strategy=roundrobin, agents Local/012@agents, Local/018@agents, ....	Attachments:	( 0) asterisklog.txt
Description:	occur before the blockade, log file show the following error message [Aug  2 09:31:12] WARNING[11780] channel.c: Exceptionally long voice queue length queuing to Local/012@agents-176a;2 then CPU load goes to 900% and up. uptime command show 10:35:29 up 3 days, 14 min,  2 users,  load average: 9.05, 9.89, 9.75 then all extensions stay on InUse state or OnHold state. Solutions reboot asterisk.
Comments:	By: Rusty Newton (rnewton) 2012-08-02 17:35:29.337-0500 attached reporters log output, removed from reference notes By: Rusty Newton (rnewton) 2012-08-02 17:44:40.539-0500 Debugging deadlocks: Please select DEBUG_THREADS and DONT_OPTIMIZE in the Compiler Flags section of menuselect. Recompile and install Asterisk (i.e. make install).  This will then give you the console command "core show locks." When the symptoms of the deadlock present themselves again, please provide output of the deadlock via: # asterisk -rx "core show locks" | tee /tmp/core-show-locks.txt # gdb -se "asterisk" <pid of asterisk> | tee /tmp/backtrace.txt gdb> bt gdb> bt full gdb> thread apply all bt Then attach the core-show-locks.txt and backtrace.txt files to this issue. Thanks! If this issue can be reproduced, please describe how to reproduce the issue. Please additionally provide an Asterisk full log with VERBOSE and DEBUG messages of at least level 5 enabled. Include a log that covers several minutes before the issue occurs if the file is not too large. *Please attach the file as a text file and compressed if necessary* queue configuration or dialplan files will be helpful as well. By: Matt Jordan (mjordan) 2012-08-29 09:01:17.499-0500 Suspended due to lack of activity. Please request a bug marshal in #asterisk-bugs on the IRC network irc.freenode.net to reopen the issue should you have the additional information requested.  Further information can be found at http://www.asterisk.org/developers/bug-guidelines By: Alexandre Keller (alexandrekeller) 2013-03-25 08:13:12.004-0500 What's the solution? I've been having a similar situation. Thanks. By: Rusty Newton (rnewton) 2013-03-28 09:56:11.694-0500 The reporter didn't respond with any debug. We didn't identify a bug or a solution. If you can provide the requested debug then you may want to file a new issue and attach all the requested information to it.