Summary:	ASTERISK-07504: MixMonitor crash
Reporter:	Armando Leal (arleal)	Labels:
Date Opened:	2006-08-09 19:48:37	Date Closed:	2011-06-07 14:00:57
Priority:	Critical	Regression?	No
Status:	Closed/Complete	Components:	Applications/app_mixmonitor
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:	( 0) core.txt ( 1) debug1.txt
Description:	Crashing in deallocation of chan->spies
Comments:	By: Armando Leal (arleal) 2006-08-09 21:44:27 -- Executing Dial("SIP/508-be05", "Zap/r2/015556430849") in new stack Aug  9 21:41:59 DEBUG[31583]: dsp.c:1619 ast_dsp_set_busy_pattern: dsp busy patt                                                                             ern set to 0,0 Aug  9 21:41:59 DEBUG[31583]: chan_zap.c:1916 zt_call: Dialing '015556430849' Aug  9 21:41:59 DEBUG[31583]: chan_zap.c:1988 zt_call: Deferring dialing... Aug  9 21:41:59 DEBUG[26660]: channel.c:777 channel_find_locked: Avoiding initia                                                                             l deadlock for 'Zap/5-1' Aug  9 21:41:59 DEBUG[26660]: channel.c:777 channel_find_locked: Avoiding initia                                                                             l deadlock for 'Zap/5-1' Aug  9 21:41:59 DEBUG[26660]: channel.c:777 channel_find_locked: Avoiding initia                                                                             l deadlock for 'Zap/5-1' Aug  9 21:41:59 DEBUG[26660]: channel.c:777 channel_find_locked: Avoiding initia                                                                             l deadlock for 'Zap/5-1' Aug  9 21:41:59 DEBUG[26660]: channel.c:777 channel_find_locked: Avoiding initia                                                                             l deadlock for 'Zap/5-1' Aug  9 21:41:59 DEBUG[26660]: channel.c:777 channel_find_locked: Avoiding initia                                                                             l deadlock for 'Zap/5-1'    -- Called r2/015556430849 Aug  9 21:41:59 DEBUG[31584]: channel.c:1011 ast_channel_spy_add: Spy MixMonito By: Armando Leal (arleal) 2006-08-09 21:48:28 This is when it appears. By: Jeffrey C. Ollie (jcollie) 2006-08-09 21:54:04 Have you tried updating to 1.2.10? By: Tilghman Lesher (tilghman) 2006-08-09 22:30:21 This is a crash, not a deadlock. By: Armando Leal (arleal) 2006-08-09 23:55:12 when ever I call an extension or a zap.. I get channel.c:777 channel_find_locked: Avoiding initial deadlock this server actually had 1.0.9 I upgraded fist to 1.2.10. Yeah I installed 1.2.10, and had the same problems, and went back to 1.2.9.1 cause I had another server with it without problems.. By: Serge Vecher (serge-v) 2006-08-10 08:48:33 arleal: we still need to see a backtrace from 1.2.10, because there were important changes to MixMonitor made between 1.2.9 and 1.2.10. Please make sure that: 1) you build Asterisk with 'make dont-optimize' 2) Use unmodified sources straight from the tarball 3) You may also want to include a bit of a console log preceeding the crash too see what's happening. Thanks. By: lesnet (lesnet) 2006-08-14 09:31:47 If it helps cooroborate the issue with MixMonitor crashing.. I've been running 1.2.9.1 for a while, and MixMonitor was solid. I upgraded to 1.2.10 and MixMonitor crashes the box regularly. Unfortunately, I've never seen the console after a crash, but my debug log shows evidence that MixMonitor is the culprit. The last time was this morning. /var/log/asterisk/debug shows: Aug 14 09:13:39 VERBOSE[1772] logger.c:   == End MixMonitor Recording Zap/15-1 Then no further entries until I restarted. One thing to note, is that I'm not using chanspy during mixmonitor (as this bug seems to relate to).  Just a simple dialplan to record calls. By: Serge Vecher (serge-v) 2006-08-14 10:07:42 lesnet: thanks for confirmation, we still need a backtrace as per note 0050154 By: Serge Vecher (serge-v) 2006-08-25 11:21:06 will close this bug if no response received within a week. By: Joshua C. Colp (jcolp) 2006-09-05 15:07:04 Feedback was not received in time, but try latest 1.2 branch and give it a go.