Hi, I am facing a similar problem to that of <anot...
# troubleshoot
m
Hi, I am facing a similar problem to that of another complaint in this Slack. I followed the steps in the self-hosted datahub and can't proceed after the
datahub docker quickstart
step. I run into the following issue: see image below and file as stated in the cmd | I'm on a Windows computer 4 CPUs, 16GB RAM and I believe I satisfy the 2GB Swap area and 10GB disk space. thanks for any help!
m
@mysterious-hamburger-65313: have you ensured your docker installation has ~ 6GB+ memory configured?
e.g. I have
Copy code
docker info | grep -i memory
Total Memory: 6.782GiB
m
yes - on my end, I have
m
interesting, what does
docker logs elasticsearch
give you?
m
I output the results in the file below
I believe the end state, if all the installation is up and running, is accessing datahub via localhost, correct? I'm unable to access the port via localhost but I do see some of the configs in docker desktop running
do you think it be possible that something may have interrupted the installation and I'd just have to reinstall or something else from the logs?
m
can you
curl <http://localhost:8080/config>
?
What does
docker logs datahub-gms
give you?
m
message has been deleted
for the latter command, I got
m
Very strange that elastic isn’t starting up. Reboot and retry I think.
The elastic logs don’t show any errors
Also maybe run d`atahub docker nuke`
To clear out any container state
m
I'll try it and update - thanks for all the help!
I ran datahub docker quickstart and now have the following
I was able to resolve the above by nuking and then running quickstart again; my next issue is similar to another user I spot will consolidate to that thread nvm, it seems when my datahub-gms is not healthy is doesn't show this but when it is it complains about the output shown in the txt above