Hello All,
Anyone seen such error in logs after do...
# replication-troubleshootings
Sheshan
12/15/2022, 1:22 PMHello All,
Anyone seen such error in logs after download is "SUCCEEDED".
Copy code
2022-12-15 13:17:28 WARN i.t.i.w.ActivityWorker$TaskHandlerImpl(logExceptionDuringResultReporting):365 - Failure during reporting of activity result to the server. ActivityId = 572543e4-4b6a-3c21-87d3-f9986f3656c5, ActivityType = JobSuccessWithAttemptNumber, WorkflowId=connection_manager_457b6ad6-4826-4fb1-93c8-d93b8a4687d0, WorkflowType=ConnectionManagerWorkflow, RunId=823444ac-dc24-4e64-8dd5-f0b2fd32ee35
io.grpc.StatusRuntimeException: NOT_FOUND: invalid activityID or activity already timed out or invoking workflow is completed
2022-12-15 13:17:37 WARN i.t.i.a.ActivityTaskExecutors$BaseActivityTaskExecutor(execute):114 - Activity failure. ActivityId=572543e4-4b6a-3c21-87d3-f9986f3656c5, activityType=JobSuccessWithAttemptNumber, attempt=2
java.lang.IllegalStateException: Transitioning Job 14 from JobStatus SUCCEEDED to SUCCEEDED is not allowed. The only valid statuses that an be transitioned to from SUCCEEDED are [] Copy code
{'message': 'A sync is already running for: 836a4c9a-7c07-40dc-b253-1937026c0db9', 'exceptionClassName': 'io.airbyte.server.errors.ValueConflictKnownException', 'exceptionStack': ['io.airbyte.server.errors.ValueConflictKnownException: A sync is already running for: 836a4c9a-7c07-40dc-b253-1937026c0db9',}n
Nataly Merezhuk (Airbyte)
12/15/2022, 6:42 PMHey Shashan, could you give me more details about your deployment - is the on k8s and if so, are you using helm?
s
Sheshan
12/16/2022, 1:19 PMWe are Running airbyte in docker
VERSION=0.40.18
Sheshan
12/16/2022, 1:20 PMI can not trigger the connection but check status api shows it succeeded.
Sheshan
12/16/2022, 1:23 PMError appears after successful notification.
Copy code
2022-12-16 12:59:17 INFO i.a.n.SlackNotificationClient(notify):135 - Successful notification (200): {
"data": {
"text": "Your connection from Redshift to Custom Destination succeeded\nThis was for sync started on Friday, December 16, 2022 at 12:56:59 PM Coordinated Universal Time, running for 29 seconds.\n\nYou can access its logs here: <http://localhost:8000/workspaces/fbe5f287-5a01-4bd1-b61a-7167b083f43f/connections/a38c7ff6-915b-49f5-ae3e-31c46f78542d>\n\nJob ID: 25"
},
"status": {
"code": 200,
"result": "success"
}
}
2022-12-16 12:59:17 WARN i.t.i.w.ActivityWorker$TaskHandlerImpl(logExceptionDuringResultReporting):365 - Failure during reporting of activity result to the server. ActivityId = c2dfb20c-4f4a-316b-9737-666d0dd30606, ActivityType = JobSuccessWithAttemptNumber, WorkflowId=connection_manager_a38c7ff6-915b-49f5-ae3e-31c46f78542d, WorkflowType=ConnectionManagerWorkflow, RunId=97d25f14-9bbe-4e5d-bd1b-deae19d88c56
io.grpc.StatusRuntimeException: NOT_FOUND: invalid activityID or activity already timed out or invoking workflow is completedn
Nataly Merezhuk (Airbyte)
12/16/2022, 2:35 PMThen the first thing I'd advise is to update to the latest version. Let me know when you've done that!
s
Sheshan
12/16/2022, 3:23 PMwill update to VERSION=0.40.25 ( github airbyte main branch). and let you know.
Sheshan
05/04/2023, 11:45 AMFacing same issue again on version 0.42.0
download is succeeded but if clicked on sync again, it is throwing sync already running error.
Can anybody help here.
Sheshan
05/04/2023, 11:46 AMScreenshot 2023-05-04 at 5.13.11 PM.png
7 Views