[asterisk-bugs] [JIRA] (ASTERISK-20190) WARNING messages spammed :"channel.c: Exceptionally long voice queue length queuing to ..." CPU usage spikes and all extensions enter InUse or OnHold

[Rusty Newton (JIRA)]

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

Rusty Newton commented on ASTERISK-20190:
-----------------------------------------

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.
                
> WARNING messages spammed :"channel.c: Exceptionally long voice queue length queuing to ..."  CPU usage spikes and all extensions enter InUse or OnHold
> ------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-20190
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20190
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 1.8.11.1, 1.8.14.1
>         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 at agents, Local/018 at agents, ....
>            Reporter: Alexander Cruz
>            Assignee: Rusty Newton
>         Attachments: asterisklog.txt
>
>
> 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 at 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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira