Summary
The user is experiencing a sync job failure with a ‘Source process read attempt failed’ error message. They have tried refreshing the connection multiple times but the issue persists.
Question
Hello,
One of our sync jobs suddenly started failing with a not so clear error message. It simply says Source process read attempt failed
.
I have refreshed the connection multiple times, but it always fails on the next sync.
Can someone help me figure out what the problem is?
Attached you’ll finde the attempt logs.
Thank you
Airbyte version: v0.63.13
Source: Postgres - v3.6.22
Destination: Postrges - v2.4.0 (edited)
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
["sync-job-failure", "source-process-read-attempt-failed", "postgres-connector", "airbyte-version"]
The problem seem to be here:
io.airbyte.workers.exception.WorkerException: A stream status (public.GridStatistics) has been detected for a stream not present in the catalog
at io.airbyte.workers.helper.StreamStatusCompletionTracker.track(StreamStatusCompletionTracker.kt:36) ~[io.airbyte-airbyte-commons-worker-0.63.13.jar:?]
at io.airbyte.workers.general.BufferedReplicationWorker.readFromSource(BufferedReplicationWorker.java:361) ~[io.airbyte-airbyte-commons-worker-0.63.13.jar:?]
at io.airbyte.workers.general.BufferedReplicationWorker.lambda$runAsyncWithHeartbeatCheck$3(BufferedReplicationWorker.java:242) ~[io.airbyte-airbyte-commons-worker-0.63.13.jar:?]
at java.base/java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1804) ~[?:?]
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) ~[?:?]
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) ~[?:?]```
Concretely on A stream status (public.GridStatistics) has been detected for a stream not present in the catalog
How could this happen?
I’ve had the same issue a few times over the last week or so and it’s not clear what’s changed. <@U071JQJ0A6T> did you find out what was causing it for you?
My last resort was to installed the latest airbyte version from scratch
And configured everything again
That solved the issue for me