I ve messed something up rolling on the floor laughing I can DataHub #troubleshoot

I've messed something up :rolling_on_the_floor_lau...

rhythmic-stone-77840

01/06/2023, 8:31 PM

I've messed something up 🤣 I can't seem to access the docker logs. Running the suggested command from the docs

docker exec --privileged datahub-gms ls -la /tmp/datahub/logs/gms

returns back a

cannot access '/tmp/datahub/logs/gms': No such file or directory

- I've rebuild my docker setup from scratch and it's still having issues. The tmp file has no datahub folder in it at all

✅ 1

rhythmic-stone-77840

01/06/2023, 8:36 PM

within temp there's only

hsperfdata_datahub

jetty-0_0_0_0-8080-war_war-_-any-10143344340197983109

kafka.client.truststore.jks

rhythmic-stone-77840

01/06/2023, 8:40 PM

running version

v.0.9.3

modern-artist-55754

01/06/2023, 10:28 PM

Can you check

docker logs -f datahub-gms

rhythmic-stone-77840

01/07/2023, 3:53 AM

The gives results back

rhythmic-stone-77840

01/07/2023, 4:34 AM

I've run

datahub docker nuke

docker system prune -a

and then remade everything using

python3 -m datahub docker quickstart --graph-service-impl elasticsearch --version v0.9.3

and it still has issues. It also seems to restart the mysql & elasticsearch containers a bunch of times before it decides everything is ok and running.

modern-artist-55754

01/07/2023, 5:53 AM

Ah that's sometime the case, the mysql & elastic setup were not setup in time before gms expects the stack ready. What you can do is to kill all the containers and run quickstart again, by then mysql and elastic should be ready and gms should be up and running fine.

rhythmic-stone-77840

01/09/2023, 2:16 PM

Once the containers do come up the logs are still not there 😕 Its so weird

rhythmic-stone-77840

01/09/2023, 4:22 PM

Looks like its an issue with 0.9.3. - updated to 0.9.5 and the logs are back to where they should be

3 Views

Open in Slack

Previous Next