Bug#1025012: zookeeper: starts but is completely unusable
Christoph Anton Mitterer
calestyo at scientia.org
Sun Jan 12 06:04:33 GMT 2025
Control: tags -1 moreinfo unreproducible
Hey.
Removing these tags since I think, I give the requested information now
and Filippo confirmed the issue. :-)
Actually I think the severity should be grave, as it makes the package
useless ;-)
But that would likely kick it from trixie (unless resolved in time),
which I would want either, since it’s rather simple to fix by appending
the CLASSPATH as described above.
@Pierre, I’ve just seen you’ve requested my
/etc/zookeeper/conf/environment ... that slipped through, sorry.
I’ve attached it (which is my version with the modifications) to this
mail.
The diff from the example version shipped with the package in bookworm
is:
--- environment 2024-06-16 12:34:19.000000000 +0200
+++ /etc/zookeeper/conf/environment 2025-01-12 06:33:54.855932755 +0100
@@ -10,4 +10,4 @@
# line tools such as `zkCli.sh` and not for the actual server
JAVA=/usr/bin/java
-CLASSPATH="/etc/zookeeper/conf:/usr/share/java/zookeeper.jar"
+CLASSPATH="/etc/zookeeper/conf:/usr/share/java/zookeeper.jar:/usr/share/java/slf4j-log4j12.jar:/usr/share/java/log4j-1.2.jar"
There should be no update issues involved, as I did a fresh install of
ZK in bookworm
> I humbly admit I cannot answer as I am not a zookeeper user... but if
> you tell me where to look I might tell.
If clustered, you’d need more ZKs running on different hosts, and you’d
have a configuration in zoo.conf like:
server.1=zk1.example.org:2182:2183;2181
server.2=zk2.example.org:2182:2183;2181
server.3=zk3.example.org:2182:2183;2181
and each of them would have the same config, except for the myid file
which would contain the number of the respective server (1, 2, 3) only.
> As you suggest (see my request above), we don't have the same
> classpath
> and this might be because you already had zookeeper installed from
> old
> bullseye package and then upgraded.
Nope, fresh setup. :-)
It was really already missing from the example environment file shipped
in the package.
> I think /etc/zookeeper/conf contents
> is set up by update-alternatives and maybe something is not working
> well
> in our post-install treatments in the case of an upgrade from an
> already-installed zookeeper.
btw: Not sure whether update-alternatives should be used there.
So again, sorry that I’ve somehow overseen your mail. Really not sure
why.
Thanks,
Chris.
-------------- next part --------------
ZOOMAIN=org.apache.zookeeper.server.quorum.QuorumPeerMain
ZOOCFGDIR=/etc/zookeeper/conf
ZOOCFG=/etc/zookeeper/conf/zoo.cfg
ZOO_LOG_DIR=/var/log/zookeeper
ZOO_LOG4J_PROP=INFO,ROLLINGFILE
JMXLOCALONLY=true
JAVA_OPTS=""
# If ZooKeeper is started through systemd, this will only be used for command
# line tools such as `zkCli.sh` and not for the actual server
JAVA=/usr/bin/java
CLASSPATH="/etc/zookeeper/conf:/usr/share/java/zookeeper.jar:/usr/share/java/slf4j-log4j12.jar:/usr/share/java/log4j-1.2.jar"
More information about the pkg-java-maintainers
mailing list