[asterisk-bugs] [JIRA] (ASTERISK-27270) cdr_mysql: various crashes at second module reload if cdr_mysql.conf is configured

[Friendly Automation (JIRA)]

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

Friendly Automation commented on ASTERISK-27270:
------------------------------------------------

Change 6721 merged by Jenkins2:
cdr_mysql: avoid releasing a config string

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

> cdr_mysql: various crashes at second module reload if cdr_mysql.conf is configured
> ----------------------------------------------------------------------------------
>
>                 Key: ASTERISK-27270
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27270
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Addons/cdr_mysql
>    Affects Versions: 13.17.1
>         Environment: Centos 7
>            Reporter: Tzafrir Cohen
>         Attachments: ASTERISK-27270_cdr_mysql.c_revert.patch
>
>
> Once we upgraded to 13.17.1, we noticed that 'module reload' occasionally causes crashes. Upon further research it seems that a second or third 'module reload' induces a crash.
> Note: I did not attach core dumps. Crashes seem to come from random places roughly at the time of configuration reload.
> The following work around the issue:
> * Downgrading to 13.13.1 fixed the issue.
> * avoiding loading cdr_mysql.so
> * Empty cdr_mysql.conf or one that only has the line '[global]'
> * Build dcr_mysql.c with the patch from f882ca25722b6290dc6e8d786452b0b26adceed1 reverted.
> The following cdr_mysql.conf is good enough to induce a crash:
> {code}
> [global]
> hostname=127.0.0.1
> {code}



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