[ZooKeeperClient] Auth failed. (kafka.zookeeper.ZooKeeperClient) about event-streams HOT 3 CLOSED

Thank you very much!

Problem 1: Starting the elastic server is solved!

Problem 2: Was my fault too. I f had some old data in the zookeeper volumes from previous installations. After removing this, all things worked fine.

from event-streams.

Thanks very much for getting in touch, and sorry that you're having trouble with this.

There are two issues that I can see in here.

The Elastic Search pods aren't starting. The relevant error here in your comment is:

max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]

For message indexing capabilities (which are enabled by default), you need to set the vm.max_map_count property to at least 262144 on all IBM Cloud Private nodes in your cluster (not only the master node). There are instructions on how to do this at https://ibm.github.io/event-streams/installing/prerequisites/

Alternatively, you can disable message indexing for your Event Streams install, so that the Elastic Search pods aren't deployed.

The Kafka pods are having problems connecting to ZooKeeper which is why they shut down. (The auth failure is not the issue here, that is always in the log at startup). I can't immediately tell the reason for this, but at first glance it looks like a networking/connectivity issue between the pods.

If you would be willing to collect additional logs, that would be helpful for investigating this further. I've attached a script for collecting this. Instructions for running it are at the top of the file.
get-logs.sh.txt

If you could send us the zip that this script would produce, the additional info might help uncover the reason for connections not being allowed from the Kafka pods to the ZooKeeper pods.

from event-streams.

Can I also check what OS you're running on and if SE Linux is enabled?

Thanks!

from event-streams.