I am setting up Airbyte for the first time following the ins Airbyte #replication-ask-ai

I am setting up Airbyte for the first time followi...

Rushil Srivastava

07/18/2023, 1:37 AM

I am setting up Airbyte for the first time following the instructions for GCP here. Unfortunately, upon setup, the dashboard does not load and continuously refreshes waiting for the server to start. In the docker logs I see that the Airbyte Temporal instance is continuously crashing searching for a dynamic config. Do I need to copy this config from somewhere?

Copy code

starting temporal server
Temporal CLI address: 172.18.0.9:7233.
2023/07/18 01:34:39 Loading config; env=docker,zone=,configDir=config
2023/07/18 01:34:39 Loading config files=[config/docker.yaml]
{"level":"info","ts":"2023-07-18T01:34:39.327Z","msg":"Build info.","git-time":"2023-03-29T22:11:52.000Z","git-revision":"edbafd63e19dc0d585ec8cd0ebd793d3c6c6f6d6","git-modified":true,"go-arch":"amd64","go-os":"linux","go-version":"go1.20.2","cgo-enabled":false,"server-version":"1.20.1","debug-mode":false,"logging-call-at":"main.go:143"}
Unable to create dynamic config client. Error: unable to validate dynamic config: dynamic config: config/dynamicconfig/development.yaml: stat config/dynamicconfig/development.yaml: no such file or directory

kapa.ai

07/18/2023, 1:37 AM

A message from kapa.ai

kapa.ai

07/18/2023, 1:38 AM

Based on the information provided in the extracts, it seems like you're encountering an issue with the Temporal server not being able to find a dynamic configuration file. This issue is not directly addressed in the provided extracts. However, there are some general troubleshooting steps you can take based on similar issues discussed in the extracts. Firstly, ensure that you have followed all the steps correctly in the [GCP deployment guide](https://docs.airbyte.com/deploying-airbyte/on-gcp-compute-engine). Secondly, there was a similar issue discussed in a [Slack conversation](https://airbytehq.slack.com/archives/C021JANJ6TY/p1675089139166419) where users were unable to find a specific configuration file (

flags.yml

). The solution was to manually copy the file from the Airbyte GitHub repository. You could try a similar approach with your missing

development.yaml

file. Lastly, if you're still encountering issues, I recommend reaching out to the Airbyte community on [Slack](https://slack.airbyte.com/) for further assistance. Please note that these are general suggestions and may not directly solve your issue as the exact problem you're facing is not covered in the provided extracts.

Rushil Srivastava

07/18/2023, 2:58 AM

I decided to just create a blank file - not sure if this is what’s supposed to happen

Sai

07/18/2023, 5:19 AM

Did that work?

Rushil Srivastava

07/18/2023, 7:33 AM

It got me into the setup stage at least, not sure about anything else yet

Iain Donaldson

07/18/2023, 11:11 AM

This is helpful and it seems to fix the issue. I found that tempral faile with this error after upgrading my airbyte instance this am. I just did the following in my local

airbyte

folder where there is a root owned directory

temporal

once you attempt to start things up:

Copy code

sudo touch ./temporal/dynamicconfig/development.yaml

things are all now back and running so creating an empty file appears to resolve this.

👍 1

山中康寛

07/19/2023, 12:03 PM

Thank you. You are all my life savers!

3 Views

Open in Slack

Previous Next