best-eve-12546
11/30/2022, 6:40 PMcuddly-arm-8412
12/02/2022, 1:08 AMbland-orange-13353
12/02/2022, 8:03 PMbumpy-journalist-41369
12/05/2022, 3:04 PMhallowed-lizard-92381
12/05/2022, 6:37 PMproud-table-38689
12/06/2022, 12:17 AMswift-eye-81077
12/06/2022, 8:38 PMkubectl get pods
and noticed that the actions pod had the status ImagePullBackOff.
After deleting the pod to try to rebuild it I've checked the logs and got the error Error from server (BadRequest): container "acryl-datahub-actions" in pod "datahub-acryl-datahub-actions-7667977f8b-v6vhp" is waiting to start: image can't be pulled.
Does anyone know how to fix this issue?victorious-spoon-76468
12/07/2022, 1:33 PMpublic
schema, and changing the default schema is not viable for the same reason. Is there a way to easily change the schema setting in datahub.?fierce-baker-1392
12/07/2022, 1:50 PMkubectl create secret generic mysql-secrets --from-literal=mysql-root-password=datahub
kubectl create secret generic neo4j-secrets --from-literal=neo4j-password=datahub
helm repo add datahub <https://helm.datahubproject.io/>
helm install prerequisites datahub/datahub-prerequisites
helm upgrade datahub datahub/datahub
The error messages:microscopic-mechanic-13766
12/07/2022, 2:52 PMproud-table-38689
12/08/2022, 12:21 AMMETADATA_SERVICE_AUTH_ENABLED
in the helm chart now UI-based ingestion fails (CLI/API based works just fine). How do I add an API token to the interface? (if that’s even needed?)proud-table-38689
12/08/2022, 2:11 AMacceptable-baker-8114
12/08/2022, 12:08 PMearly-byte-99364
12/08/2022, 8:26 PMbrainy-intern-50400
12/09/2022, 12:42 PM./gradlew :datahub-frontend:dist -x yarnTest -x yarnLint
i get build failed
. I get the same error on a othere ubuntu machine. Its allways a problem to start yarn:
Execution failed for task ':datahub-web-react:yarnInstall'.
> A problem occurred starting process 'command 'yarn''
To Reproduce
Steps to reproduce the behavior:
1. Go to 'datahub'
2. Execute ./gradlew :datahub-frontend:dist -x yarnTest -x yarnLint
3. See error
Expected behavior
Gradle should build datahub without error.
Desktop (please complete the following information):
• OS: Ubuntu 20.04.5 LTS
• Version 0.9.3
(build 11.0.17+8-post-Ubuntu-1ubuntu220.04, mixed mode, sharing) : here a link to the closed issue: https://github.com/datahub-project/datahub/issues/6677 Thank u all here :)astonishing-answer-96712
12/09/2022, 5:56 PMastonishing-answer-96712
12/09/2022, 5:58 PM--stacktrace
or --debug
for more detailed outputs that we can help with herefew-tent-75240
12/09/2022, 6:27 PMsome-alligator-9844
12/12/2022, 10:02 AMpurple-beach-52588
12/13/2022, 5:00 PMworried-animal-81235
12/14/2022, 1:58 AMbumpy-pharmacist-66525
12/14/2022, 1:57 PMhallowed-lizard-92381
12/14/2022, 7:51 PMmicroscopic-mechanic-13766
12/15/2022, 9:54 AMred-waitress-53338
12/15/2022, 10:07 PMmicroscopic-twilight-7661
12/16/2022, 8:10 AMdatahub-gms
pod fails to start.
The only error messages I can see are:
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
But I doubt this is the issue. And these messages:
│ ANTLR Tool version 4.5 used for code generation does not match the current runtime version 4.7.2ANTLR Runtime version 4.5 used for parser compilation does not match the current runtime version 4.7.2ANTLR Too │
│ l version 4.5 used for code generation does not match the current runtime version 4.7.2ANTLR Runtime version 4.5 used for parser compilation does not match the current runtime version 4.7.2ERROR StatusLogger │
│ Log4j2 could not find a logging implementation. Please add log4j-core to the classpath. Using SimpleLogger to log to the console... │
│ ANTLR Tool version 4.5 used for code generation does not match the current runtime version 4.7.2ANTLR Runtime version 4.5 used for parser compilation does not match the current runtime version 4.7.2ANTLR Too │
│ l version 4.5 used for code generation does not match the current runtime version 4.7.2ANTLR Runtime version 4.5 used for parser compilation does not match the current runtime version 4.7.22022/12/15 15:28:2 │
│ 2 Command exited with error: exit status 1
I've tried increasing pod memory limits but that didn't help either (according to this issue it has been resolved in newer version, just wanted to rule it out)microscopic-mechanic-13766
12/16/2022, 10:12 AMrough-flag-51828
12/16/2022, 11:45 AMstrong-traffic-65959
12/16/2022, 2:47 PMfuture-iron-16086
12/16/2022, 9:18 PMhelm upgrade --install datahub datahub/datahub --debug
history.go:56: [debug] getting history for release datahub
upgrade.go:142: [debug] preparing upgrade for datahub
upgrade.go:524: [debug] copying values from datahub (v6) to new release.
upgrade.go:150: [debug] performing update for datahub
upgrade.go:322: [debug] creating upgraded release for datahub
client.go:310: [debug] Starting delete for "datahub-elasticsearch-setup-job" Job
client.go:128: [debug] creating 1 resource(s)
client.go:540: [debug] Watching for changes to Job datahub-elasticsearch-setup-job with timeout of 5m0s
client.go:568: [debug] Add/Modify event for datahub-elasticsearch-setup-job: ADDED
client.go:607: [debug] datahub-elasticsearch-setup-job: Jobs active: 0, jobs failed: 0, jobs succeeded: 0
client.go:568: [debug] Add/Modify event for datahub-elasticsearch-setup-job: MODIFIED
client.go:607: [debug] datahub-elasticsearch-setup-job: Jobs active: 1, jobs failed: 0, jobs succeeded: 0
client.go:568: [debug] Add/Modify event for datahub-elasticsearch-setup-job: MODIFIED
client.go:607: [debug] datahub-elasticsearch-setup-job: Jobs active: 0, jobs failed: 0, jobs succeeded: 0
client.go:568: [debug] Add/Modify event for datahub-elasticsearch-setup-job: MODIFIED
client.go:310: [debug] Starting delete for "datahub-kafka-setup-job" Job
client.go:128: [debug] creating 1 resource(s)
client.go:540: [debug] Watching for changes to Job datahub-kafka-setup-job with timeout of 5m0s
client.go:568: [debug] Add/Modify event for datahub-kafka-setup-job: ADDED
client.go:607: [debug] datahub-kafka-setup-job: Jobs active: 1, jobs failed: 0, jobs succeeded: 0
client.go:568: [debug] Add/Modify event for datahub-kafka-setup-job: MODIFIED
client.go:607: [debug] datahub-kafka-setup-job: Jobs active: 1, jobs failed: 0, jobs succeeded: 0
client.go:568: [debug] Add/Modify event for datahub-kafka-setup-job: MODIFIED
client.go:607: [debug] datahub-kafka-setup-job: Jobs active: 1, jobs failed: 0, jobs succeeded: 0
client.go:568: [debug] Add/Modify event for datahub-kafka-setup-job: MODIFIED
client.go:607: [debug] datahub-kafka-setup-job: Jobs active: 0, jobs failed: 0, jobs succeeded: 0
client.go:568: [debug] Add/Modify event for datahub-kafka-setup-job: MODIFIED
client.go:310: [debug] Starting delete for "datahub-mysql-setup-job" Job
client.go:128: [debug] creating 1 resource(s)
client.go:540: [debug] Watching for changes to Job datahub-mysql-setup-job with timeout of 5m0s
client.go:568: [debug] Add/Modify event for datahub-mysql-setup-job: ADDED
client.go:607: [debug] datahub-mysql-setup-job: Jobs active: 1, jobs failed: 0, jobs succeeded: 0
client.go:568: [debug] Add/Modify event for datahub-mysql-setup-job: MODIFIED
client.go:607: [debug] datahub-mysql-setup-job: Jobs active: 1, jobs failed: 0, jobs succeeded: 0
client.go:568: [debug] Add/Modify event for datahub-mysql-setup-job: MODIFIED
client.go:607: [debug] datahub-mysql-setup-job: Jobs active: 1, jobs failed: 0, jobs succeeded: 0
client.go:568: [debug] Add/Modify event for datahub-mysql-setup-job: MODIFIED
client.go:607: [debug] datahub-mysql-setup-job: Jobs active: 1, jobs failed: 0, jobs succeeded: 0
client.go:568: [debug] Add/Modify event for datahub-mysql-setup-job: MODIFIED
client.go:607: [debug] datahub-mysql-setup-job: Jobs active: 1, jobs failed: 1, jobs succeeded: 0
client.go:568: [debug] Add/Modify event for datahub-mysql-setup-job: MODIFIED
client.go:607: [debug] datahub-mysql-setup-job: Jobs active: 1, jobs failed: 1, jobs succeeded: 0
upgrade.go:434: [debug] warning: Upgrade "datahub" failed: pre-upgrade hooks failed: timed out waiting for the condition
Error: UPGRADE FAILED: pre-upgrade hooks failed: timed out waiting for the condition
helm.go:84: [debug] pre-upgrade hooks failed: timed out waiting for the condition
UPGRADE FAILED
main.newUpgradeCmd.func2
<http://helm.sh/helm/v3/cmd/helm/upgrade.go:200|helm.sh/helm/v3/cmd/helm/upgrade.go:200>
<http://github.com/spf13/cobra.(*Command).execute|github.com/spf13/cobra.(*Command).execute>
<http://github.com/spf13/cobra@v1.4.0/command.go:856|github.com/spf13/cobra@v1.4.0/command.go:856>
<http://github.com/spf13/cobra.(*Command).ExecuteC|github.com/spf13/cobra.(*Command).ExecuteC>
<http://github.com/spf13/cobra@v1.4.0/command.go:974|github.com/spf13/cobra@v1.4.0/command.go:974>
<http://github.com/spf13/cobra.(*Command).Execute|github.com/spf13/cobra.(*Command).Execute>
<http://github.com/spf13/cobra@v1.4.0/command.go:902|github.com/spf13/cobra@v1.4.0/command.go:902>
main.main
<http://helm.sh/helm/v3/cmd/helm/helm.go:83|helm.sh/helm/v3/cmd/helm/helm.go:83>
runtime.main
runtime/proc.go:255
runtime.goexit
runtime/asm_amd64.s:1581
It seems that datahub-mysql-setup-job failed to run
Any help to solve it?