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

Chris Nauroth commented on ZOOKEEPER-2115:
------------------------------------------

[~biju74], thank you for patch v2.

Right now, failures will write a message of "insufficient permissions".  
However, it's possible that the commands failed for reasons unrelated to 
permissions, such as a general I/O error.  Could we go back to the more general 
"could not do" error messages that were in the first patch?

There is still a separate {{rm}} call for "version-2", which needs its own 
separate check of the exit code.

[~biju74] or [~mnarayan], are either of you interested in providing another 
revision of the patch?

> Initialize command succeeds even though it didn't in case of permission 
> errors on the data directory
> ----------------------------------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-2115
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2115
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: scripts
>    Affects Versions: 3.5.0
>            Reporter: Manikandan Narayanaswamy
>            Assignee: Flavio Junqueira
>            Priority: Trivial
>             Fix For: 3.6.0
>
>         Attachments: ZOOKEEPER-2115-1.patch, ZOOKEEPER-2115-2.patch, 
> ZOOKEEPER-2115.patch, ZOOKEEPER-2115.patch
>
>
> while testing single user mode that the initialize command succeeds even 
> though it didn't in case of permission errors on the data directory:
> {code}
> ....
> + exec /usr/lib/zookeeper/bin/zkServer-initialize.sh --myid=1
> mkdir: cannot create directory `/var/lib/zookeeper/version-2': Permission 
> denied
> mkdir: cannot create directory `/var/lib/zookeeper/version-2': Permission 
> denied
> /usr/lib/zookeeper/bin/zkServer-initialize.sh: line 112: 
> /var/lib/zookeeper/myid: Permission denied
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to