Error message 'The check connection failed because of an internal error in the scheduler used by Airbyte'

Slack Knowledge Base Q&A Platform Questions
, , , ,
1

Summary

The user is encountering an error where the check connection fails due to an internal error in the scheduler used by Airbyte. The error is related to not finding the image airbyte/source-mysql:3.3.13. Restarting Docker Compose temporarily resolves the issue.


Question

hello everyone , i get message error “The check connection failed because of an internal error in the scheduler used by airbyte.” , when i see the logs
i fount
2024-05-19 10:02:21 e[46mplatforme[0m > Docker volume job log path: /tmp/workspace/9773249e-0a50-49dc-b1b1-1ab3d2c1490a/0/logs.log
2024-05-19 10:02:21 e[46mplatforme[0m > Executing worker wrapper. Airbyte version: 0.55.2
2024-05-19 10:02:21 e[46mplatforme[0m > Attempt 0 to save workflow id for cancellation
2024-05-19 10:02:21 e[46mplatforme[0m > Using default value for environment variable SIDECAR_KUBE_CPU_LIMIT: ‘2.0’
2024-05-19 10:02:21 e[46mplatforme[0m > Using default value for environment variable SOCAT_KUBE_CPU_LIMIT: ‘2.0’
2024-05-19 10:02:21 e[46mplatforme[0m >
2024-05-19 10:02:21 e[46mplatforme[0m > Using default value for environment variable SIDECAR_KUBE_CPU_REQUEST: ‘0.1’
2024-05-19 10:02:21 e[46mplatforme[0m > Using default value for environment variable SOCAT_KUBE_CPU_REQUEST: ‘0.1’
2024-05-19 10:02:21 e[46mplatforme[0m > ----- START CHECK -----
2024-05-19 10:02:21 e[46mplatforme[0m >
2024-05-19 10:02:21 e[46mplatforme[0m > Checking if airbyte/source-mysql:3.3.13 exists…
2024-05-19 10:02:21 e[46mplatforme[0m > airbyte/source-mysql:3.3.13 not found locally. Attempting to pull the image…
2024-05-19 10:02:21 e[46mplatforme[0m > Image does not exist.
2024-05-19 10:02:21 e[46mplatforme[0m > Unexpected error while checking connection:
io.airbyte.workers.exception.WorkerException: Could not find image: airbyte/source-mysql:3.3.13

the connection was already established and worked fine , but i get this error message twice in 2 months
and it solved when i restart docker compose , but i can’t know what the reason behind it


This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.

Join the conversation on Slack

["error-message", "check-connection", "internal-error", "scheduler", "airbyte", "docker-compose", "image-not-found"]