|Summary:||ASTERISK-07039: deadlock somewhere, channels get locked|
|Date Opened:||2006-05-25 23:47:28||Date Closed:||2006-05-26 12:33:24|
|Environment:||Attachments:||( 0) asterisk_bt_20060526_2.txt|
|Description:||we have got a deadlock in Asterisk. see attached backtrace.|
in console, if i issue 'show channels', i see this stalled channel, and error message about it:
*CLI> show channels
Channel Location State Application(Data)
SIP/1317-dd41 (None) Up Bridged Call(SIP/1123-1b7f)
1 active channel
1 active call
May 26 08:31:48 WARNING: channel.c:787 channel_find_locked: Avoided deadlock for '0x40b454b8', 10 retries!
also, the evening before today, asterisk was talking this to log\console:
May 25 20:43:08 WARNING: channel.c:787 channel_find_locked: Avoided initial deadlock for '0x40b454b8', 10 retries!
May 25 20:43:22 WARNING: channel.c:787 channel_find_locked: Avoided initial deadlock for '0x40b454b8', 10 retries!
May 25 20:43:36 WARNING: channel.c:787 channel_find_locked: Avoided initial deadlock for '0x40b454b8', 10 retries!
(and so on, every 10-20 seconds)
i was unable to get bt that evening (incoming calls), but just for now, there are no such messages.
****** ADDITIONAL INFORMATION ******
it seems to me, that this issue is fully related to issue 6997. this is the same Asterisk, and the same configuration.
it looks like the same lock, but not in chan_zap, but in chan_sip.
so, i'm setting the same severity, cause this bug can lock chan_zap as in 6997, which leads Asterisk to become unusabe.
|Comments:||By: Serge Vecher (serge-v) 2006-05-26 12:21:53|
caspy: please checkout the latest 1.2 branch code (>rev. 30546). A fix was just committed that should resolve the locking issues in app_queue. Also, for the future, if the problem is fully related to an existing bug, please post relevant debugging material in that open bug instead of opening a new one. Report results of whether the issue is fixed or not in 6997. Thank you!