[asterisk-bugs] [Asterisk 0018629]: Possible deadlock on 1.6.2.12, 14 and 15

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18629 
====================================================================== 
Reported By:                justintonation
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18629
Category:                   Core/General
Reproducibility:            random
Severity:                   crash
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           1.6.2.15 
JIRA:                       SWP-2961 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2011-01-17 01:22 CST
Last Modified:              2011-02-19 18:51 CST
====================================================================== 
Summary:                    Possible deadlock on 1.6.2.12, 14 and 15
Description: 
After hours to days the system appears to reach a deadlocked state.  SIP
phones lose registration, in-flight calls continue, no new calls can be
established.  Need a "service asterisk restart" to get going again.

Problem is usually first observed when phones lose registration (120
seconds between registrations).

System has never been observed to reach this state overnight or on a
weekend so it appears to only happen when the system is actively handling
calls.


======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0018680 Random deadlocks in channel.c line 2744...
====================================================================== 

---------------------------------------------------------------------- 
 (0132190) justintonation (reporter) - 2011-02-19 18:51
 https://issues.asterisk.org/view.php?id=18629#c132190 
---------------------------------------------------------------------- 
wufan: Sorry not to respond sooner - I have been working on other matters
and missed the update emails.  I did not notice the pattern you describe in
our system although its a bit hard to be 100% sure - the full logs are very
useful but its sometimes hard to spot patterns amongst the detail.

loloski: Our deadlock problems were resolved by reverting to 1.6.2.8 as
suggested by sysreq in issue 18619 - since we reverted we have had several
trouble-free weeks.  Of course its in the nature of things that all
software has bugs so you may need a bit of functionality that is broken in
1.6.2.8 that we just don't notice.  If you have nothing else to go on then
1.6.2.8 may be a good place try to stabilise your site.

I expect to get some time back on Asterisk shortly and intend then to see
if there is anything that looks like it has addressed our issue and will
give it a try.  I also want to try 1.8 but am waiting for more user
experience on how well FreePBX coexists with it - early reports seem
promising. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-02-19 18:51 justintonation Note Added: 0132190                          
======================================================================