https://datahubproject.io logo
Join Slack
Powered by
Hi Team, I am experiencing error on datahub-gms co...
# troubleshoot
g
Hi Team, I am experiencing error on datahub-gms container. It keeps on showing 'unhealthy'. I've tried restarting the containers however, same issue again and again.
n
Good day @glamorous-spring-97970 Do you have the metadata_service_authentication enabled? And is the datahub-datahub-system-update-job successful?
I had the same error earlier (I could be wrong about this. So pardon me if I am) and the root cause was that when you enable metadata_service_authentication, the system update job looks for the datahub_auth_secrets before the secrets is created. The workaround I used is 1. Deploy datahub with default values (metadata_service_authentication is disabled by default) 2. Upgrade your deployment with system update disabled and metadata_service_authentication enabled 3. Upgrade your deployment again with both metadata_service_authentication and system update enabled Hope this helps.
g
Hi @nutritious-salesclerk-57675 Thanks for replying. Tbh, I haven't enabled the "metadata_service_authentication". It's all default settings
n
Good day @glamorous-spring-97970 Is your datahub-system-update-job successful?
g
Not sure, where is that ?
n
Its part of the deployment. If you have deployed with k8s, you would be able to see it as a pod.
g
@glamorous-spring-97970 are you still facing issue ?
g
Hi @gentle-hamburger-31302, I am again experiencing the same issue. One of the containers images (linkedin/datahub-gms:head) is unhealthy and I am unable to login to the Datahub tool.
g
@incalculable-ocean-74010 Could you please look into
g
@incalculable-ocean-74010 -- FYI
g
@glamorous-spring-97970 Could you please attach log of container
Copy code
docker logs datahub-gms
g
DockerContainerDatahub-GMS-json.log
DockerContainerDatahub-GMS-json.log
@gentle-hamburger-31302 - This one is the latest.
Latest DatahubGMS Logs.zip
@gentle-hamburger-31302 - Any luck ?
i
It looks like this deployment was done through DataHub cli using: 
datahub docker quickstart
, in that case can you please run:
Copy code
datahub docker quickstart --backup --backup-file datahub.sql
Then
Copy code
datahub docker nuke --keep-data
Once that is done, please run:
Copy code
datahub docker quickstart --version 0.10.3
This is to ensure you: 1.) Backup the data in the instance. 2.) Delete the running containers but not the state. 3.) Deploy DataHub on a stable version (not head)
g
Thanks @incalculable-ocean-74010. Let me try this option and will get back to you. Btw, is it the correct command ?
Copy code
datahub docker quickstart --backup --backup-file datahub.sql
i
I think so
a
g
Hi @incalculable-ocean-74010, I tried your recommended steps however, post pulling the docker images, I've been receiving an error msg for the broker:
i
what is the output of 
docker logs broker
?
g
Huge & massive log "The Cluster ID LC6qyUXwTbamO2IOd4MhWQ doesn't match stored clusterId Some(mZSwmpDgQiuKOXZXEtoZSg) in meta.properties. The broker is trying to join the wrong cluster. Configured zookeeper.connect may be wrong"
Hi @incalculable-ocean-74010 -- Any suggestions on the above ?
i
I do not have any suggestions. This looks unrelated to DataHub, something related with Kafka & Zookeeper.
Open in Slack
PreviousNext
Powered by