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

Asterisk Bug Tracker noreply at bugs.digium.com
Wed Apr 22 08:57:30 CDT 2009


The following issue requires your FEEDBACK. 
====================================================================== 
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-22 08:57 CDT
====================================================================== 
Summary:                    chan_sip deadlock
Description: 
output of 'core show locks' and bt attached


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

---------------------------------------------------------------------- 
 (0103619) file (administrator) - 2009-04-22 08:57
 http://bugs.digium.com/view.php?id=14886#c103619 
---------------------------------------------------------------------- 
After looking at this core show locks and backtrace I see two things:

The devicestate code is doing a DNS lookup on the name of a peer. This
should only happen if the peer doesn't exist and it should also not take
that long. Is your configuration proper with that peer configured and is
your server setup with working/reliable nameservers?

Secondly the scheduler looks to be rescheduling things, which is perfectly
normal and should not cause a deadlock.

What exactly did you experience that made you consider this a deadlock?
What couldn't you do? What were you doing? What sort of call capacity does
the machine run? How many configured entries in sip.conf? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-04-22 08:57 file           Note Added: 0103619                          
2009-04-22 08:57 file           Status                   assigned => feedback
======================================================================




More information about the asterisk-bugs mailing list