sudo abctl local install insecure cookies chart version=1 1 Airbyte #replication-troubleshooting

sudo abctl local install --insecure-cookies --char...

V S Supritha

12/11/2025, 5:26 AM

sudo abctl local install --insecure-cookies --chart-version=1.1.0 --verbose

Copy code

kubectl get pods -n airbyte-abctl                                                                                
NAME                                                      READY   STATUS      RESTARTS   AGE                                                         
airbyte-abctl-airbyte-bootloader                          0/1     Completed   0          16h                                                         
airbyte-abctl-connector-builder-server-7787844c79-d7ncc   1/1     Running     0          16h                                                         
airbyte-abctl-cron-7fcc6f85d7-9c8pd                       1/1     Running     0          16h                                                         
airbyte-abctl-pod-sweeper-pod-sweeper-86db9f55c5-rlr6l    1/1     Running     0          16h                                                         
airbyte-abctl-server-544d94dcdf-8r7vk                     1/1     Running     0          16h                                                         
airbyte-abctl-temporal-5fd44f968f-fdmnm                   1/1     Running     0          16h                                                         
airbyte-abctl-webapp-7b96bc447-n44sk                      1/1     Running     0          16h                                                         
airbyte-abctl-worker-6486bfdccc-nggrx                     1/1     Running     0          16h                                                         
airbyte-abctl-workload-api-server-5884589bd9-76jzl        1/1     Running     0          16h                                                         
airbyte-abctl-workload-launcher-7bcdd8db5f-wxlvn          1/1     Running     0          16h                                                         
airbyte-db-0                                              1/1     Running     0          16h

I am not able to create source in airbyte UI--> throwing HTTP 500 status airbyteserver pod error:

Copy code

2025-12-10 13:05:58 ERROR i.a.s.a.ApiHelper(execute):49 - Unexpected Exception
java.lang.RuntimeException: java.nio.file.NoSuchFileException: /workspace/5a749837-102a-47bc-a8a8-8156a1fd850e/0/logs.log
        at io.airbyte.commons.server.converters.JobConverter.getLogRead(JobConverter.java:285) ~[io.airbyte-airbyte-commons-server-1.1.0.jar:?]
        at io.airbyte.commons.server.converters.JobConverter.getSynchronousJobRead(JobConverter.java:318) ~[io.airbyte-airbyte-commons-server-1.1.0.jar:?]
        at io.airbyte.commons.server.converters.JobConverter.getSynchronousJobRead(JobConverter.java:304) ~[io.airbyte-airbyte-commons-server-1.1.0.jar:?]
        at io.airbyte.commons.server.handlers.SchedulerHandler.reportConnectionStatus(SchedulerHandler.java:736) ~[io.airbyte-airbyte-commons-server-1.1.0.jar:?]
        at io.airbyte.commons.server.handlers.SchedulerHandler.checkSourceConnectionFromSourceCreate(SchedulerHandler.java:257) ~[io.airbyte-airbyte-commons-server-1.1.0.jar:?]
        at io.airbyte.server.apis.SchedulerApiController.lambda$executeSourceCheckConnection$1(SchedulerApiController.java:47) ~[io.airbyte-airbyte-server-1.1.0.jar:?]
        at io.airbyte.server.apis.ApiHelper.execute(ApiHelper.java:28) ~[io.airbyte-airbyte-server-1.1.0.jar:?]
        at io.airbyte.server.apis.SchedulerApiController.executeSourceCheckConnection(SchedulerApiController.java:47) ~[io.airbyte-airbyte-server-1.1.0.jar:?]
        at io.airbyte.server.apis.$SchedulerApiController$Definition$Exec.dispatch(Unknown Source) ~[io.airbyte-airbyte-server-1.1.0.jar:?]
        at io.micronaut.context.AbstractExecutableMethodsDefinition$DispatchedExecutableMethod.invokeUnsafe(AbstractExecutableMethodsDefinition.java:461) ~[micronaut-inject-4.6.5.jar:4.6.5]
        at io.micronaut.context.DefaultBeanContext$BeanContextUnsafeExecutionHandle.invokeUnsafe(DefaultBeanContext.java:4350) ~[micronaut-inject-4.6.5.jar:4.6.5]
        at io.micronaut.web.router.AbstractRouteMatch.execute(AbstractRouteMatch.java:272) ~[micronaut-router-4.6.5.jar:4.6.5]
        at io.micronaut.web.router.DefaultUriRouteMatch.execute(DefaultUriRouteMatch.java:38) ~[micronaut-router-4.6.5.jar:4.6.5]
        at io.micronaut.http.server.RouteExecutor.executeRouteAndConvertBody(RouteExecutor.java:498) ~[micronaut-http-server-4.6.5.jar:4.6.5]
        at io.micronaut.http.server.RouteExecutor.lambda$callRoute$5(RouteExecutor.java:475) ~[micronaut-http-server-4.6.5.jar:4.6.5]
        at io.micronaut.core.execution.ExecutionFlow.lambda$async$1(ExecutionFlow.java:87) ~[micronaut-core-4.6.5.jar:4.6.5]
        at io.micronaut.core.propagation.PropagatedContext.lambda$wrap$3(PropagatedContext.java:211) ~[micronaut-core-4.6.5.jar:4.6.5]
        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: java.nio.file.NoSuchFileException: /workspace/5a749837-102a-47bc-a8a8-8156a1fd850e/0/logs.log
        at java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:92) ~[?:?]
        at java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:106) ~[?:?]
        at java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111) ~[?:?]
        at java.base/sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:261) ~[?:?]
        at java.base/java.nio.file.Files.newByteChannel(Files.java:379) ~[?:?]
        at java.base/java.nio.file.Files.newByteChannel(Files.java:431) ~[?:?]
        at org.apache.commons.io.input.ReversedLinesFileReader.<init>(ReversedLinesFileReader.java:415) ~[commons-io-2.15.1.jar:2.15.1]
        at org.apache.commons.io.input.ReversedLinesFileReader.<init>(ReversedLinesFileReader.java:358) ~[commons-io-2.15.1.jar:2.15.1]
        at org.apache.commons.io.input.ReversedLinesFileReader.<init>(ReversedLinesFileReader.java:305) ~[commons-io-2.15.1.jar:2.15.1]
        at io.airbyte.commons.logging.LocalLogClient.tailCloudLogs(LogClient.kt:502) ~[io.airbyte-airbyte-commons-storage-1.1.0.jar:?]
        at io.airbyte.commons.logging.LogClientManager.getJobLogFile(LogClientManager.kt:37) ~[io.airbyte-airbyte-commons-storage-1.1.0.jar:?]
        at io.airbyte.commons.server.converters.JobConverter.getLogRead(JobConverter.java:283) ~[io.airbyte-airbyte-commons-server-1.1.0.jar:?]

Please help how to fix this

kapa.ai

12/11/2025, 5:27 AM

From the logs, the server is failing when it tries to read the job logs for the “check connection” task of your new source: >

NoSuchFileException: /workspace/<job-id>/0/logs.log

This means the server thinks a synchronous job exists, but the corresponding log file was never written (or has already been deleted). The knowledge sources you provided do not contain any reference to this specific

NoSuchFileException

logs.log

issue, nor any troubleshooting steps for it. They focus on: -

abctl local install

/ Helm patch order issues around

--low-resource-mode

and chart upgrades.[[Failed patch order](https://docs.airbyte.com/platform/deploying-airbyte/troubleshoot-deploy#failed-to-create-patch-order-in-patch-list)] - Problems with local installs on

abctl

0.30.1 (insecure cookies, workload API bearer token, etc.).[[source-file 502](https://github.com/airbytehq/airbyte/issues/65574)] - Dataplane and database cleanup steps for v1.6.0.[[Could not deploy 1.6.0](https://github.com/airbytehq/airbyte/issues/58587)] None of these sources mention a

NoSuchFileException

/workspace/.../logs.log

or a 500 error when creating a source on chart version

1.1.0

, so I cannot provide a documented fix with confidence. Given that limitation, the only actions I can safely suggest (based strictly on the patterns in the docs/issues) are: 1. Re-run installation without changing modes repeatedly Several issues stem from switching options (e.g. toggling

--low-resource-mode

) between installs, which leads to inconsistent Helm patches and deployments.[[Failed patch order](https://docs.airbyte.com/platform/deploying-airbyte/troubleshoot-deploy#failed-to-create-patch-order-in-patch-list)] - Run:

Copy code

bash      abctl local uninstall      sudo abctl local install --insecure-cookies --chart-version=1.1.0 --verbose

- Then immediately try creating the source again and see if behavior changes. 2. Check that worker jobs actually run when you click “Test connection” In other local-install issues, the root problem was that worker jobs never launched properly (e.g. due to auth / workload-api problems), so nothing executed and logs weren’t produced.[[source-file 502](https://github.com/airbytehq/airbyte/issues/65574)] - After clicking “Test connection”, run:

Copy code

bash      kubectl get pods -n airbyte-abctl

and check whether any short‑lived job pods appear and then complete. If no job pods ever start, the logs file truly won’t exist. 3. If you’re on
abctl
v0.30.1 and HTTP / insecure cookies There are multiple open issues with local installs on

abctl v0.30.1

(502s, insecure-cookies behavior, local S3 source creation failing).[[Disable secure cookies](https://github.com/airbytehq/airbyte/issues/66156); [source-file 502](https://github.com/airbytehq/airbyte/issues/65574)] The knowledge sources, however, do not describe a specific workaround for your log‑file error beyond general re‑install and, in one case, patching secrets for the workload API server.[[source-file 502](https://github.com/airbytehq/airbyte/issues/65574)] Because the provided documentation and issues do not address this

logs.log

NoSuchFileException

, I’m unable to give a definitive, documented fix. The next best step, consistent with the docs, would be: - Capture: -

abctl version

kubectl logs -n airbyte-abctl -l <http://app.kubernetes.io/name=worker|app.kubernetes.io/name=worker> --tail=200

- The exact steps to reproduce (connector type, configuration). - Open or update a GitHub issue in

airbytehq/airbyte

with these details so the team can investigate this specific server/worker mismatch, since it’s not covered in the current troubleshooting guides.

2 Views

Open in Slack

Previous Next