You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Camille Fournier (JIRA)" <ji...@apache.org> on 2013/10/10 19:51:42 UTC

[jira] [Commented] (ZOOKEEPER-1744) clientPortAddress breaks "zkServer.sh status"

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-1744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13791728#comment-13791728 ] 

Camille Fournier commented on ZOOKEEPER-1744:
---------------------------------------------

Isn't this a dupe of another patch ZOOKEEPER-1785? [~shralex]

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