Bug#1025012: zookeeper: starts but is completely unusable

[Pierre Gruet]

Control: tags -1 moreinfo unreproducible

Hello Chris,


> Package: zookeeper
> Version: 3.8.0-10
> Severity: grave
> Justification: renders package unusable
>
>
> Hey.
>

> nor /var/log/zookeeper .. not even any files get created in there).
>
> Connecting via zkCli gives:
> # /usr/share/zookeeper/bin/zkCli.sh
> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
> SLF4J: Defaulting to no-operation (NOP) logger implementation

On Mon, 28 Nov 2022 20:49:22 +0100 Christoph Anton Mitterer <cales...@scientia.org> wrote: > I've tried the new packagin, but while all my config and data files are in place, > and while the server "runs", there is no logging (neither to stdout/err for systemd > SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.

> Connecting to localhost:2181
> Welcome to ZooKeeper!
> JLine support is disabled
> SLF4J: Failed to load class "org.slf4j.impl.StaticMDCBinder".
> SLF4J: Defaulting to no-operation MDCAdapter implementation.

> SLF4J: See http://www.slf4j.org/codes.html#no_static_mdc_binder for further details.

> <and there it just hangs>
>
>
> Perhaps some missing dependency?

Thanks for the bug report (and the follow-up precisions you sent)!



$ /usr/share/zookeeper/bin/zkCli.sh


(However, I also get the hanging issue if I do not install zookeeperd.)




        https://www.slf4j.org/codes.html#StaticLoggerBinder



Finally, as:

I would tend to discuss only the SLF4J issue and ignore the rest.

Please tell me what you think,

>
>
> Thanks,
> Chris.
>
>

Thanks to you,

--
Pierre

Yet I fail to reproduce it on testing. I installed zookeeper and zookeeperd on testing, then ran specifying nothing about the classpath (it is already handled in the MANIFEST.MF file of the zookeeper jar), and I could enter commands (though with no prompt, as you say). I guess there is some difference in the versions of the dependencies between stable and testing, as you underline that the dependencies come from stable. Concerning the SLF4J warning: in the past I already stumbled upon this and visited the URI which is in the warning message. Because of the last paragraph in the relevant section therein, I was unsure I should choose a SLF4J binding as this would impose my choice to the end user. What do you think? - I think there is a mismatch somewhere in the versions of the dependencies between stable and testing; - I cannot reproduce on a system with dependencies fetched from testing only,

OpenPGP_signature
Description: OpenPGP digital signature