|Summary:||ASTERISK-12710: Crash - call to agent channel when agent is logging in.|
|Reporter:||Alan Graham (zerohalo)||Labels:|
|Date Opened:||2008-09-10 14:22:12||Date Closed:||2011-06-07 14:00:40|
|Environment:||Attachments:||( 0) bt.txt|
|Description:||When logging as an Agent via manager call and a call was being delivered to the queue asterisk locked up and the CLI became unresponsive. BT attached.|
|Comments:||By: Alan Graham (zerohalo) 2008-09-10 14:48:33|
description should read: CLI became unresponsive to commands and calls were not progressing when this happened. Agent channel was logging into queue at the same time that an incoming calls was being delivered to the queue.
By: Mark Michelson (mmichelson) 2008-09-11 11:40:24
Sounds like a deadlock to me. Did you happen to have Asterisk compiled with DEBUG_THREADS enabled in menuselect when you had this happen? Also by chance, do you still have the core dump on your system? And finally if the answer to the first two questions is yes, would you be willing to give a developer ssh access to your system to inspect the core dump further?
By: Alan Graham (zerohalo) 2008-09-11 12:28:41
compiled with DEBUG_THREADS and DONT_OPTIMIZE - forwarding contact information to you now.
By: Mark Michelson (mmichelson) 2008-09-11 13:36:44
I wasn't able to get any useful information off the core file due to ?? stack frames in the threads which were waiting for locks. I already indicated this in an e-mail to you, but I just want to repeat this here in case this same problem occurs to anyone else.
What's needed here is the output of the command "core show locks" when this deadlock occurs. If I can get output of that, then it will help me in debugging the issue. If the CLI is unresponsive as zerohalo indicated, I usually find that starting a new remote console with asterisk -r allows me to start entering commands properly again.
By: Joshua C. Colp (jcolp) 2008-12-18 10:47:40.000-0600
zerohalo: Any progress getting the needed information?
By: Tilghman Lesher (tilghman) 2009-01-16 14:31:16.000-0600
No response from reporter