[asterisk-bugs] [JIRA] (ASTERISK-26686) Deadlock db_sync_thread

Asterisk Team (JIRA) noreply at issues.asterisk.org
Tue Jan 3 01:46:10 CST 2017


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

Asterisk Team commented on ASTERISK-26686:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

> Deadlock db_sync_thread
> -----------------------
>
>                 Key: ASTERISK-26686
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-26686
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/AstDB
>    Affects Versions: 13.13.1
>         Environment: Fedora Server 23 SQLLite 3.11.0
>            Reporter: Ross Beer
>         Attachments: backtrace_20160103.txt
>
>
> Asterisk locks with no further processing. This looks to be related to the ASTDB holding a lock.



--
This message was sent by Atlassian JIRA
(v6.2#6252)



More information about the asterisk-bugs mailing list