[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-01-24 18:31 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.


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

---------------------------------------------------------------------- 
 (0130972) justintonation (reporter) - 2011-01-24 18:31
 https://issues.asterisk.org/view.php?id=18629#c130972 
---------------------------------------------------------------------- 
Thanks lmadsen - I appreciate it.  I am happy to do what I can to assist in
further debugging this issue.

I ended up putting 1.6.2.8 (with DONT-OPTIMIZE and without DEBUG-THREADS)
into production this week as I felt I had to throw the users a bone and try
and give them a more stable platform, if only until the next round of
testing.

So far (Monday and half of Tuesday here) we have had about 550 calls
through the system with no lockups.  That's by no means a record and we
have a Public Holiday for Australia Day this Wednesday so my sense is that
the workload is a little subdued.  Still, its looking promising as a
reliable release in our environment for the moment.  Maybe this helps to
localise the change that has introduced this presumed deadlock?

As I say, I'm happy to test something else if I can (I've not use SVN
before but I expect I can make it work given time). 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-01-24 18:31 justintonation Note Added: 0130972                          
======================================================================