Hi everyone, I'm getting a "Sync failed" error wit...
# ask-community-for-troubleshooting
n
Hi everyone, I'm getting a "Sync failed" error with no logs, the only log trace it prints is
Copy code
2023-05-31 14:06:33 - Additional Failure Information: message='io.temporal.serviceclient.CheckedExceptionWrapper: java.util.concurrent.ExecutionException: java.lang.RuntimeException: io.airbyte.workers.exception.WorkerException: Running the launcher replication-orchestrator failed', type='java.lang.RuntimeException', nonRetryable=false
This is for a custom source connector connection, I also reviewed the server logs but there are no logs available for the last 3 days at all. It has been working normally until recently. Could someone help me out with this issue? cc: @Brian Castelli @Harshil Dhariwal @kapa.ai
k
A message from kapa.ai
A message from kapa.ai
Hmm, I don't know enough to give you a confident answer yet. However, I can suggest some general steps to troubleshoot the issue: 1. Make sure you have tested your custom source connector locally using the
spec
,
check
, and
read
commands. This will help you ensure that the connector is working as expected before deploying it to Airbyte. 2. Check the Airbyte version you are using and consider upgrading to the latest version if you haven't already. This can help resolve any issues that may have been fixed in newer releases. 3. Review the information provided in the [Airbyte forum](https://discuss.airbyte.io) and [Slack community](https://airbytehq.slack.com) to see if anyone else has encountered a similar issue and found a solution. If you're still having trouble, consider sharing more information about your custom source connector, such as the code and configuration, so the community can better assist you.
Hmm, I don't know enough to give you a confident answer yet. However, I can suggest some general troubleshooting steps based on the information extracts provided: 1. Make sure your custom source connector is built correctly and passes all the necessary tests. You can refer to this [forum discussion](https://discuss.airbyte.io/t/2248) where a user faced a similar issue and resolved it by fixing the requirements in
setup.py
and updating the Dockerfile. 2. Ensure that your Airbyte instance has access to the internet and can reach the necessary resources, as mentioned in this [Slack conversation](https://airbytehq.slack.com/archives/C021JANJ6TY/p1670252832457049). 3. Check if there are any compatibility issues between your custom connector and the Airbyte version you are using. In some cases, updating Airbyte to the latest version has resolved issues, as seen in this [forum discussion](https://discuss.airbyte.io/t/2604). 4. Review your custom connector's resource allocation, such as memory and CPU, as insufficient resources can cause sync failures. You can refer to this [forum discussion](https://discuss.airbyte.io/t/2291) for an example. If you still face issues, I recommend sharing more details about your custom source connector, Airbyte version, and any relevant logs. Additionally, you can explore the [Airbyte documentation](https://docs.airbyte.com) and [forum](https://discuss.airbyte.io) for more information and support.
b
@Nohelia Merino there are airbyte logs available for the pod that is used for the data transfer and in the minio pod. Have you tried looking at those? The minio logs require you to shell into the pod itself and look under the
/storage
folder.