[asterisk-bugs] [JIRA] (ASTERISK-27572) cdr_mysql creates empty records if reconnects when mysql was not up on module load

Friendly Automation (JIRA) noreply at issues.asterisk.org
Wed Jun 6 08:14:54 CDT 2018


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

Friendly Automation commented on ASTERISK-27572:
------------------------------------------------

Change 8919 merged by George Joseph:
cdr_mysql: split mysql init out of my_load_module

[https://gerrit.asterisk.org/8919|https://gerrit.asterisk.org/8919]

> cdr_mysql creates empty records if reconnects when mysql was not up on module load
> ----------------------------------------------------------------------------------
>
>                 Key: ASTERISK-27572
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27572
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Addons/cdr_mysql
>    Affects Versions: 13.18.5, 15.1.5
>            Reporter: Tzafrir Cohen
>            Severity: Minor
>
> Setup: configure the system to use mysql as a CDR backend.
> 1. asterisk -rx 'module unload cdr_mysql.so'
> 1. Stop mysqld (or mariadb, or whatever)
> 1. asterisk -rx 'module load cdr_mysql.so'
> 1. Start mysqld
> 1. Make a call that generates a CDR.
> 1. The MySQL CDR backend will try to reconnect each time it has a record to generate and there's no existing connection.
> Expected: A normal record for the call.
> Actual: The record for the call has no field set.
> The reason for that is that when reconnecting (on mysql_log()), the content of the columns list is not created.
> Tested on branch 13 (commit 8e0f2c7379c1a39b5416878e36515b6ff97aaa9d). Code looks the same on master.



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



More information about the asterisk-bugs mailing list