[asterisk-bugs] [Asterisk 0012376]: Asterisk becomes unresponsive after locking 1.4.19

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12376 
====================================================================== 
Reported By:                DougUDI
Assigned To:                putnopvut
====================================================================== 
Project:                    Asterisk
Issue ID:                   12376
Category:                   General
Reproducibility:            sometimes
Severity:                   crash
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.4.19-rc3 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             04-07-2008 09:26 CDT
Last Modified:              05-22-2008 11:23 CDT
====================================================================== 
Summary:                    Asterisk becomes unresponsive after locking 1.4.19
Description: 
We are runing a high load system using 1.4.19 and have times where asterisk
becomes completely unresponsive and will not allow any incoming or outgoing
calls to or from the system. After a "core show channels" there is no end
channel count and the CLI will become completely unresponsive. I have
attached "core show locks" output.


====================================================================== 

---------------------------------------------------------------------- 
 putnopvut - 05-22-08 11:23  
---------------------------------------------------------------------- 
Thanks for the output. In both scenarios, the channel list lock is held by
a thread calling the function ast_channel_free and is blocking access to
that lock by other threads. That thread, however, does not appear to be
waiting to acquire other locks.

This indicates that some operation or set of operations attempted by
ast_channel_free is taking an excessive amount of time or may even be
blocking indefinitely. In order to pinpoint where the problem is occurring,
I'll need to see a backtrace of that thread when Asterisk deadlocks. The
best way to do this is when the process deadlocks, open a terminal and use
gdb to attach to the running process. Then get the output of "thread apply
all bt full." If you can attach that output here, that would be helpful.
Thanks. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
05-22-08 11:23  putnopvut      Note Added: 0087210                          
======================================================================