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

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-30097:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/].

> 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: Improvement
>      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
>            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)