[asterisk-bugs] [Asterisk 0014886]: chan_sip deadlock

Mon Apr 27 13:45:17 CDT 2009

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14886 
====================================================================== 
Reported By:                zerohalo
Assigned To:                file
====================================================================== 
Project:                    Asterisk
Issue ID:                   14886
Category:                   Channels/chan_sip/General
Reproducibility:            have not tried
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.24 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-04-13 10:26 CDT
Last Modified:              2009-04-27 13:45 CDT
====================================================================== 
Summary:                    chan_sip deadlock
Description: 
output of 'core show locks' and bt attached

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

---------------------------------------------------------------------- 
 (0103832) zerohalo (reporter) - 2009-04-27 13:45
 http://bugs.digium.com/view.php?id=14886#c103832 
---------------------------------------------------------------------- 
file - my apologies... I seem to be juggling too many things and not paying
enough attention to what I'm posting.

This is a production server using multiple, reliable nameservers that are
monitored for any failures or response-time under 1 second.

There is about a thousand active peers, all of which are accounted for in
the realtime (cached) database. There are many, many more inactive (at
least ~10k) peers, not active here. Average call load for this server is
around 30-50 concurrent calls.

When this occured, peers were not able to register, nor are calls able to
complete.

I'm pretty sure I somehow posted this as a duplicate to the info I posted
in http://bugs.digium.com/view.php?id=14918, 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-04-27 13:45 zerohalo       Note Added: 0103832                          
======================================================================