[asterisk-bugs] [JIRA] (ASTERISK-17255) Possible deadlock on 1.6.2.12, 14 and 15

[Matt Jordan (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-17255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=201472#comment-201472 ] 

Matt Jordan commented on ASTERISK-17255:
----------------------------------------

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.  After testing with Asterisk 1.8, if you find this problem has not been resolved, please open a new issue against Asterisk 1.8.

In addition, it looks like this problem was resolved by ASTERISK-18166. If you find you still have problems with a deadlock in Asterisk 1.8, please contact a bug marshal in #asterisk-bugs.
                
> Possible deadlock on 1.6.2.12, 14 and 15
> ----------------------------------------
>
>                 Key: ASTERISK-17255
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-17255
>             Project: Asterisk
>          Issue Type: Bug
>          Components: Core/General
>            Reporter: Dieter Jansen
>            Severity: Critical
>         Attachments: case.201101121019.bt.log, case.201101121019.caseinfo, case.201101121019.gcore.log, case.201101121455.bt.log, case.201101121455.caseinfo, case.201101121455.gcore.log, case.201101131248.bt.log, case.201101131248.caseinfo, case.201101131248.gcore.log, case.201101221250.backtrace-threads.txt, case.201101221250.caseinfo, case.201101221250.core-show-locks.txt
>
>
> After hours to days the system appears to reach a deadlocked state.  SIP phones lose registration, in-flight calls continue, no new calls can be established.  Need a "service asterisk restart" to get going again.
> Problem is usually first observed when phones lose registration (120 seconds between registrations).
> System has never been observed to reach this state overnight or on a weekend so it appears to only happen when the system is actively handling calls.
> ****** ADDITIONAL INFORMATION ******
> I have experienced this (or similar) with 1.6.2.12, 1.6.2.14 and now 1.6.2.15 though I only have backtraces for 1.6.2.15 .
> Reported against 1.6.2.14 because that is the latest on the pulldown.
> System started as:
>   AsteriskNOW 1.7.1 distribution
>   Asterisk 1.6.2.12
>   B410P BRI interface card connected to Australian Telco
>   DAHDI Version: 2.4.0 Echo Canceller: MG2
>   libpri version: 1.4.11.4
> Updated to:
>   Asterisk 1.6.2.14
>   libpri version: 1.4.11.5
> And then to:
>   Asterisk 1.6.2.15
> Originally posted details to http://forums.digium.com/viewtopic.php?f=1&t=76457
> Gathered backtraces of three occurrences as suggested by malcolmd and will attach files.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira