Summary:ASTERISK-11489: Multiple deadlock / show channels freeze on Queues 1.4.16/17
Reporter:Doug (doug)Labels:
Date Opened:2008-02-21 01:51:59.000-0600Date Closed:2008-04-15 10:34:21
Versions:Frequency of
Description:I have a problem that was patched in the past and this did solve the issue untill lately. We get calls that will get stuck in the queue and never be passed to an agent, the Zap channel is open but the caller has hung up. Seems like a deadlock related to queues. The original ticket 0011730 was succefully patched, but some how this problem has started again. Show channels has output but does not give a final channel count and afer this command the CLI becomes unreponsive very much like the problem in ticket 0011712. When we have a call in the queue that gets stuck Asterisk will cause load ave to get extreamly high in the ranges of 300.0. The only way to clear this error is to restart Asterisk. I will try and recompile a debug version of Asterisk to collect the lock info as did last time.
Comments:By: Russell Bryant (russell) 2008-02-21 09:04:46.000-0600

The first thing that you need to do is to update to the latest version (1.4.18).

By: Joel Vandal (jvandal) 2008-02-21 10:08:37.000-0600

They already use Asterisk 1.4.18 but I will check with Doug to recompile Asterisk with DEBUG_THREADS option enabled.

By: Joel Vandal (jvandal) 2008-02-21 13:25:02.000-0600

FYI the category is wrong, we do not use chan_agent on our systems.

By: Russell Bryant (russell) 2008-02-29 17:14:19.000-0600

ok, well let us know if you get this to happen with DEBUG_THREADS and can get "core show locks" output

By: Mark Michelson (mmichelson) 2008-04-09 14:06:50

Ping. has the issue happened again?

By: Joel Vandal (jvandal) 2008-04-09 16:05:29

Will check with DougUDI tomorrow in morning about this issue, but at my knowledge, this must be fixed with 1.4.19.

Will let you know ASAP.

By: Joshua C. Colp (jcolp) 2008-04-14 11:19:23

So is this still an issue?

By: Joel Vandal (jvandal) 2008-04-15 09:52:03

IMHO you can close this issue, we now use Asterisk 1.4.19 and this look to be fixed.

By: Mark Michelson (mmichelson) 2008-04-15 10:34:13

Closing as per the latest bug note.