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

Rusty Newton (JIRA) noreply at issues.asterisk.org
Fri Jul 18 09:15:56 CDT 2014


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

Rusty Newton edited comment on ASTERISK-24041 at 7/18/14 9:14 AM:
------------------------------------------------------------------

Please post cdr_pgsql and backend configuration on here as well to increase the odds to help others troubleshoot or identify if their issue is the same.

Note that cdr_pgsql is extended support, meaning it is supported by the community and not the core developers. Response time to the issue may reflect that.

In the meantime, if you need to push CDR to PostgresQL you might try cdr_adaptive_odbc and use ODBC to get there, which is core supported.


was (Author: rnewton):
Please post cdr_pgsql and backend configuration on here as well to increase the odds to help others troubleshoot or identify if their issue is the same.

Note that cdr_pgsql is extended support, meaning it is supported by the community and not the core developers. Response time to the issue may reflect that.

In the meantime, if you need to push CDR to PostgresQL you might try cdr_adaptive_odbc and use ODBC.

> 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
>         Attachments: backtrace-threads.txt, 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