|Summary:||ASTERISK-17868: deadlock while reload|
|Date Opened:||2011-05-16 17:49:15||Date Closed:||2011-07-26 14:30:02|
|Environment:||Attachments:||( 0) backtrace.2011-05-17-04:45:05.txt|
( 1) locks.2011-05-17-04:45:05.txt
|Description:||I was able to make asterisk deadlocked issuing multiple reload commands from CLI.|
|Comments:||By: Leif Madsen (lmadsen) 2011-05-17 07:25:02|
Can you reproduce this every time? Can you reproduce this on Asterisk 1.8?
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
By: jamhed (jamhed) 2011-05-17 07:53:52
I was able to do that 3 times in a row, that's why I decided it is reproduceable. I can try to do that with asterisk 1.8 later.
By: Lott Caskey (lottc) 2011-05-17 15:09:51
I have verified that this also happens in 1.8.4.
Issue reload multiple times..
[May 17 15:53:49] == Parsing '/etc/asterisk/cdr.conf': [May 17 15:53:49] == Found
...verbose reload messages...
[May 17 15:53:49] -- Added extension '_2020' priority 1 to default
Asterisk then will not acknowledge further commands, and eventually segfault.
By: Lott Caskey (lottc) 2011-05-17 19:23:38
I downloaded the 1.8 SVN branch and could not replicate the error.
By: Dave Miller (justdave) 2011-06-10 20:13:10.513-0500
We've been reproducing this about once a week since we upgraded to 188.8.131.52. (from 184.108.40.206)
Besides the CLI stopping responding, the SIP port stops answering new connections (we have it all nagios monitored, and the monitors start firing saying it's timing out).
Tends to happen frequently in the daytime when our desktop support people add new extensions or make voicemail changes (which they used to be able to do all the time without causing anything to break when we were running 1.4.x).
By: Byron Smith (byronsmith) 2011-07-11 08:39:06.897-0500
I too am able to reproduce on Asterisk 220.127.116.11.1. Very much like DAvid mentioned, I'm unable to perform any further SIP registrations from this point however the CLI still responds. The same applies whereby the daytime staff were able to add extensions and make normal admin changes on 1.4 however 18.104.22.168 things have all gone a little pear shaped. I did first upgrade to 22.214.171.124 however the reload problem was even more reproducible than it is now!
By: Joao Carvalho (foxfire) 2011-07-12 04:17:37.032-0500
Asterisk 126.96.36.199 solved some of the deadlocks, but there is still one in there.
What i fear is this issue might not get resolved because 1.6 and 1.4 are no longer maintained.
The biggest problem is that 1.8 is far from ready for production.
I really regret to have upgraded from 1.4, unfortunately i can not go back.
So which version is the most suited to minimize the problem ?
By the way Byron avoid doing "module reload", use individual reload instead.
By: Dave Miller (justdave) 2011-07-12 19:30:17.179-0500
Does 188.8.131.52 need to be added to the affected versions on this? With 1.6 being unsupported now, maybe it'll get more attention that way?
By: David Vossel (dvossel) 2011-07-20 16:23:04.976-0500
The patch on this review, https://reviewboard.asterisk.org/r/1313/ will likely resolve this issue.
By: leearcher (leearcher) 2011-07-21 04:16:51.326-0500
https://issues.asterisk.org/jira/browse/ASTERISK-18103 relates to a reload bug in 184.108.40.206
By: Joao Carvalho (foxfire) 2011-07-25 03:47:29.231-0500
I have just noticed that patch 1313 just went into 1.8 SVN, any chance of getting a patch for 220.127.116.11 to test it ?
By: Russell Bryant (russell) 2011-07-26 14:30:02.163-0500
fixed in 1.8, which is the only supported version
By: Dave Miller (justdave) 2011-07-26 22:15:36.286-0500
It's hard to tell where the tree is at the moment... which release version of Asterisk 1.8 will this wind up going into?
By: leearcher (leearcher) 2011-07-30 15:36:54.056-0500
1.8 might be the only supported version but if there is to be a 18.104.22.168.1, to fix the reload issue, can this fix not make it in?