[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-23-2008 07:09 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.


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

---------------------------------------------------------------------- 
 destiny6628 - 05-23-08 07:09  
---------------------------------------------------------------------- 
Today had the same problem where show channels command stopped working and
both incoming and outgoing calls stopped .

At that time have taken the output of core show locks as well and have
upload the output by the name of core show locks-1.txt .

2) Have the taken the gdb output of the asterisk process using thread
apply all bt full as well .

The output is attached by the name backtrace.txt .

Hope this helps us in getting to the cause of the problem .

Thanks 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
05-23-08 07:09  destiny6628    Note Added: 0087243                          
======================================================================