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

[Asterisk Team (JIRA)]

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

Asterisk Team closed ASTERISK-24041.
------------------------------------

    Resolution: Suspended

Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1].
[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines

> 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)