[asterisk-bugs] [Asterisk 0013136]: [patch] sip peer qualified failed, asterisk lock.

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13136 
====================================================================== 
Reported By:                pabelanger
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   13136
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           1.6.0 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-07-23 02:32 CDT
Last Modified:              2008-11-19 00:19 CST
====================================================================== 
Summary:                    [patch] sip peer qualified failed, asterisk lock.
Description: 
We just had asterisk lock on us tonight.  Best we can guess is because we
lost our SIP PEER (via qualify).

See output from 'show core locks'.
====================================================================== 

---------------------------------------------------------------------- 
 (0095050) Corydon76 (administrator) - 2008-11-19 00:19
 http://bugs.digium.com/view.php?id=13136#c95050 
---------------------------------------------------------------------- 
I've evaluated most of those commands and determined that most of the
errors were not relevant or possible, with the given arguments, but it's
possible that I might have missed some.

In terms of O_NONBLOCK, the existing code already clears that flag in code
following the connect, so it was unnecessary to do that again.  In fact,
I'm not really sure why it was there in the first place, as the socket
would otherwise block, by default.

It's possible that the write() blocks, but I don't think that's likely,
given that poll() indicated that a write() should not block.  As to what
exactly is blocking, that can be determined by connecting to Asterisk with
gdb and running a 'thread apply all bt'.  I suspect it's still blocking in
the connect() for some reason that I can't divine, but testing is needed to
confirm that. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-11-19 00:19 Corydon76      Note Added: 0095050                          
======================================================================