Jean-Charles Touzalin
10/23/2023, 8:25 AMairbyte-worker-container pop twice this weekend (for the 1st time):
java.net.SocketException: Socket closed
at java.base/sun.nio.ch.NioSocketImpl.endAccept(NioSocketImpl.java:675)
at java.base/sun.nio.ch.NioSocketImpl.accept(NioSocketImpl.java:748)
at java.base/java.net.ServerSocket.implAccept(ServerSocket.java:690)
at java.base/java.net.ServerSocket.platformImplAccept(ServerSocket.java:655)
at java.base/java.net.ServerSocket.implAccept(ServerSocket.java:631)
at java.base/java.net.ServerSocket.implAccept(ServerSocket.java:588)
at java.base/java.net.ServerSocket.accept(ServerSocket.java:546)
at io.airbyte.workers.process.KubePodProcess.lambda$setupStdOutAndStdErrListeners$12(KubePodProcess.java:677)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:577)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)
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:1589)
There isn't much too debug. Any idea what could cause this?kapa.ai
10/23/2023, 8:26 AMjava.net.SocketException, which typically indicates a networking issue. However, without more context or information, it's hard to determine the exact cause. It could be related to the issues discussed in the forum posts [here](https://discuss.airbyte.io/t/3856) and [here](https://discuss.airbyte.io/t/4077), where users experienced failures with the airbyte-worker container. However, these issues were specific to their setups and may not directly apply to your situation. For more detailed guidance, I recommend checking out the [Airbyte documentation](https://docs.airbyte.com/) or asking for help in the [Airbyte community](https://discuss.airbyte.io/).