[asterisk-bugs] [JIRA] (ASTERISK-25416) Lockup when trying to restart - 'core restart when convenient'

Mark Michelson (JIRA) noreply at issues.asterisk.org
Thu Oct 1 15:33:33 CDT 2015


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

Mark Michelson commented on ASTERISK-25416:
-------------------------------------------

The problem appears to be that pbx_dundi destroys its scheduler context but then tries to access it again later when pruning peers. In some cases, this will go fine since the recently destroyed object will still be usable. However, it is possible for the memory where the destroyed object resides to have been overwritten with something new, thereby trying to operate the lock useless. It's in these cases that the shutdown blocks forever. The proper solution here is to destroy the scheduler context after pruning peers in pbx_dundi's unload_module() function.

> Lockup when trying to restart - 'core restart when convenient'
> --------------------------------------------------------------
>
>                 Key: ASTERISK-25416
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25416
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 11.19.0
>            Reporter: Birger "WIMPy" Harzenetter
>            Assignee: Mark Michelson
>            Severity: Minor
>         Attachments: Asterisk-debug.txt
>
>
> Asterisk locks up when performing a "core restart when convenient"
> [edit by Rusty - below]
> For reference, [Asterisk-debug.txt|https://issues.asterisk.org/jira/secure/attachment/53023/Asterisk-debug.txt] contains:
>  * Backtrace
>  * 'core show locks' output
>  * 'core show threads' output
>  * 'core show taskprocessors' output



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



More information about the asterisk-bugs mailing list