Open kevinsuedmersen opened 3 years ago
Thank you @kevinsuedmersen for mentioning this problem! Not working for me either. Will try to fix it in a couple of days.
Thanks a lot. I updated the issue with logs of the hue container, just in case that helps
@kevinsuedmersen @m-semnani
When running docker-compose up database
the logs should output a message that basically says remove
MYSQL_USER: root
MYSQL_PASSWORD: secret
(remove these values from docker-compose.yml database section)
Given Hue is dependent on the Database, when I remove the values and re-run.. this works for me and I can see the Hue UI.
Though Hue UI (for me) now displays
Could not connect to hive-server:10000 (code THRIFTTRANSPORT): TTransportException(u'Could not connect to hive-server:10000',)
I'll try to resolve the above but in the meantime, I can see the Hue UI
@matthieuoliveira if it helps, you may want to check out the repository https://github.com/kevinsuedmersen/hadoop-sandbox
@kevinsuedmersen Awesome, i'll definitely try out sandbox. Thank you
is the problem solved?
Hello,
Thanks for sharing this great repo. Unfortunately, it seems like hue service is crashing and I cannot access any UIs (not even the namenode UI. I am running the following commands in Ubuntu 20.04 inside WSL2:
Then, after everything is installed and the services are up and running, I do a simple
docker ps
and see the following results:As we can see, the hue service is running is up and running with container ID 3d42461686fb. However, after I wait a few seconds and do
docker ps again
, I see that the hue container is not running anymore:Also, when I try to access the UI of the namenode on localhost:50070 and the UI of hue on localhost:8888, I get the error
This site can’t be reached
(which is obviously the case for the hue service, but surprisingly also for the namenode.The only thing I changed compared to your docker-compose file is that I changed the volume path
/tmp
into./tmp
, but I am getting the same problem in either case. Do you have any recommendations how to fix this issue?Update 1: Below are the logs of the hue container of a few seconds after running
docker-compose up --build -d
and thendocker-compose logs hue
:There are actually more logs, but they are just a repititon of the above. My initial thought was that maybe there is something wrong in the database section of the hue-overrides.ini file, but the host and port name seem to make sense to me. If anyone could share some more insights on this, I'd highly appreciate it.
Thanks, Kevin