[asterisk-bugs] [Asterisk 0012752]: Asterisk stop responding to commands, stop processing calls in and out

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12752 
====================================================================== 
Reported By:                rossnick
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12752
Category:                   Core/PBX
Reproducibility:            random
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.20 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             05-29-2008 07:19 CDT
Last Modified:              06-21-2008 07:52 CDT
====================================================================== 
Summary:                    Asterisk stop responding to commands, stop
processing calls in and out
Description: 
Sometimes, Asterisk just stops working. I notice it with phones getting "No
service" on their display, calls not comming in etc. I almost always have a
console connected, and when I issue commands most of them doesn't do
anything. For exemple, "core show channels" or "core show locks". Some
commands like "sip show peers" only show half of the info.

I compiled with DONT_OPTIMIZE and DEBUG_THREADS and run asterisk inside
gdb (/usr/sbin/asterisk -f -vvvg -c).
====================================================================== 

---------------------------------------------------------------------- 
 Corydon76 - 06-21-08 07:52  
---------------------------------------------------------------------- 
rossnick:  if the process is still running, I'd much rather have a 'core
show locks'.  If the process crashes, then a 'bt', 'bt full', and 'list'
are what are generally useful.  There are some specific cases that need a
'thread apply all ...', but we leave it up to a specific bug marshal on the
bugtracker to determine when it's needed for a particular issue. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
06-21-08 07:52  Corydon76      Note Added: 0089052                          
======================================================================