zookeeper-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bobi Traykov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-3444) Latest stable version will not start on Windows Server 2016 (DataCenter edition) and Java 8
Date Wed, 26 Jun 2019 10:41:00 GMT

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

Bobi Traykov commented on ZOOKEEPER-3444:

Hi [~eolivelli], 
Thank you for your comment!
The correlation was that my laptop is running on Windows 10 and (I think) it's closer in terms
of OS-specifics to Windows Server 2016 than Windows Server 2012. So it's more of statement
for the sake of details - not really that correlatable, I agree.

I can confirm that in all attempts te line endings of the zoo.cfg were transformed from LF
to CR LF.

Symbolic links - I have not used any explicitly - in all attempts I navigated the CMD session
to the \bin folder and from there executed the *zkServer.cmd*.

Please let me know if there are any other details that I can supply on this issue.

> Latest stable version will not start on Windows Server 2016 (DataCenter edition) and
Java 8
> -------------------------------------------------------------------------------------------
>                 Key: ZOOKEEPER-3444
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3444
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: java client
>    Affects Versions: 3.5.5
>         Environment: Windows Server 2016 DataCenter edition
> Firewall and User Access Control - both full disabled.
> +Java used+:
> java version "1.8.0_212"
> Java(TM) SE Runtime Environment (build 1.8.0_212-b10)
> Java HotSpot(TM) 64-Bit Server VM (build 25.212-b10, mixed mode)
> +Java package (from the Oracle site)+: jre-8u212-windows-x64.exe
> Used the bin package of the ZooKeeper release.
>            Reporter: Bobi Traykov
>            Priority: Major
> When attepmting to start ZooKeeper using the *ZKServer.cmd* batch file, I receive the
following error:
> {noformat}
> D:\apache-zookeeper-3.5.5-bin\bin>call "D:\jre1.8.0_212"\bin\java "-Dzookeeper.log.dir=D:\apache-zookeeper-3.5.5-bin\bin\..\logs"
"-Dzookeeper.root.logger=ALL1,CONSOLE" "-Dzookeeper.log.file=zookeeper-ironman-server-TF-AMIR-BASTION.log"
"-XX:+HeapDumpOnOutOfMemoryError" "-XX:OnOutOfMemoryError=cmd /c taskkill /pid %%p /t /f"
-cp "D:\apache-zookeeper-3.5.5-bin\bin\..\build\classes;D:\apache-zookeeper-3.5.5-bin\bin\..\build\lib\*;D:\apache-zookeeper-3.5.5-bin\bin\..\*;D:\apache-zookeeper-3.5.5-bin\bin\..\lib\*;D:\apache-zookeeper-3.5.5-bin\bin\..\conf"
org.apache.zookeeper.server.quorum.QuorumPeerMain "D:\apache-zookeeper-3.5.5-bin\bin\..\conf\zoo.cfg"
> 2019-06-25 08:40:41,391 [myid:] - INFO [main:QuorumPeerConfig@133] - Reading configuration
from: D:\apache-zookeeper-3.5.5-bin\bin\..\conf\zoo.cfg
> 2019-06-25 08:40:41,391 [myid:] - ERROR [main:QuorumPeerMain@89] - Invalid config, exiting
> org.apache.zookeeper.server.quorum.QuorumPeerConfig$ConfigException: Error processing
> at org.apache.zookeeper.server.quorum.QuorumPeerConfig.parse(QuorumPeerConfig.java:154)
> at org.apache.zookeeper.server.quorum.QuorumPeerMain.initializeAndRun(QuorumPeerMain.java:113)
> at org.apache.zookeeper.server.quorum.QuorumPeerMain.main(QuorumPeerMain.java:82)
> Caused by: java.lang.IllegalArgumentException: dataDir is not set
> at org.apache.zookeeper.server.quorum.QuorumPeerConfig.parseProperties(QuorumPeerConfig.java:368)
> at org.apache.zookeeper.server.quorum.QuorumPeerConfig.parse(QuorumPeerConfig.java:150)
> ... 2 more
> Invalid config, exiting abnormally{noformat}
> The *zoo.cfg* is a copy-paste from the *zoo_sample.cfg* - the *dataDir* parameter is
pointing to E:/zookeeper - an existing empty directory.
> The previous two stable releases start without any issues:
> zookeeper-3.4.10.tar.gz
> zookeeper-3.4.14.tar.gz
> Last, but not least, the 3.5.5 release works fine for me on Windows 10 (fully updated),
Windows Server 2008 R2 and Windows Server 2012 R2.

This message was sent by Atlassian JIRA

View raw message