Error: Unable to establish connection with ZooKeeper

[UTGuy]

Connecting with the docker-compose name does not work here but connecting with the network IP does. In my sample application, I had the name as simply 'zookeeper' instead of 'compliance-message-queue-zookeeper' and connected with 'zookeeper:2181' and it worked. Is there a name length issue somewhere?

[elkozmon]

Hi.

It seems unlikely that name length would be the issue, but tbh, I have no idea.

Is it possible for you to post your Docker compose file so I can try it out?

Thanks

[UTGuy]

This is a shortened version of it...

#-------------------------------------------------------------------------------------------------------------
# Copyright (c) Microsoft Corporation. All rights reserved.
# Licensed under the MIT License. See https://go.microsoft.com/fwlink/?linkid=2090316 for license information.
#-------------------------------------------------------------------------------------------------------------

    version: '3.5'
    services:
      compliance-message-queue-zookeeper:
        image: zookeeper
        ports:
          - 2181:2181
          - 9100:8080
        networks:
          - proxynet

      compliance-message-queue-zookeeper-ui:
        image: elkozmon/zoonavigator
        ports:
          - 9101:9000
        environment: 
          CONNECTION_LOCALZK_NAME: compliance-message-queue
          CONNECTION_LOCALZK_CONN: compliance-message-queue-zookeeper:2181
          AUTO_CONNECT_CONNECTION_ID: LOCALZK
        networks:
          - proxynet

      compliance-message-queue-kafka-ui:
        image: digitsy/kafka-magic
        ports:
          - 9102:80
        environment: 
          KMAGIC_ALLOW_TOPIC_DELETE: "true"
          CONFIG_STORE_TYPE: "file"
          CONFIG_STORE_CONNECTION: "Data Source=KafkaMagicConfig.db;"
        networks:
          - proxynet

      compliance-message-queue-kafka-1:
        image: bitnami/kafka
        ports:
          - "9095:9092"
        environment:
          ALLOW_PLAINTEXT_LISTENER: 'yes'
          KAFKA_ZOOKEEPER_CONNECT: compliance-message-queue-zookeeper:2181
          KAFKA_BROKER_ID: 500
          KAFKA_offsets_topic_replication_factor: 1
        volumes:
          - ./volumes/kafka/docker.sock:/var/run/docker.sock
          - ./volumes/kafka/data/500:/kafka
        networks:
          - proxynet

    networks:
      proxynet:
        name: content_config_tool_network

[elkozmon]

Strange, works totally fine for me.

[UTGuy]

I've removed the image and re- downloaded. I'm trying to clear out any cached images I might have... but no luck so far

here are the logs...

SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/app/lib/ch.qos.logback.logback-classic-1.2.3.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/app/lib/org.slf4j.slf4j-log4j12-1.6.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder]
[info] application - Enabling Filter: play.filters.headers.SecurityHeadersFilter
[info] application - Enabling Filter: play.filters.cors.CORSFilter
[info] play.api.Play - Application started (Prod) (no global state)
[info] p.c.s.AkkaHttpServer - Listening for HTTP on /0.0.0.0:9000

[elkozmon]

When ZooNavigator fails to connect to ZooKeeper, there should be an error log as well. Could you post that as well?

Also, do you experience the same problem with the shortened version of the Docker compose file you posted above?

I suspect there's some network issue rather than a bug in ZooNavigator.

[UTGuy]

The zookeeper logs show no error. I don't have the problem with the shortened version unfortunately, but theres not much difference with the larger version. It is being used in a .devContainer (https://code.visualstudio.com/docs/remote/containers)

[UTGuy]

I've given up... I just named the zookeeper service zookeeper and told zoonavigator it was zookeeper:2181. I have no idea why it can't use that alias in a dev container

[elkozmon]

Sorry, wish I could help :(