[asterisk-bugs] [JIRA] (ASTERISK-24041) deadlock when cdr_pgsql fails to post CDR due to PGSQL connection failure

Asterisk Team (JIRA) noreply at issues.asterisk.org
Tue Jan 2 08:29:45 CST 2018


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

Asterisk Team updated ASTERISK-24041:
-------------------------------------

    Assignee: Joshua Colp  (was: Gergely Dömsödi)
      Status: Open  (was: Waiting for Feedback)

> deadlock when cdr_pgsql fails to post CDR due to PGSQL connection failure
> -------------------------------------------------------------------------
>
>                 Key: ASTERISK-24041
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24041
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: CDR/cdr_pgsql
>    Affects Versions: 1.8.28.0
>            Reporter: Gergely Dömsödi
>            Assignee: Joshua Colp
>         Attachments: backtrace-threads.txt, cdr.conf, cdr_pgsql.conf, core-channels.txt, core-locks.txt, core-threads.txt, main-cut.log
>
>
> On our production system SIP channels got stuck in asterisk. This happened 1-2 times daily on a system which is barely used. After a lot of trial-and-no-result, I managed to seemingly solve it by turning off the posting of CDRs to PGSQL, hence the assumption that it is somehow related to cdr_pgsql. 
> In the logs, we could see a SIP hangup coming in from one leg of the channel, the UserEvent fireing which we have in the "h" extension, but the asterisk didn't send the BYE event to the other participant.
> Unfortunately I couldn't reproduce the issue on a non-production system, but I managed to get a lot of debug log from the production server.



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



More information about the asterisk-bugs mailing list