Hi all! I am running into this issue when running the quickstart cmd

Unable to run quickstart - the following issues were detected:

- broker is not running

- datahub-gms is still starting

- zookeeper is not running

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/tmp3qcg5vb6.log

i killed all containers and ran docker system prune but still get this error. still debugging this but lmk if you have any ideas, thanks!

hey Jacob! I believe this could be related to some issues we've been seeing with quickstart, but there may be a fix in a more recent version. can you try running this with

--version v0.9.6.1

?

Hi Chris! I have tried running the command with version v0.9.6.1 and still am running into the same issue

gotcha and you're running this to deploy datahub on your local machine?

I have datahub deployed on an Amazon linux 2 instance

hey @miniature-exabyte-80137, do you have enough resources dedicated to the deployment?

yeah we've seen this issue when there's not enough memory dedicated to docker spinning these pods up

Hi @bulky-soccer-26729 and @bulky-electrician-72362, I have the recommended amount of resources allocated to the server. Would like to note that we had datahub QuickStart working two weeks ago and only recently has it started failing for us

The zookeeper service is not running or being started. Do you see this container running and if so we’d need the logs. Quickstart should have dumped zookeeper logs if it was running, so likely something is preventing it from running. It could be many things, but the error is either hidden or before the massive log dump.

Hi David I don’t see this container running

Need the logs earlier than what was posted, any reference to zookeeper there? Additionally earlier in the logs would indicate which docker compose file is being used. All the quickstart compose files include zookeeper, but just wanted to verify it is hitting the expected files for example this.

Hi @brainy-tent-14503! Attached is the full log dumped from quickstart

zookeeper                  | ===> Running preflight checks ... 
zookeeper                  | ===> Check if /var/lib/zookeeper/data is writable ...
zookeeper                  | Command [/usr/local/bin/dub path /var/lib/zookeeper/data writable] FAILED !

Looks like a write path issue. I believe you’d want to run

nuke

, fix the permissions and then start it. @orange-night-91387 - miss anything?

Nope, that should fix it.

sudo mkdir /var/lib/zookeeper
sudo chown <MYUSER> /var/lib/zookeeper
mkdir /var/lib/zookeeper/data

Hi all! We were able to solve the issue after nuking. Just wanted to follow up and see if the cause of the issue is known/how to prevent it in the future. Thanks!