|Summary:||ASTERISK-17697: Deadlocks on 188.8.131.52.2|
|Date Opened:||2011-04-15 09:31:08||Date Closed:||2011-06-07 14:00:33|
|Environment:||Attachments:||( 0) backtrace.txt|
( 1) channels-locks.txt
( 2) coreshowlocks.txt
( 3) core-show-locks.txt
( 4) features.conf
|Description:||Getting deadlocks on 184.108.40.206.2. I suspect MixMonitor() is causing them, but I'm not sure. Unfortunely I couldn't get a backtrace, but the output of 'core show locks' is attached below.|
|Comments:||By: Bradley Watkins (marquis) 2011-04-18 17:10:50|
Unfortunately, I don't see where the 'core show locks' output shows a deadlock. I see multiple threads waiting on one WRLOCK, but not where it is held. If this is reproducible, can you try and post another output that shows this information?
By: viniciusfontes (viniciusfontes) 2011-04-25 06:42:57
Not reproducible, but it just happened again. I attached the output of 'core show channels verbose' and 'core show locks' (same file).
By: Paul Belanger (pabelanger) 2011-04-25 21:09:46
Please select DEBUG_THREADS and DONT_OPTIMIZE in the Compiler Flags section of menuselect. Recompile and install Asterisk (i.e. make install)
This will then give you the console command:
core show locks
When the symptoms of the deadlock present themselves again, please provide output of the deadlock via:
# asterisk -rx "core show locks" | tee /tmp/core-show-locks.txt
# gdb -se "asterisk" <pid of asterisk> | tee /tmp/backtrace.txt
gdb> bt full
gdb> thread apply all bt
Then attach the core-show-locks.txt and backtrace.txt files to this issue. Thanks!
By: Leif Madsen (lmadsen) 2011-05-10 15:34:16
Closed as a duplicate of ASTERISK-17264
By: Leif Madsen (lmadsen) 2011-05-11 15:51:15
Reopening after testing from rmudgett leads us to believe this is not a duplicate of the other issue.
By: Leif Madsen (lmadsen) 2011-05-11 15:52:05
Do you happen to have pickupsound and/or pickupfailsound specified in features.conf?
By: viniciusfontes (viniciusfontes) 2011-05-12 14:30:04
Just had a deadlock again. I'm attaching the output requested by pabelanger as well as my features.conf.
By: JoshE (n8ideas) 2011-05-12 14:48:52
Looks to me like you are actually experiencing this issue ASTERISK-1854791. This particular deadlock path hasn't reoccurred for me after applying this patch chan_sip.rtptimeout.patch from that issue.
By: Richard Mudgett (rmudgett) 2011-05-12 18:52:06
The deadlock files show two different deadlocks.
The coreshowlocks.txt and channel-locks.txt should be fixed by the v1.6.2 version of ASTERISK-17264.
The core-show-locks.txt looks like an unbalanced lock where a channel was left locked somewhere.
By: Leif Madsen (lmadsen) 2011-05-16 08:13:56
Due to the end of support for Asterisk 1.6.2, and the closure of related issues that may resolve this issue in 1.8, I'm going to close this issue. Please re-test with Asterisk 1.8, and if you continue to have problems there, please open a new issue.
Per the Asterisk maintenance timeline page at http://www.asterisk.org/asterisk-versions maintenance (bug) support for the 1.4 and 1.6.x branches has ended. For continued maintenance support please move to the 1.8 branch which is a long term support (LTS) branch.
For more information about branch support, please see https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions