[asterisk-bugs] [JIRA] (ASTERISK-21108) If chan_motif fails to load, Asterisk still thinks it's loaded

[Michael L. Young (JIRA)]

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

Michael L. Young edited comment on ASTERISK-21108 at 2/14/13 8:26 PM:
----------------------------------------------------------------------

Rusty, I think that is actually correct.  The message is a bit mis-leading.  The module is loaded, it is just not in a running state.

This prompted to think that we should be displaying the status of the module.  So, I just wrote a patch to do this.  When testing the patch, I actually found something not running that I thought was running. :)

Let me know what you think of the patch.
                
      was (Author: elguero):
    Rusty, I think that is actually correct.  The message is a bit mis-leading.  The module is loaded, it is just not in a running state.

This prompted to think that we should be displaying the status of the module.  So, I just wrote a patch to do this.  When testing the patch, I actually found something not running that I thought was running. :)
                  
> If chan_motif fails to load, Asterisk still thinks it's loaded
> --------------------------------------------------------------
>
>                 Key: ASTERISK-21108
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21108
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_motif
>    Affects Versions: SVN
>         Environment: x86_64 ,  SVN-branch-11-r381467
>            Reporter: Rusty Newton
>         Attachments: asterisk-21108_add_status.diff
>
>
> During Asterisk's load we see that chan_motif.so is not loaded... (due to leaving sample stuff in the config)
> {noformat}
> [Feb 14 18:26:30] DEBUG[17905] config.c: Parsing /etc/asterisk/motif.conf
> [Feb 14 18:26:30] VERBOSE[17905] config.c:   == Parsing '/etc/asterisk/motif.conf': Found
> [Feb 14 18:26:30] DEBUG[17905] config.c: extract int from [30] in [-2147483648, 2147483647] gives [30](0)
> [Feb 14 18:26:30] DEBUG[17905] config.c: extract int from [30] in [-2147483648, 2147483647] gives [30](0)
> [Feb 14 18:26:30] DEBUG[17905] config.c: extract int from [10] in [-2147483648, 2147483647] gives [10](0)
> [Feb 14 18:26:30] DEBUG[17905] config.c: extract int from [10] in [-2147483648, 2147483647] gives [10](0)
> [Feb 14 18:26:30] ERROR[17905] chan_motif.c: Connection 'local-jabber-account' configured on endpoint 'jingle-endpoint' could not be found
> [Feb 14 18:26:30] ERROR[17905] config_options.c: Error parsing connection=local-jabber-account at line 81 of 
> [Feb 14 18:26:30] ERROR[17905] config_options.c: In motif.conf: Processing options for jingle-endpoint failed
> [Feb 14 18:26:30] ERROR[17905] chan_motif.c: Unable to read config file motif.conf. Not loading module.
> {noformat}
> However after Asterisk is up and running:
> {noformat}
> ubuntu*CLI> module show like chan_motif.so 
> Module                         Description                              Use Count 
> chan_motif.so                  Motif Jingle Channel Driver              0         
> 1 modules loaded
> {noformat}
> I'm not sure what issues it could cause when Asterisk thinks a module is loaded that isn't loaded, however it at least caused me pain trying to figure out why chan_motif (which I thought was loaded) was ignoring inbound XMPP traffic. :D

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira