[asterisk-bugs] [JIRA] (ASTERISK-23651) Reloading some modules that are loaded already, results in 'No such module' before a successful reload

Matt Jordan (JIRA) noreply at issues.asterisk.org
Mon Dec 8 11:28:48 CST 2014


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

Matt Jordan updated ASTERISK-23651:
-----------------------------------

    Target Release Version/s: 13.1.0

> Reloading some modules that are loaded already, results in 'No such module' before a successful reload
> ------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-23651
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-23651
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/Configuration, Core/General
>    Affects Versions: SVN, 12.1.1
>            Reporter: Rusty Newton
>            Severity: Minor
>      Target Release: 12.8.0, 13.1.0
>
>
> Below are a few random samples, with the first two showing the issue and the last two are fine.
> {noformat}
> newtonr-laptop*CLI> module reload chan_motif.so
> No such module 'chan_motif.so'
>     -- Reloading module 'chan_motif.so' (Motif Jingle Channel Driver)
> [Apr 22 11:43:05] DEBUG[4775]: config_options.c:649 aco_process_config: motif.conf was unchanged
> newtonr-laptop*CLI> module reload chan_pjsip.so 
> No such module 'chan_pjsip.so'
>     -- Reloading module 'chan_pjsip.so' (PJSIP Channel Driver)
> newtonr-laptop*CLI> module reload app_voicemail.so 
> Module 'app_voicemail.so' reloaded successfully.
>     -- Reloading module 'app_voicemail.so' (Comedian Mail (Voicemail System))
> newtonr-laptop*CLI> module reload chan_iax2.so 
> Module 'chan_iax2.so' reloaded successfully.
>     -- Reloading module 'chan_iax2.so' (Inter Asterisk eXchange (Ver 2))
> {noformat}
> Marking this as a regression, as I don't see this behavior in previous versions.
> The issue doesn't appear to affect the actual reload of module configuration.



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



More information about the asterisk-bugs mailing list