Hello Team, I am new to Datahub and i am getting this error while running datahub docker quickstart, It was working previously and we did a system restart and started the docker services again and ran a quickstart and getting this error. dependency failed to start: container for service "zookeeper" exited (1) .............. [+] Running 6/7 ⠿ Container zookeeper Error 2.9s ⠿ Container mysql Healthy 0.5s ⠿ Container broker Created 0.0s ⠿ Container mysql-setup Started 1.1s ⠿ Container schema-registry Created 0.0s ⠿ Container elasticsearch Healthy 0.5s ⠿ Container elasticsearch-setup Started 1.0s dependency failed to start: container for service "zookeeper" exited (1) ............. Unable to run quickstart - the following issues were detected: - datahub-frontend-react is not running - datahub-gms is not running - kafka-setup is still running - schema-registry is not running - broker is not running - zookeeper is not running

Hey there 👋 I'm The DataHub Community Support bot. I'm here to help make sure the community can best support you with your request. Let's double check a few things first: ✅ There's a lot of good information on our docs site: www.datahubproject.io/docs, Have you searched there for a solution? ✅ button ✅ It's not uncommon that someone has run into your exact problem before in the community. Have you searched Slack for similar issues? ✅ button Did you find a solution to your issue? ❌ Sorry you weren't able to find a solution. I'm sending you some tips on info you can provide to help the community troubleshoot. Whenever you feel your issue is solved, please react ✅ to your original message to let us know!

Could you share the log of zookeeper container?

Thankyou, Now i am getting below when running quickstart : datahub docker quickstart --version=v0.9.6 --quickstart-compose-file docker-compose.yml .... Unable to run quickstart - the following issues were detected: - datahub-gms is still starting - elasticsearch is still starting If you think something went wrong, please file an issue at https://github.com/datahub-project/datahub/issues or send a message in our Slack https://slack.datahubproject.io/ Be sure to attach the logs from /tmp/tmpqb_8s3f_.log I could below in the logs:- datahub-gms | 2023/05/15 220654 Waiting for: http://elasticsearch:9200 datahub-gms | 2023/05/15 220654 Waiting for: tcp://mysql:3306 datahub-gms | 2023/05/15 220654 Waiting for: tcp://broker:29092 datahub-gms | 2023/05/15 220654 Problem with dial: dial tcp 172.18.0.529092 connect: connection refused. Sleeping 1s datahub-gms | 2023/05/15 220654 Problem with request: Get "http://elasticsearch:9200": dial tcp 172.18.0.29200 connect: connection refused. Sleeping 1s datahub-gms | 2023/05/15 220654 Problem with dial: dial tcp 172.18.0.43306 connect: connection refused. Sleeping 1s datahub-gms | 2023/05/15 220655 Problem with dial: dial tcp 172.18.0.529092 connect: connection refused. Sleeping 1s datahub-gms | 2023/05/15 220655 Problem with request: Get "http://elasticsearch:9200": dial tcp 172.18.0.29200 connect: connection refused. Sleeping 1s datahub-gms | 2023/05/15 220655 Connected to tcp://mysql:3306 datahub-gms | 2023/05/15 220656 Problem with dial: dial tcp 172.18.0.529092 connect: connection refused. Sleeping 1s datahub-gms | 2023/05/15 220656 Problem with request: Get "http://elasticsearch:9200": dial tcp 172.18.0.29200 connect: connection refused. Sleeping 1s datahub-gms | 2023/05/15 220657 Problem with dial: dial tcp 172.18.0.529092 connect: connection refused. Sleeping 1s datahub-gms | 2023/05/15 220657 Problem with request: Get "http://elasticsearch:9200": dial tcp 172.18.0.29200 connect: connection refused. Sleeping 1s datahub-gms | 2023/05/15 220658 Problem with request: Get "http://elasticsearch:9200": dial tcp 172.18.0.29200 connect: connection refused. Sleeping 1s datahub-gms | 2023/05/15 220658 Problem with dial: dial tcp 172.18.0.529092 connect: connection refused. Sleeping 1s datahub-gms | 2023/05/15 220659 Problem with request: Get "http://elasticsearch:9200": dial tcp 172.18.0.29200 connect: connection refused. Sleeping 1s datahub-gms | 2023/05/15 220659 Problem with dial: dial tcp 172.18.0.529092 connect: connection refused. Sleeping 1s datahub-gms | 2023/05/15 220700 Problem with request: Get "http://elasticsearch:9200": dial tcp 172.18.0.29200 connect: connection refused. Sleeping 1s datahub-gms | 2023/05/15 220700 Problem with dial: dial tcp 172.18.0.529092 connect: connection refused. Sleeping 1s datahub-gms | 2023/05/15 220701 Problem with dial: dial tcp 172.18.0.529092 connect: connection refused. Sleeping 1s datahub-gms | 2023/05/15 220701 Problem with request: Get "http://elasticsearch:9200": dial tcp 172.18.0.29200 connect: connection refused. Sleeping 1s datahub-gms | 2023/05/15 220702 Problem with request: Get "http://elasticsearch:9200": dial tcp 172.18.0.29200 connect: connection refused. Sleeping 1s datahub-gms | 2023/05/15 220702 Problem with dial: dial tcp 172.18.0.529092 connect: connection refused. Sleeping 1s datahub-gms | 2023/05/15 220703 Problem with request: Get "http://elasticsearch:9200": dial tcp 172.18.0.29200 connect: connection refused. Sleeping 1s datahub-gms | 2023/05/15 220703 Problem with dial: dial tcp 172.18.0.529092 connect: connection refused. Sleeping 1s datahub-gms | 2023/05/15 220704 Problem with request: Get "http://elasticsearch:9200": dial tcp 172.18.0.29200 connect: connection refused. Sleeping 1s datahub-gms | 2023/05/15 220704 Problem with dial: dial tcp 172.18.0.529092 connect: connection refused. Sleeping 1s datahub-gms | 2023/05/15 220705 Problem with dial: dial tcp 172.18.0.529092 connect: connection refused. Sleeping 1s

Could you try updating to a more recent version and see if that works?

Yes tried v0.10.2 just running docker datahub quickstart is failing as well with same errors, mostly zookeeper and datahub-gms containers not able to start.

Hey @astonishing-answer-96712 For me broker is failing

Is there anyone can help guide, I looked into some similar errors received by others and most of the suggesting to destroy and rec-create the containers, Instead of this is their any fix available?.

@icy-kitchen-54364 you still facing issue ?

Thanks @astonishing-father-13229 did you had to destroy the containers and recreate it?. Did you already backed up your configs and data?. I am still facing issue. I don't have backup for Development environment where i am facing this issue and don't want to destroy and loss any data. Trying to find a solution without losing the data

Yes, I took backup up my configs and data