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

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=13136 
====================================================================== 
Reported By:                pabelanger
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   13136
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     confirmed
Asterisk Version:           SVN 
JIRA:                        
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2008-07-23 02:32 CDT
Last Modified:              2009-09-28 16:12 CDT
====================================================================== 
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'.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
parent of           0015894 SIP register via tls causes lock on sip...
====================================================================== 

---------------------------------------------------------------------- 
 (0111475) dvossel (administrator) - 2009-09-28 16:12
 https://issues.asterisk.org/view.php?id=13136#c111475 
---------------------------------------------------------------------- 
here is what is going on... The TCP connection setup is done while it holds
the monitor thread.  If the connect() function in ast_tcptls_client_start
does not timeout, the monitor lock may be held indefinitely.  There is a
patch for this up on reviewboard, https://reviewboard.asterisk.org/r/380/.


--------- This thread is stuck at the connect() function while holding the
monitor lock -----
https://issues.asterisk.org/view.php?id=0  0xb7f0f410 in __kernel_vsyscall ()
No symbol table info available.
https://issues.asterisk.org/view.php?id=1  0xb7e91e18 in connect () from
/lib/tls/i686/cmov/libc.so.6
No symbol table info available.
https://issues.asterisk.org/view.php?id=2  0x08153933 in ast_tcptls_client_start
(desc=0xb6bdb910) at
tcptls.c:301
	flags = 135607986
	ser = (struct ast_tcptls_session_instance *) 0x0
	ssu = {tid = 3065899920, schedid = -1}
	__PRETTY_FUNCTION__ = "ast_tcptls_client_start"
	__FUNCTION__ = "ast_tcptls_client_start"
https://issues.asterisk.org/view.php?id=3  0xb6c482df in sip_prepare_socket
(p=0x8319f28) at chan_sip.c:18733 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-09-28 16:12 dvossel        Note Added: 0111475                          
======================================================================