[asterisk-bugs] [JIRA] (ASTERISK-27909) cdr: Deadlock with submit_scheduled_batch and submit_unscheduled_batch

[Friendly Automation (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-27909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Friendly Automation closed ASTERISK-27909.
------------------------------------------

    Resolution: Fixed

> cdr: Deadlock with submit_scheduled_batch and submit_unscheduled_batch
> ----------------------------------------------------------------------
>
>                 Key: ASTERISK-27909
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27909
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: CDR/General
>    Affects Versions: 15.4.0
>         Environment: CentOS Linux 7 (Core)
> Linux *** 3.10.0-862.2.3.el7.x86_64 #1 SMP Wed May 9 18:05:47 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
> Asterisk versions: 15.4.0
>            Reporter: Denis Lebedev
>            Assignee: Matthew Fredrickson
>            Severity: Minor
>         Attachments: gdb.txt
>
>
> We faced with deadlock in cdr.c in functions:
> {noformat}
> static int submit_scheduled_batch(const void *data)
> static void submit_unscheduled_batch(void)
> {noformat}
> Previously there was another deadlock which was fixed in ASTERISK-21162. That task added pretty the same mutex {{cdr_sched_lock}} on which asterisk is stucked in deadlock in consequent versions.
> The problem is quite rare so it's almost impossible to reproduce it under some artificial circumstances.
> Symptoms:
> * asterisk stops to flush cdr items into DB
> * pings to cdr are performed in 5s (afaiu, they are timed out)
> {noformat}
> *CLI> core ping taskprocessor subm:cdr_engine-00000003
> pinging subm:cdr_engine-00000003 ...
> 	subm:cdr_engine-00000003 ping time: 5.000129 sec
> {noformat}
> * asterisk begins to "eat" memory on the host under load
> * but proceeds serving incoming calls traffic
> Also asterisk can't be restarted from cli.



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