[
https://issues.apache.org/jira/browse/ZOOKEEPER-1744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13791781#comment-13791781
]
Alexander Shraer commented on ZOOKEEPER-1744:
---------------------------------------------
right - I also don't think these are duplicate. My changes are extending the
way clientPort is being identified, whereas here the patch
is identifying the hostname to be used with this port.
> clientPortAddress breaks "zkServer.sh status"
> ----------------------------------------------
>
> Key: ZOOKEEPER-1744
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1744
> Project: ZooKeeper
> Issue Type: Bug
> Components: scripts
> Affects Versions: 3.4.5
> Reporter: Nick Ohanian
> Assignee: Nick Ohanian
> Priority: Critical
> Fix For: 3.4.6, 3.5.0
>
> Attachments: ZOOKEEPER-1744.patch
>
>
> When "clientPortAddress" is used in the config file (zoo.cfg), zkServer.sh's
> status command runs a grep command that matches both "clientPort" and
> "clientPortAddress". This creates an extra argument for FourLetterWordMain,
> which fails, so the status command incorrectly indicates that it couldn't
> connect to the server.
> Also, "localhost" is hardcoded as the target host for FourLetterWordMain.
> The "clientPortAddress" should be used if it is provided in the config file.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
