Bug#1025012: zookeeper: starts but is completely unusable

[Filippo Giunchedi]

found 3.8.0-11+deb12u1
thanks

On Tue, Dec 06, 2022 at 11:33:07PM +0100, Christoph Anton Mitterer wrote:
[...]
> >  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?
> 
> Well since that two infamous security holes, log4j has a somewhat
> damaged reputation ;-) ... but apart from that I think this would make
> the most sense here.
> 
> As I've said in
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025012#20 :
> 
> /usr/share/java/slf4j-log4j12.jar wasn't enough for me and I needed to
> add /usr/share/java/log4j-1.2.jar to the CLASSPATH instead, in order to
> get output to /var/log/zookeeper

I ran into the same issue (i.e. missing zookeeper logs) on Bookworm.

Reproducible with the following:
* apt install zookeeperd
* systemctl start zookeeper
* observe no logs written to /var/log/zookeeper as the default zk conf would like to do

The fix for me was indeed to add log4j and its slf4j backend jars to CLASSPATH in /etc/zookeeper/conf/environment

HTH,
Filippo