Actions
Bug #22967
open
"use of closed network connection" and "read: connection reset by peer" log messages from crunch-run while running processes with local dispatcher
Status:
New
Priority:
Normal
Assigned To:
-
Category:
Crunch
Target version:
-
Story points:
-
Description
This is seen after updating the deb packages arvados-controller , crunch-run, and crunch-dispatch-local to version 3.2.0~dev20250603162746-1, with jobs image arvados/jobs:3.2.0.dev20250602210356. The crunch-run log shows repeating entries like these during a process run with the local dispatcher:
2025-06-04T21:36:34.690546319Z tunnel connection 1592: gateway end: writeto tcp 127.0.0.1:56306->127.0.0.1:38653: read tcp 127.0.0.1:56306->127.0.0.1:38653: read: connection reset by peer 2025-06-04T21:36:34.713861655Z tunnel connection 1596: gateway end: writeto tcp 127.0.0.1:56316->127.0.0.1:38653: read tcp 127.0.0.1:56316->127.0.0.1:38653: read: connection reset by peer 2025-06-04T21:36:34.713920910Z tunnel connection 1594: gateway end: writeto tcp 127.0.0.1:56310->127.0.0.1:38653: read tcp 127.0.0.1:56310->127.0.0.1:38653: read: connection reset by peer 2025-06-04T21:37:18.647353998Z tunnel connection 1672: gateway end: writeto tcp 127.0.0.1:34734->127.0.0.1:38653: read tcp 127.0.0.1:34734->127.0.0.1:38653: read: connection reset by peer 2025-06-04T21:37:18.670973876Z tunnel connection 1674: gateway end: writeto tcp 127.0.0.1:34746->127.0.0.1:38653: read tcp 127.0.0.1:34746->127.0.0.1:38653: use of closed network connection 2025-06-04T21:38:37.469907602Z tunnel connection 1806: gateway end: writeto tcp 127.0.0.1:37576->127.0.0.1:38653: read tcp 127.0.0.1:37576->127.0.0.1:38653: read: connection reset by peer 2025-06-04T21:38:37.491914408Z tunnel connection 1808: gateway end: writeto tcp 127.0.0.1:37586->127.0.0.1:38653: read tcp 127.0.0.1:37586->127.0.0.1:38653: use of closed network connection 2025-06-04T21:42:26.215705383Z tunnel connection 2198: gateway end: writeto tcp 127.0.0.1:53638->127.0.0.1:38653: read tcp 127.0.0.1:53638->127.0.0.1:38653: use of closed network connection 2025-06-04T21:42:26.239544313Z tunnel connection 2200: gateway end: writeto tcp 127.0.0.1:53650->127.0.0.1:38653: read tcp 127.0.0.1:53650->127.0.0.1:38653: read: connection reset by peer 2025-06-04T21:42:36.803330586Z tunnel connection 2222: gateway end: writeto tcp 127.0.0.1:33490->127.0.0.1:38653: read tcp 127.0.0.1:33490->127.0.0.1:38653: use of closed network connection
I haven't found any apparent negative effects beside these log entries, though. But, so far as I know, these messages were new. Possibly after the changes in 021849f6?
Updated by Tom Clegg 4 months ago
This looks like log spam, yes.
You can see it in the output of lib/controller tests > ContainerGatewaySuite.TestConnectThroughTunnelWithProxyOK (and others)
time="2025-12-08T18:52:43.949695782-05:00" level=info msg="tunnel connection 2: gateway end: writeto tcp 127.0.0.1:40052->127.0.0.1:44239: read tcp 127.0.0.1:40052->127.0.0.1:44239: use of closed network connection"
Actions