@kapa.ai i see this in my sync logs 2026-07-09 155409,389 [pool-3-thread-3] INFO i.a.w.i.VersionedAirbyteStreamFactory(internalLog$io_airbyte_airbyte_commons_worker):248 - INFO DefaultDispatcher-worker-8 i.a.c.l.f.ClientSocket(connect):29 Waiting for socket file to be created: /var/run/sockets/airbyte_socket_4.sock what is the error?

The knowledge sources do not explicitly mention this specific log line as an error. Based on what's available, this log message is actually an informational message (

INFO

level), not an error. It indicates that a worker thread is waiting for a Unix socket file (

/var/run/sockets/airbyte_socket_4.sock

) to be created as part of Airbyte's inter-container data channel communication during a replication job. This is a normal part of the sync startup process — the source/destination containers communicate via socket files, and this message simply means the worker is waiting for that socket to become available. [Github Issue] However, if your sync is hanging or failing, here are a few things to check: 1. Too many socket paths (

DATA_CHANNEL_SOCKET_PATHS

): If you're setting

JOB_MAIN_CONTAINER_CPU_LIMIT

using millicores (e.g.,

4000m

), there is a known bug where Airbyte misinterprets the value and creates thousands of socket paths instead of the expected few. This causes containers to crash with

exec /usr/bin/sh: argument list too long

. The workaround is to use whole CPU units (e.g.,

4

instead of

4000m

). [Github Issue] 2. Broken pipe on socket: A

java.io.IOException: Broken pipe

on the source-to-destination socket means the downstream process exited unexpectedly. This is typically a transient error and may resolve on retry. [PR #76895] Recommended next steps: • Check if the sync eventually succeeds or fails. • Look for

Error

,

Exception

, or

Fail

in the full sync logs for more context. • Verify your

JOB_MAIN_CONTAINER_CPU_LIMIT

is set using whole units, not millicores. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai now i see this: 2026-07-12 055259,327 [pool-3-thread-3] INFO i.a.w.i.VersionedAirbyteStreamFactory(internalLog$io_airbyte_airbyte_commons_worker):248 - INFO main i.a.c.l.t.TaskScopeProvider$kill$6(invokeSuspend):69 Waiting for TaskWrapper(io.airbyte.cdk.load.task.implementor.TeardownTask@60897453) to complete [dd.trace 2026-07-12 055313:528 +0000] [OkHttp localhost/...] WARN com.datadog.profiling.uploader.ProfileUploader - Failed to upload profile to localhost/profiling/v1/input java.net.ConnectException: Failed to connect to localhost/127.0.0.1:8126 (Will not log warnings for 5 minutes)

The knowledge sources do not contain enough information to give a definitive explanation of your specific situation, but I can offer the following based on what is available: 1. The

TeardownTask

waiting message This line:

Waiting for TaskWrapper(io.airbyte.cdk.load.task.implementor.TeardownTask@60897453) to complete

is an

INFO

-level message indicating the sync pipeline is in its final cleanup/teardown phase. This is a normal part of sync completion. In the knowledge sources, similar teardown sequences are seen in successful syncs. [Github Issue] 2. The Datadog warning

WARN com.datadog.profiling.uploader.ProfileUploader - Failed to upload profile to http://localhost:8126/profiling/v1/input java.net.ConnectException: Failed to connect to localhost/127.0.0.1:8126

This is a Datadog Java agent warning — it means the Datadog profiling agent inside the container cannot reach a local Datadog agent on port

8126

. This is not an Airbyte error and does not affect your sync. It is a known benign warning seen in other Airbyte deployments as well. [OOM discussion] In summary: • Neither of these messages indicates a sync failure on their own. • If your sync is still hanging or failing, look for

ERROR

,

Exception

, or

OutOfMemoryError

entries in the logs for the real root cause. • If the

TeardownTask

never completes, that would be worth investigating further by checking if the destination connector is stuck. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

@kapa.ai now i get this 2026-07-12 091432,514 [io-executor-thread-6] ERROR i.a.s.a.ApiHelper(execute):47 - Unexpected Exception io.airbyte.commons.server.errors.IdNotFoundKnownException: Could not find attempt stats for job_id: 553 and attempt no: 0 at io.airbyte.commons.server.handlers.AttemptHandler.getAttemptCombinedStats(AttemptHandler.kt:251) at io.airbyte.server.apis.controllers.AttemptApiController.getAttemptCombinedStats$lambda$2(AttemptApiController.kt:66) at io.airbyte.server.apis.ApiHelper.execute(ApiHelper.kt:32) at io.airbyte.server.apis.controllers.AttemptApiController.getAttemptCombinedStats(AttemptApiController.kt:65) at io.airbyte.server.apis.controllers.$AttemptApiController$Definition$Exec.dispatch(Unknown Source) at io.micronaut.context.AbstractExecutableMethodsDefinition$DispatchedExecutableMethod.invokeUnsafe(AbstractExecutableMethodsDefinition.java:461) at io.micronaut.context.DefaultBeanContext$BeanContextUnsafeExecutionHandle.invokeUnsafe(DefaultBeanContext.java:4438) at io.micronaut.web.router.AbstractRouteMatch.execute(AbstractRouteMatch.java:272) at io.micronaut.web.router.DefaultUriRouteMatch.execute(DefaultUriRouteMatch.java:38) at io.micronaut.http.server.RouteExecutor.executeRouteAndConvertBody(RouteExecutor.java:465) at io.micronaut.http.server.RouteExecutor.lambda$callRoute$5(RouteExecutor.java:442) at io.micronaut.core.execution.ExecutionFlow.lambda$async$0(ExecutionFlow.java:92) at io.micronaut.core.propagation.PropagatedContext.lambda$wrap$3(PropagatedContext.java:232) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) at java.base/java.lang.Thread.run(Thread.java:1583) 2026-07-12 091432,518 [io-executor-thread-6] ERROR i.a.c.s.e.h.IdNotFoundExceptionHandler(handle):33 - Not found exception class NotFoundKnownExceptionInfo { id: null message: Id not found: Could not find attempt stats for job_id: 553 and attempt no: 0 exceptionClassName: io.airbyte.commons.server.errors.IdNotFoundKnownException exceptionStack: [io.airbyte.commons.server.errors.IdNotFoundKnownException: Id not found: Could not find attempt stats for job_id: 553 and attempt no: 0, at io.airbyte.commons.server.errors.handlers.IdNotFoundExceptionHandler.handle(IdNotFoundExceptionHandler.kt:32), at io.airbyte.commons.server.errors.handlers.IdNotFoundExceptionHandler.handle(IdNotFoundExceptionHandler.kt:24), at io.micronaut.http.server.RequestLifecycle.lambda$handlerExceptionHandler$10(RequestLifecycle.java:314), at io.micronaut.http.server.RequestLifecycle.handlerExceptionHandler(RequestLifecycle.java:326), at io.micronaut.http.server.RequestLifecycle.onErrorNoFilter(RequestLifecycle.java:253), at io.micronaut.http.server.RequestLifecycle.lambda$onErrorNoFilter$2(RequestLifecycle.java:215), at io.micronaut.core.execution.ImperativeExecutionFlowImpl.onErrorResume(ImperativeExecutionFlowImpl.java:112), at io.micronaut.core.execution.DelayedExecutionFlowImpl$OnErrorResume.apply(DelayedExecutionFlowImpl.java:393), at io.micronaut.core.execution.DelayedExecutionFlowImpl.work(DelayedExecutionFlowImpl.java:58), at io.micronaut.core.execution.DelayedExecutionFlowImpl.completeLazy(DelayedExecutionFlowImpl.java:80), at io.micronaut.core.execution.DelayedExecutionFlowImpl.completeExceptionally(DelayedExecutionFlowImpl.java:104), at io.micronaut.core.execution.DelayedExecutionFlow.complete(DelayedExecutionFlow.java:100), at io.micronaut.core.execution.ImperativeExecutionFlowImpl.onComplete(ImperativeExecutionFlowImpl.java:132), at io.micronaut.core.execution.ExecutionFlow.lambda$async$0(ExecutionFlow.java:92), at io.micronaut.core.propagation.PropagatedContext.lambda$wrap$3(PropagatedContext.java:232), at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144), at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642), at java.base/java.lang.Thread.run(Thread.java:1583), Caused by: io.airbyte.commons.server.errors.IdNotFoundKnownException: Could not find attempt stats for job_id: 553 and attempt no: 0, at io.airbyte.commons.server.handlers.AttemptHandler.getAttemptCombinedStats(AttemptHandler.kt:251), at io.airbyte.server.apis.controllers.AttemptApiController.getAttemptCombinedStats$lambda$2(AttemptApiController.kt:66), at io.airbyte.server.apis.ApiHelper.execute(ApiHelper.kt:32), at io.airbyte.server.apis.controllers.AttemptApiController.getAttemptCombinedStats(AttemptApiController.kt:65), at io.airbyte.server.apis.controllers.$AttemptApiController$Definition$Exec.dispatch(Unknown Source), at io.micronaut.context.AbstractExecutableMethodsDefinition$DispatchedExecutableMethod.invokeUnsafe(AbstractExecutableMethodsDefinition.java:461), at io.micronaut.context.DefaultBeanContext$BeanContextUnsafeExecutionHandle.invokeUnsafe(DefaultBeanContext.java:4438), at io.micronaut.web.router.AbstractRouteMatch.execute(AbstractRouteMatch.java:272), at io.micronaut.web.router.DefaultUriRouteMatch.execute(DefaultUriRouteMatch.java:38), at io.micronaut.http.server.RouteExecutor.executeRouteAndConvertBody(RouteExecutor.java:465), at io.micronaut.http.server.RouteExecutor.lambda$callRoute$5(RouteExecutor.java:442), ... 5 more] rootCauseExceptionClassName: java.lang.Class rootCauseExceptionStack: [io.airbyte.commons.server.errors.IdNotFoundKnownException: Could not find attempt stats for job_id: 553 and attempt no: 0, at io.airbyte.commons.server.handlers.AttemptHandler.getAttemptCombinedStats(AttemptHandler.kt:251), at io.airbyte.server.apis.controllers.AttemptApiController.getAttemptCombinedStats$lambda$2(AttemptApiController.kt:66), at io.airbyte.server.apis.ApiHelper.execute(ApiHelper.kt:32), at io.airbyte.server.apis.controllers.AttemptApiController.getAttemptCombinedStats(AttemptApiController.kt:65), at io.airbyte.server.apis.controllers.$AttemptApiController$Definition$Exec.dispatch(Unknown Source), at io.micronaut.context.AbstractExecutableMethodsDefinition$DispatchedExecutableMethod.invokeUnsafe(AbstractExecutableMethodsDefinition.java:461), at io.micronaut.context.DefaultBeanContext$BeanContextUnsafeExecutionHandle.invokeUnsafe(DefaultBeanContext.java:4438), at io.micronaut.web.router.AbstractRouteMatch.execute(AbstractRouteMatch.java:272), at io.micronaut.web.router.DefaultUriRouteMatch.execute(DefaultUriRouteMatch.java:38), at io.micronaut.http.server.RouteExecutor.executeRouteAndConvertBody(RouteExecutor.java:465), at io.micronaut.http.server.RouteExecutor.lambda$callRoute$5(RouteExecutor.java:442), at io.micronaut.core.execution.ExecutionFlow.lambda$async$0(ExecutionFlow.java:92), at io.micronaut.core.propagation.PropagatedContext.lambda$wrap$3(PropagatedContext.java:232), at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144), at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642), at java.base/java.lang.Thread.run(Thread.java:1583)] }

This error is related to the "Missing stats" issue seen across multiple Airbyte deployments. The error:

Could not find attempt stats for job_id: 553 and attempt no: 0

means Airbyte's server is querying for sync statistics (records emitted, bytes committed, etc.) for a job attempt, but cannot find them in the database — specifically in the

attempt_sync_stats

table that backs the

attempts

records. [Forum Post] [Forum Post] This is consistent with the

WARN Missing stats for job X attempt Y

messages seen in other deployments. [Github Issue] What this means: • The attempt record exists in the

attempts

table (job 553, attempt 0), but no corresponding stats row was written for it. • This typically happens when a sync attempt starts but the replication worker never successfully writes stats back to the database — often because the job was cancelled, timed out, or the worker pod was killed before stats could be persisted. What to check: 1. Did the sync actually complete? Check the job status in the Airbyte UI for job 553. If it shows as cancelled or failed, the missing stats are expected. 2. Is the sync hanging? Based on your earlier logs (

TeardownTask

waiting, socket waiting), the worker may be getting stuck before it can write stats. 3. Check worker pod logs for the replication pod associated with job 553 for any OOM kills, crashes, or timeout errors. 4. This is generally not the root cause — it is a symptom. The underlying issue is likely why the worker is not completing normally. The knowledge sources do not provide a definitive fix for this specific error, so I'd recommend opening a support ticket or GitHub issue with your full worker logs if the syncs are consistently failing. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.