[asterisk-bugs] [Asterisk 0015609]: [patch] WARNING[23025]: channel.c:952 __ast_queue_frame: Exceptionally long voice queue length queuing to Local

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15609 
====================================================================== 
Reported By:                aragon
Assigned To:                russell
====================================================================== 
Project:                    Asterisk
Issue ID:                   15609
Category:                   Core/Channels
Reproducibility:            have not tried
Severity:                   block
Priority:                   normal
Status:                     confirmed
Target Version:             1.4.28
Asterisk Version:           SVN 
JIRA:                       SWP-205 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!): 206273 
Request Review:              
====================================================================== 
Date Submitted:             2009-07-29 09:26 CDT
Last Modified:              2009-11-11 16:22 CST
====================================================================== 
Summary:                    [patch] WARNING[23025]: channel.c:952
__ast_queue_frame: Exceptionally long voice queue length queuing to Local
Description: 
Since upgrading to 1.4 SVN 206273 I see LOTS these errors when paging or
when calls are processed by app_queue.  When I see the messages during a
page I don't hear any paging (my Polycom phones continue to ring but no
paging audio).

I have no idea where the message is coming from how to reproduce, or
collect debug information for this specific issue.  I need help to find
root cause.
I think it could be caused by locking in autoservice since I see this lock
every time I see the warning message

=== Currently Held Locks ==============================================
=======================================================================
===
=== <file> <line num> <function> <lock name> <lock addr> (times locked)
===
=== Thread ID: 3057154960 (autoservice_run      started at [  238]
autoservice.c ast_autoservice_start())
=== ---> Waiting for Lock https://issues.asterisk.org/view.php?id=0
(autoservice.c): MUTEX 89 autoservice_run
&(&aslist)->lock 0x81798c8 (1)
=== --- ---> Locked Here: autoservice.c line 89 (autoservice_run)
=== -------------------------------------------------------------------


======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
duplicate of        0015976 abort in filestream_destructor / ast_fi...
related to          0015109 [patch] Abort by memory allocator, poss...
has duplicate       0015900 Console flood &amp; CPU load 100% when ...
has duplicate       0016096 Exceptionally long voice queue length q...
related to          0015817 crash in local_attended_transfer, likel...
related to          0015845 Crash during attended transfer occurs
related to          0015616 random crashes
====================================================================== 

---------------------------------------------------------------------- 
 (0113688) aragon (reporter) - 2009-11-11 16:22
 https://issues.asterisk.org/view.php?id=15609#c113688 
---------------------------------------------------------------------- 
We have been converting agi to fastagi and reduce CPU loads a lot.
With latest SVN-branch-1.4-r229091M  I have yet to see autoservice
problem
Load average at approx 15cps is about .3 on test rig.
WARNINGS only occur during hangups
During WARNINGS load spikes to 1.5 and keeps climbing until WARNINGS
disappear.
Even with decreased loads on CPU the WARNINGS are VERY spammy and do
indicate service affecting issues.

Issuing some core show locks commands I have seen this...
=== Currently Held Locks ==============================================
=======================================================================
===
=== <file> <line num> <function> <lock name> <lock addr> (times locked)
===
=== Thread ID: -1232684144 (pbx_thread           started at [ 2624] pbx.c
ast_pbx_start())
=== ---> Tried and failed to get Lock https://issues.asterisk.org/view.php?id=0
(channel.c): MUTEX 2078
__ast_read &chan->lock 0xa06dad0 (0)

Other than this I have nothing else to report.  My team has made zero
progress on reducing the WARNINGS or fixing the underlying bug.  However we
have made huge improvements in load averages converting to fastagi
scripts.... but with the decreased load and hugely improved script
efficiency we are able to handle more calls and now the WARNINGS/underlying
bug are even worse. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-11-11 16:22 aragon         Note Added: 0113688                          
======================================================================