[asterisk-bugs] [Asterisk 0015637]: Deadlock after peer answeres queue call

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15637 
====================================================================== 
Reported By:                cstadlmann
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15637
Category:                   Core/Channels
Reproducibility:            random
Severity:                   crash
Priority:                   normal
Status:                     new
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!): 204834 
Request Review:              
====================================================================== 
Date Submitted:             2009-08-03 08:43 CDT
Last Modified:              2009-08-05 09:54 CDT
====================================================================== 
Summary:                    Deadlock after peer answeres queue call
Description: 
We have the following set up:

Asterisk is hosting a queue with 4 members, ring strategy 'least recent'.
The complete setup is realtime, but I don't think this has anything to do
with the deadlock.

The queue is playing MOH, which is a wav-file (no .mp3). After the SIP
peer answeres the call, MOH stops playing, and exactly in this moment the
deadlock occurs.

It does not matter if queue members are 'Local/' or 'SIP/' channels,
patching Asterisk as stated in Bug 14112 only makes the deadlock occur
every 6 hours, with SIP channels the deadlock occurs every 3 hours or so.

The only way to get Asterisk running again is to 'kill -9' the process. No
other CLI command than one 'core show locks' is working, any subsequent CLI
command does not produce any response anymore.
====================================================================== 

---------------------------------------------------------------------- 
 (0108655) cstadlmann (reporter) - 2009-08-05 09:54
 https://issues.asterisk.org/view.php?id=15637#c108655 
---------------------------------------------------------------------- 
Asterisk just crashed again...

smartelpbx*CLI> core show locks
smartelpbx*CLI>
=======================================================================
=== Currently Held Locks ==============================================
=======================================================================
===
=== <file> <line num> <function> <lock name> <lock addr> (times locked)
===
=== Thread ID: 3062631312 (do_monitor           started at [16811]
chan_sip.c restart_monitor())
=== ---> Lock https://issues.asterisk.org/view.php?id=0 (chan_sip.c): MUTEX
16659 do_monitor &iflock 0xb6944fa0
(1)
=== ---> Lock https://issues.asterisk.org/view.php?id=1 (chan_sip.c): MUTEX
16671 do_monitor &sip->lock 0x83d6640
(1)
=== ---> Waiting for Lock https://issues.asterisk.org/view.php?id=2 (pbx.c):
MUTEX 5785 pbx_builtin_getvar_helper
(channel lock) 0x839ac68 (1)
=== --- ---> Locked Here: channel.c line 2565 (ast_indicate_data)
=== -------------------------------------------------------------------
===
=== Thread ID: 3060509584 (session_do           started at [ 2522]
manager.c accept_thread())
=== ---> Lock https://issues.asterisk.org/view.php?id=0 (manager.c): RDLOCK 2281
process_message &actionlock
0x81b6ac0 (1)
=== ---> Tried and failed to get Lock https://issues.asterisk.org/view.php?id=1
(channel.c): MUTEX 1127
channel_find_locked (channel lock) 0x839ac68 (0)
=== -------------------------------------------------------------------
===
=== Thread ID: 3059051408 (pbx_thread           started at [ 2597] pbx.c
ast_pbx_start())
=== ---> Lock https://issues.asterisk.org/view.php?id=0 (channel.c): MUTEX 2565
ast_indicate_data (channel lock)
0x839ac68 (1)
=== ---> Waiting for Lock https://issues.asterisk.org/view.php?id=1
(chan_sip.c): MUTEX 4017 sip_indicate
&p->lock 0x83d6640 (1)
=== --- ---> Locked Here: chan_sip.c line 16671 (do_monitor)
=== -------------------------------------------------------------------
===
=======================================================================

Maybe the whole issue has something to do with indication and sip notify
message processing? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-08-05 09:54 cstadlmann     Note Added: 0108655                          
======================================================================