Summary:	ASTERISK-05162: Deadlocks - manager?
Reporter:	wunderkin (wunderkin)	Labels:
Date Opened:	2005-09-27 12:38:01	Date Closed:	2005-10-04 13:34:31
Priority:	Blocker	Regression?	No
Status:	Closed/Complete	Components:	Core/General
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:	( 0) gdb ( 1) gdb-050928-mgr ( 2) gdb-2
Description:	I have 2 deadlock logs attached.  It seems to be randomly deadlocking even with 1 call.  It is happening quite frequently for me now.  It happened twice last night and twice again today. I'm using the latest -HEAD.  I'm generating an outbound call via a Manager Origionate command.  I'm only using *1* constantly connected manager connection. All of my processes have pretty much been the same.  I've done the same thing with previous versions of Asterisk without having so frequent deadlocks.
Comments:	By: Mark Spencer (markster) 2005-09-28 23:10:27 Please update to latest CVS head, as I've made lots of manager improvements that *may* fix your problem.  If you can still duplicate the issue, please call Digium and ask for me, referencing this bug, and I'll want to login to your system to diagnose.  Thanks! By: wunderkin (wunderkin) 2005-09-29 01:22:57 Thanks Mark.  All went well during the testing.  I was ready to head to bed and closed out the processes.  I had 2 connections to the manager.  Closed those out (PHP scripts - I hit Control-C on them), looked at the Asterisk console (getting ready to to stop it).. and bam.. deadlock again :( I uploaded gdb-050928-mgr which is with -HEAD shortly after the manager patches. I may have another deadlock too (probably from IAX) that I need to try again and see if I still have the problems.  I've been testing with PRI right now.   (Before the fix): I changed to using callfiles as a band-aid fix to this problem.  I tested using PRI -- worked great.  As soon as I added IAX2 into the picture, it deadlocked.  I'll take a look again in the morning. By: Mark Spencer (markster) 2005-10-04 13:04:02 This new updated deadlock issue has already been fixed in CVS head.  Reopen if you continue to have trouble. By: Mark Spencer (markster) 2005-10-04 13:04:10 This new updated deadlock issue has already been fixed in CVS head.  Reopen if you continue to have trouble.