[asterisk-bugs] [JIRA] (ASTERISK-21228) Deadlock in pbx_find_extension when attempting an autoservice stop due to holding the context lock

[Dare Awktane (JIRA)]

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

Dare Awktane edited comment on ASTERISK-21228 at 4/26/13 8:28 AM:
------------------------------------------------------------------

I'm unable to run asterisk with debug flags enabled during the week but it looks like your patch caused a different issue. Apparent deadlock with the following output on the console:

[Apr 26 07:23:48] WARNING[16179]: chan_sip.c:4210 __sip_autodestruct: Autodestruct on dialog '72764eac4838da9f5548311344a28c46 at edm.trk.tprm.ca' with owner SIP/thinktel-000001fd in place (Method: BYE). Rescheduling destruction for 10000 ms
  == Using SIP RTP CoS mark 5
[Apr 26 07:23:52] WARNING[16179]: chan_sip.c:4210 __sip_autodestruct: Autodestruct on dialog '637C27D4 at 159.18.161.101' with owner SIP/thinktel-00000203 in place (Method: BYE). Rescheduling destruction for 10000 ms
[Apr 26 07:23:55] WARNING[16179]: chan_sip.c:4210 __sip_autodestruct: Autodestruct on dialog '485c420a3c3256fc6fdb80c92f561cb7 at edm.trk.tprm.ca' with owner SIP/thinktel-000001ff in place (Method: BYE). Rescheduling destruction for 10000 ms
[Apr 26 07:24:01] WARNING[16179]: chan_sip.c:4210 __sip_autodestruct: Autodestruct on dialog 'E4601269 at 159.18.161.101' with owner SIP/thinktel-00000205 in place (Method: BYE). Rescheduling destruction for 10000 ms
[Apr 26 07:24:01] WARNING[16179]: chan_sip.c:4210 __sip_autodestruct: Autodestruct on dialog 'B7F78109 at 159.18.161.101' with owner SIP/thinktel-00000202 in place (Method: BYE). Rescheduling destruction for 10000 ms
  == Using SIP RTP CoS mark 5
[Apr 26 07:24:04] WARNING[16179]: chan_sip.c:4210 __sip_autodestruct: Autodestruct on dialog '44d59aa72a5a26ec5e2358ca7ae9f858 at edm.trk.tprm.ca' with owner SIP/thinktel-000001fe in place (Method: BYE). Rescheduling destruction for 10000 ms
[Apr 26 07:24:08] WARNING[16179]: chan_sip.c:4210 __sip_autodestruct: Autodestruct on dialog '58679d5c02285c22209df7b1360e9309 at edm.trk.tprm.ca' with owner SIP/thinktel-000001fc in place (Method: BYE). Rescheduling destruction for 10000 ms

I can get you the thread details over the weekend if you would like it.
                
      was (Author: awktane):
    I will try the patch on one of our machines before I make the changes to the dial plan. I'll let you know the results.
                  
> Deadlock in pbx_find_extension when attempting an autoservice stop due to holding the context lock
> --------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-21228
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21228
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/PBX
>    Affects Versions: 1.8.20.1, 1.8.21.0, 11.2.1, 11.3.0
>         Environment: Linux 3.2.0-38-generic #61-Ubuntu SMP x86_64 x86_64 x86_64 GNU/Linux
>            Reporter: Dare Awktane
>         Attachments: 1366481920-backtrace_threads.txt, 1366481920-core_show_locks.txt, 1366495718-backtrace_threads.txt, 1366495718-core_show_locks.txt, 20130425__AST-21228.patch, backtrace-threads.txt, core-show-locks.txt
>
>
> Due to the way locks are maintained it appears as though our realtime switch calls in our extensions.conf, which are also stored in the database via odbc, are causing a conflict. We have 5500 contexts any of which can be called at any time as each one exists to maintain separation between our customers.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira