You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@zookeeper.apache.org by "Mate Szalay-Beko (Jira)" <ji...@apache.org> on 2022/05/17 08:32:00 UTC

[jira] [Updated] (ZOOKEEPER-3887) In SSL-only server zkServer.sh status command should use secureClientPortAddress instead of clientPortAddress

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-3887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mate Szalay-Beko updated ZOOKEEPER-3887:
----------------------------------------
    Fix Version/s: 3.5.10

> In SSL-only server zkServer.sh status command should use secureClientPortAddress instead of clientPortAddress
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-3887
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3887
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: scripts
>    Affects Versions: 3.6.2
>            Reporter: Mohammad Arshad
>            Assignee: Mohammad Arshad
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.5.10, 3.6.3, 3.8.0, 3.7.1
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> When only SSL client port is enabled, zkServer.sh status command should use secureClientPortAddress value instead of clientPortAddress. 
> As clientPortAddress is not configured, zkServer.sh status command tries to connect to localhost and fails.
> ZOOKEEPER-3818 has addressed the port issue, same way we should address the host issue.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)