We seem to be running into issues where our Airbyte instance Airbyte #ask-ai

We seem to be running into issues where our Airbyt...

King Ho

05/15/2023, 11:05 AM

We seem to be running into issues where our Airbyte instances deployed using docker on VMs hosted on GCP are becoming partially non-responsive. The web interface runs, but clicking on a job in a connection has the progress wheel spin endlessly and result in a 502 error on the request (get_debug_info). After restarting the docker container, its all ok, but this is not sustainable. It almost feels like there is a caching error or problem

kapa.ai

05/15/2023, 11:05 AM

A message from kapa.ai

kapa.ai

05/15/2023, 11:06 AM

I understand that you're experiencing issues with your Airbyte instances deployed on GCP VMs using Docker. Based on the information extracts provided, I don't have enough details to pinpoint the exact cause of the issue. However, I can suggest a few steps to help you troubleshoot the problem: 1. Check the worker logs for any errors by running the following command:

Copy code

docker logs airbyte-worker | grep ERROR

If this command returns any output, please run:

Copy code

docker logs airbyte-worker > airbyte-worker.log

This command will create a log file in the current directory. You can share this log file on the Airbyte [Slack channel](https://slack.airbyte.com/) in the #issues section for further assistance. 2. If there are no errors in the logs, try restarting the Airbyte server and worker by running:

Copy code

docker restart airbyte-server airbyte-worker

Wait a few moments and try to access the interface again. If the issue persists, I recommend reaching out to the Airbyte community on [Slack](https://slack.airbyte.com/) for further assistance.

Open in Slack

Previous Next