[
https://issues.apache.org/jira/browse/ZOOKEEPER-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768937#action_12768937
]
Ted Dunning commented on ZOOKEEPER-556:
---------------------------------------
In the following exchange, a new Zookeeper user lost several days wrestling
with this issue. Henry spotted the problem. I didn't. Patrick didn't.
With a prominent error message, the user would have found this in 5 minutes.
{noformat}
yeah - thought this was it: you've missed the forward slash on
home/mark/zookeeper (this turned up on your exception message).
On Thu, Oct 22, 2009 at 2:55 PM, Mark Vigeant
<[email protected]>wrote:
> Yeah I just figured out the problem with zoocfg.py
>
> I am running as the same user who created myid. Here's my config:
>
> zoo.cfg
>
> tickTime-2000
> dataDir=home/mark/zookeeper
> clientPort=2181
> initLimit=5
> syncLimit=2
> server.1= hermes:2888:3888
> server.2= leela:2888:3888
>
> on the machines hermes and leela I've put myid files in
> /home/mark/zookeeper
> with the numbers 1 and 2 respectively
{noformat}
> Startup messages should account for common error of missing leading slash in
> config files
> -----------------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-556
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-556
> Project: Zookeeper
> Issue Type: Bug
> Reporter: Ted Dunning
>
> It would be nice if the startup noticed directories without a leading slash
> in the config file. That is worth a warning.
> Moreover, if that directory exists looking from root, but not looking from
> the current directory, a very serious warning is in order.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
