[asterisk-bugs] [JIRA] (ASTERISK-22871) cel_pgsql module not loading after "reload" or "reload cel_pgsql.so" command

[Matt Jordan (JIRA)]

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

Matt Jordan updated ASTERISK-22871:
-----------------------------------

    Target Release Version/s: 12.1.0
    
> cel_pgsql module not loading after "reload" or "reload cel_pgsql.so" command
> ----------------------------------------------------------------------------
>
>                 Key: ASTERISK-22871
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22871
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: CEL/cel_pgsql
>    Affects Versions: 11.2.0, 11.5.0
>         Environment: Debian 6.0.7 virtualized on Proxmox 3.1 (KVM) 
> Memory 1Gb
> CPU 2.27 GHz (1 socket)
>            Reporter: Matteo
>            Assignee: Kevin Harwell
>      Target Release: 1.8.26.0, 11.8.0, 12.1.0
>
>
> Running the command "reload cel_pgsql.so" (or simply "reload") from the asterisk CLI the cel_pgsql.so module is not reloaded, it is just unloaded.
> Looking quickly through the code of the cel/cel_pgsql.c module I have seen that the execution of the "reload" command ends up in the else if (cfg == CONFIG_STATUS_FILEUNCHANGED) condition reported below.
> You can find pasted below the snippet of the code I mentioned before, it could be helpful.
> {code}
>         if ((cfg = ast_config_load(config, config_flags)) == NULL || cfg == CONFIG_STATUS_FILEINVALID) {
>                 ast_log(LOG_WARNING, "Unable to load config for PostgreSQL CEL's: %s\n", config);
>                 return AST_MODULE_LOAD_DECLINE;
>         } else if (cfg == CONFIG_STATUS_FILEUNCHANGED) {
> /*                ast_log(LOG_WARNING, "I go here !!!!!!!!!!\n");*/
>                 return AST_MODULE_LOAD_SUCCESS;
>         }
> {code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira