https://datahubproject.io logo
Join Slack
Powered by
Hi, Trying to execute datahub docker on AWS - EC2 ...
# troubleshoot
h
Hi, Trying to execute datahub docker on AWS - EC2 instance. And when I try to ingest mysql_to_datahub recipe, I get the following-
e
There may be some networking issues between the containers. Can you confirm that frontend can talk to gms in your ec2 docker setup?
h
How to ascertain that ?
The list of images running
e
ah
Can you deploy head for gms? Seems like it is using latest
That must be it
Wait hmn so there are two gms containers?
Can you kill the old one?
h
ok let me try that
Getting this when executing datahub docker quickstart on EC2
From the log file.
m
@handsome-football-66174: looks like both the gms-s are no longer running, could you just restart it?
h
When I restart Datahub I get the above errors. Using datahub docker quickstart
m
datahub docker check
is still showing gms down?
h
yes The following issues were detected: - datahub-gms is not running
m
and what does 
docker ps
show?
h
m
ok, can you run 
datahub docker quickstart
again?
also 
docker info | grep Total
would be good to see
h
ok
datahub docker quickstart
Output of docker info | grep Total WARNING: bridge-nf-call-iptables is disabled WARNING: bridge-nf-call-ip6tables is disabled  Total Memory: 15.66GiB
m
what is the output of 
docker logs datahub-gms
h
Pretty long , but see this error io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection refused: datahub-gms/172.18.0.7:8080 datahub-frontend-react  | Caused by: java.net.ConnectException: Connection refused datahub-frontend-react  | at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) datahub-frontend-react  | at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:716) datahub-frontend-react  | at io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:330) datahub-frontend-react  | at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:334) datahub-frontend-react  | at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:702) datahub-frontend-react  | at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:650) datahub-frontend-react  | at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:576) datahub-frontend-react  | at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:493) datahub-frontend-react  | at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989) datahub-frontend-react  | at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) datahub-frontend-react  | at java.lang.Thread.run(Thread.java:748)
e
Can we start over and run 
datahub docker nuke
?
Let’s make sure there are no running containers related to datahub
after running ^
h
Sure
did the following- datahub docker nuke datahub docker quickstart Same error- ............. Unable to run quickstart - the following issues were detected: - datahub-gms is not running
Is there anything specific to be done when executing on an EC2.
e
Can you see why gms is failing? Like docker logs
b
GMS keeps going down ... this is very odd. Do you mind extracting the GMS logs? I will send you the guide on how to get them
Please extract the logs from datahub GMS container, as detailed here: https://datahubproject.io/docs/how/extract-container-logs/
And if possible send the zipped copy over for review!
m
@big-carpet-38439: we debugged this with @handsome-football-66174 yesterday and solved this issue. The problem was the mem-limit: 512 on the docker quickstart which was conflicting with the xmx 1G on the jvm opts.
b
Awesome. Thanks for closing the loop
2 Views
Open in Slack
PreviousNext
Powered by