[
https://issues.apache.org/jira/browse/ZOOKEEPER-2895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16164309#comment-16164309
]
neha commented on ZOOKEEPER-2895:
---------------------------------
I have tried the same thing and it works fine for me until I have
{code}clientPort=2181{code} configured in my zoo.cfg. But when it is not
configured in the zoo.cfg, and default value is taken (maybe from code) then it
occurs.
The fix can go like if it is configured in zoo.cfg, take this value and extract
clientPort value from it else consider default value.
Makes sense??
> a bug in zkServer.sh
> ---------------------
>
> Key: ZOOKEEPER-2895
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2895
> Project: ZooKeeper
> Issue Type: Bug
> Components: other
> Affects Versions: 3.4.10
> Environment: centos 6.5
> jdk1.8.0_131
> Reporter: huangyun
>
> I deploy ZooKeeper in a cluster of three nodes on three different linux
> machines.
> All is going well,but I got the output of " Error contacting service. It is
> probably not running " when I executed "zkServer.sh status" to check if the
> node of cluster was running.
> Finally, I found a problem in zkServer.sh
> it got "clientPort=2181" when executing "zkServer.sh status" ,but the correct
> String is only "2181".So, It is a solution to the problem that removing
> "clientPort=" from "clientPort=2181" .
> I hope you understand me. My poor English.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
