Hi team, I am trying to deploy datahub using ./gra...
# troubleshoot
l
Hi team, I am trying to deploy datahub using ./gradlew quickstartDebug command. I am getting the following error: Datahub-gms is running but not healthy Datahub-upgrade exited with an error I am running on version v0.9.2 and also tried running with v0.10.0 and v0.9.6 Can anyone please help me on this?
📖 1
🔍 1
l
Hey there 👋 I'm The DataHub Community Support bot. I'm here to help make sure the community can best support you with your request. Let's double check a few things first: ✅ There's a lot of good information on our docs site: www.datahubproject.io/docs, Have you searched there for a solution? ✅ button ✅ It's not uncommon that someone has run into your exact problem before in the community. Have you searched Slack for similar issues? ✅ button Did you find a solution to your issue? ❌ Sorry you weren't able to find a solution. I'm sending you some tips on info you can provide to help the community troubleshoot. Whenever you feel your issue is solved, please react ✅ to your original message to let us know!
l
Hi @orange-night-91387 can you please help me on this?
o
What you're saying doesn't make sense to me,
I am running on version v0.9.2
This version does not use datahub-upgrade as a part of docker compose, it was added in v0.10. You're using the local gradle command to run, are you trying to check out the codebase at a particular tag to execute it? The gradlew quickstart is for local development and requires you to build your local code. If you're just trying to run datahub at a particular version you can run
datahub docker quickstart
cli and specify the version using
--version
l
Sorry, i am running v0.10.2 version.
I am trying to fork datahub so i was runnjng ./gradlew quickstartDebug command
It was pulling debug tag images and v0.10.2 images
o
What error did upgrade exit with?
l
java.net.ConnectException: Connection refused at org.elasticsearch.client.RestClient.extractAndWrapCause(RestClient.java:879) ~[elasticsearch-rest-client-7.10.2.jar!/:7.10.2] at org.elasticsearch.client.RestClient.performRequest(RestClient.java:283) ~[elasticsearch-rest-client-7.10.2.jar!/:7.10.2] at org.elasticsearch.client.RestClient.performRequest(RestClient.java:270) ~[elasticsearch-rest-client-7.10.2.jar!/:7.10.2] at org.elasticsearch.client.RestHighLevelClient.internalPerformRequest(RestHighLevelClient.java:1632) ~[elasticsearch-rest-high-level-client-7.10.2.jar!/:7.10.2] at org.elasticsearch.client.RestHighLevelClient.performRequest(RestHighLevelClient.java:1617) ~[elasticsearch-rest-high-level-client-7.10.2.jar!/:7.10.2] at org.elasticsearch.client.IndicesClient.exists(IndicesClient.java:974) ~[elasticsearch-rest-high-level-client-7.10.2.jar!/:7.10.2] at com.linkedin.metadata.search.elasticsearch.indexbuilder.ESIndexBuilder.buildReindexState(ESIndexBuilder.java:141) ~[metadata-io.jar!/:na] at com.linkedin.metadata.graph.elastic.ElasticSearchGraphService.getReindexConfigs(ElasticSearchGraphService.java:331) ~[metadata-io.jar!/:na] at com.linkedin.datahub.upgrade.system.elasticsearch.util.IndexUtils.getAllReindexConfigs(IndexUtils.java:34) ~[classes!/:na] at com.linkedin.datahub.upgrade.system.elasticsearch.steps.BuildIndicesPreStep.lambda$executable$0(BuildIndicesPreStep.java:53) ~[classes!/:na] at com.linkedin.datahub.upgrade.impl.DefaultUpgradeManager.executeStepInternal(DefaultUpgradeManager.java:106) ~[classes!/:na] at com.linkedin.datahub.upgrade.impl.DefaultUpgradeManager.executeInternal(DefaultUpgradeManager.java:65) ~[classes!/:na] at com.linkedin.datahub.upgrade.impl.DefaultUpgradeManager.executeInternal(DefaultUpgradeManager.java:39) ~[classes!/:na] at com.linkedin.datahub.upgrade.impl.DefaultUpgradeManager.execute(DefaultUpgradeManager.java:30) ~[classes!/:na] at com.linkedin.datahub.upgrade.UpgradeCli.run(UpgradeCli.java:80) ~[classes!/:na] at org.springframework.boot.SpringApplication.callRunner(SpringApplication.java:812) ~[spring-boot-2.5.12.jar!/:2.5.12] at org.springframework.boot.SpringApplication.callRunners(SpringApplication.java:796) ~[spring-boot-2.5.12.jar!/:2.5.12] at org.springframework.boot.SpringApplication.run(SpringApplication.java:346) ~[spring-boot-2.5.12.jar!/:2.5.12] at org.springframework.boot.builder.SpringApplicationBuilder.run(SpringApplicationBuilder.java:143) ~[spring-boot-2.5.12.jar!/:2.5.12] at com.linkedin.datahub.upgrade.UpgradeCliApplication.main(UpgradeCliApplication.java:23) ~[classes!/:na] at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:na] at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:na] at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:na] at java.base/java.lang.reflect.Method.invoke(Method.java:566) ~[na:na] at org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:49) ~[datahub-upgrade.jar:na] at org.springframework.boot.loader.Launcher.launch(Launcher.java:108) ~[datahub-upgrade.jar:na] at org.springframework.boot.loader.Launcher.launch(Launcher.java:58) ~[datahub-upgrade.jar:na] at org.springframework.boot.loader.JarLauncher.main(JarLauncher.java:88) ~[datahub-upgrade.jar:na] Caused by: java.net.ConnectException: Connection refused at java.base/sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) ~[na:na] at java.base/sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:777) ~[na:na] at org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processEvent(DefaultConnectingIOReactor.java:174) ~[httpcore-nio-4.4.12.jar!/:4.4.12] at org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processEvents(DefaultConnectingIOReactor.java:148) ~[httpcore-nio-4.4.12.jar!/:4.4.12] at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor.execute(AbstractMultiworkerIOReactor.java:351) ~[httpcore-nio-4.4.12.jar!/:4.4.12] at org.apache.http.impl.nio.conn.PoolingNHttpClientConnectionManager.execute(PoolingNHttpClientConnectionManager.java:221) ~[httpasyncclient-4.1.4.jar!/:4.1.4] at org.apache.http.impl.nio.client.CloseableHttpAsyncClientBase$1.run(CloseableHttpAsyncClientBase.java:64) ~[httpasyncclient-4.1.4.jar!/:4.1.4] at java.base/java.lang.Thread.run(Thread.java:829) ~[na:na] Failed Step 1/5: BuildIndicesPreStep. Failed after 0 retries. Exiting upgrade SystemUpdate with failure. Upgrade SystemUpdate completed with result FAILED. Exiting...
This is the error in datahub-upgrade
Actually i am getting Problem with request: Get https//elasticsearch9200 EOF sleeping 1s So i changed host to 0.0.0.0 in elasticsearch docker.env and gms docker.env files
After I changed to 0.0.0.0 , i am not facing EOF issue
o
0.0.0.0 resolves to localhost for the container so it won't work
You don't have anything running on port 9200 for that container so it gives you a connection refused error
Not sure about the EOF error for Elastic though, maybe you need to run a
docker system prune
?
l
0.0.0.0:9200 it was running in this way because when I give this address in browser i am able to access that
o
If you're not giving it enough filespace Elastic will run into issues so it could be that
Docker containers set up a separate network address
l
I ran docker system prune and i have cleaned all images and containers and ran so many times but still i am facing the same issue
Where can I give that filespace?
And i am able to ping elasticsearch from elasticsearch-setup container and vice versa
But i am getting EOF error in elasticsearch-setup container
This is the space occupied by docker. Still it gives me EOF in elasticsearch-setup container
Hi @orange-night-91387 , Could you please help me on this?