Hi everyone I have a problem that I would like to ...
# replication-troubleshooting
a
Hi everyone I have a problem that I would like to share with you I’m running the latest version in AWS Kubernetes and I’m getting this error
Copy code
2022-08-25 15:01:15 [32mINFO[m i.a.w.t.TemporalAttemptExecution(lambda$getWorkerThread$2):158 - Completing future exceptionally...
java.lang.RuntimeException: io.airbyte.workers.exception.WorkerException: Running the launcher replication-orchestrator failed
	at io.airbyte.workers.temporal.TemporalUtils.withBackgroundHeartbeat(TemporalUtils.java:341) ~[io.airbyte-airbyte-workers-0.40.2.jar:?]
	at io.airbyte.workers.temporal.sync.LauncherWorker.run(LauncherWorker.java:91) ~[io.airbyte-airbyte-workers-0.40.2.jar:?]
	at io.airbyte.workers.temporal.TemporalAttemptExecution.lambda$getWorkerThread$2(TemporalAttemptExecution.java:155) ~[io.airbyte-airbyte-workers-0.40.2.jar:?]
	at java.lang.Thread.run(Thread.java:1589) [?:?]
Caused by: io.airbyte.workers.exception.WorkerException: Running the launcher replication-orchestrator failed
	at io.airbyte.workers.temporal.sync.LauncherWorker.lambda$run$3(LauncherWorker.java:184) ~[io.airbyte-airbyte-workers-0.40.2.jar:?]
	at io.airbyte.workers.temporal.TemporalUtils.withBackgroundHeartbeat(TemporalUtils.java:336) ~[io.airbyte-airbyte-workers-0.40.2.jar:?]
	... 3 more
Caused by: software.amazon.awssdk.services.s3.model.NoSuchBucketException: The specified bucket does not exist (Service: S3, Status Code: 404, Request ID: 170E9E94F5789BB9, Extended Request ID: null)
	at
logs are written to the bucket I get the error when I try to sync data can anyone help?
e
I have the same issue while trying to move data from mysql to snowflake 😢
I found this that appears to work but for me it doesn't as i am not using minio https://discuss.airbyte.io/t/nosuchbucket-exception-in-s3documentstoreclient/1915/4
a
@Elizabeth Rodriguez I created issue on github You can also describe your problem there or follow
👍 1
e
I found this in an old conversation, it might work
a
But my service account is named correctly
🤔 1
d
did you ever solve this? I'm getting a similar error, and like you I did not change my service account.
k
same here, my service account name is set to airbyte-admin as well but still i get those errors
j
Hi. Wondering if anyone has found a solution for this? I'm using S3 and getting the same error - sync is failing
a
We have just fixed this. If your 'airbyte-worker' pod is also showing
NoSuchBucket
errors, it is likely due to the bucket that is specified in
STATE_STORAGE_MINIO_BUCKET_NAME
not having being created. I dont know why airbyte code cant create the bucket, but we logged into the 'airbyte-minio' UI and manually added the bucket and it started working again.
thanku 1
Update: this isnt surviving pod restart unfortunately.
The bucket disappears
do we have airbyte in prod?
presumably, since it is state it should persist