[asterisk-bugs] [JIRA] (ASTERISK-30097) console: Recent documentation changes for connecting to remote console are inconsistent

[Kevin Harwell (JIRA)]

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

Kevin Harwell commented on ASTERISK-30097:
------------------------------------------

[~InterLinked] Many thanks!

> console: Recent documentation changes for connecting to remote console are inconsistent
> ---------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-30097
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-30097
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/Logging
>    Affects Versions: 18.12.1
>         Environment: Asterisk compiled with a specific installpath and using a configuration from a different path.
>            Reporter: Matthias Hensler
>            Assignee: N A
>            Severity: Trivial
>
> The recent changes from ASTERISK-22246, that introduced warnings for parameters without effect when connecting to a remote console, are actually inconsistent.
> Specifically it lists the "-C" option for specifying a configuration file as having no effect, while it actually has.
> Consider the setup which we use here:
> * an asterisk version is compiled to its own installpath to make it easy for switching between versions. In this case "/usr/local/packages/asterisk-18.12.1" and a symlink "/usr/local/packages/asterisk" pointing to that specific version.
> * all the configuration is still at /etc/asterisk/ and asterisk is started with "-C /etc/asterisk/asterisk.conf"
> * a cronjob is run to rotate the logfile: "/usr/local/packages/asterisk/sbin/asterisk -C /etc/asterisk/asterisk.conf -rx 'logger rotate'"
> While above setup still works, it now issues the warning "'C' option is not compatible with remote console mode and has no effect.". But actually the "C"-option is still absolutely necessary to find the correct path to the remote-socket. Not using the "C"-option doesn't work:
> {quote}
>   Unable to open specified master config file '/usr/local/packages/asterisk-18.12.1/etc/asterisk/asterisk.conf', using built-in defaults
>    Unable to connect to remote asterisk (does /usr/local/packages/asterisk-18.12.1/var/run/asterisk/asterisk.ctl exist?)
> {quote}
> It is still possible to make the command work by running " /usr/local/packages/asterisk/sbin/asterisk -s /var/run/asterisk/asterisk.ctl -rx 'logger rotate'". However that still issues the first warning that the master-configfile isn't found.
> In conclusion I think that the "C"-option shouldn't marked as having no effect.



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