Sticky-session / socket hang up

[giovanniborella]

lately we have been getting errors like this:

| autoconnect.gc2 not removed
| Session started. User: xx Database: xx Has autologin: false NaN
| node:events:497
|       throw er; // Unhandled 'error' event
|       ^
| 
| Error: socket hang up
|     at Socket.socketOnEnd (node:_http_client:524:23)
|     at Socket.emit (node:events:531:35)
|     at endReadableNT (node:internal/streams/readable:1696:12)
|     at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
| Emitted 'error' event on Request instance at:
|     at Request.onerror (node:internal/streams/legacy:63:12)
|     at Request.emit (node:events:519:28)
|     at Request.onRequestError (/root/vidi/node_modules/request/request.js:877:8)
|     at ClientRequest.emit (node:events:519:28)
|     at Socket.socketOnEnd (node:_http_client:524:9)
|     at Socket.emit (node:events:531:35)
|     at endReadableNT (node:internal/streams/readable:1696:12)
|     at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
|   code: 'ECONNRESET'
| }
| 
| Node.js v20.16.0
| node:events:497
|       throw er; // Unhandled 'error' event
|       ^
| 
| Error [ERR_IPC_CHANNEL_CLOSED]: Channel closed
|     at target.send (node:internal/child_process:754:16)
|     at Worker.send (node:internal/cluster/worker:48:10)
|     at Master.balance (/root/vidi/node_modules/sticky-session/lib/sticky/master.js:84:44)
|     at Master.emit (node:events:519:28)
|     at TCP.onconnection (node:net:2223:8)
| Emitted 'error' event on Worker instance at:
|     at ChildProcess.<anonymous> (node:internal/cluster/worker:32:12)
|     at ChildProcess.emit (node:events:519:28)
|     at node:internal/child_process:758:35
|     at process.processTicksAndRejections (node:internal/process/task_queues:77:11) {
|   code: 'ERR_IPC_CHANNEL_CLOSED'
| }
| 
| Node.js v20.16.0
| 2024-11-26 08:53:08,224 WARN exited: vidi (exit status 1; not expected)
| 2024-11-26 08:53:08,224 INFO reaped unknown pid 9087 (exit status 0)
| 2024-11-26 08:53:08,224 INFO reaped unknown pid 9228 (exit status 1)
| 2024-11-26 08:53:08,224 INFO reaped unknown pid 9300 (exit status 0)
| 2024-11-26 08:53:08,224 INFO reaped unknown pid 9371 (exit status 0)
| 2024-11-26 08:53:08,224 INFO reaped unknown pid 9393 (exit status 0)
| 2024-11-26 08:53:08,224 INFO reaped unknown pid 9471 (exit status 0)
| 2024-11-26 08:53:08,225 INFO reaped unknown pid 9608 (exit status 0)
| 2024-11-26 08:53:08,225 INFO reaped unknown pid 9615 (exit status 0)
| 2024-11-26 08:53:09,227 INFO spawned: 'vidi' with pid 9661
| server started on port 3000
| worker: 3
| 2024-11-26 08:53:10,724 INFO success: vidi entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
| worker: 1
| worker: 5
| worker: 8
| worker: 2
| worker: 6
| worker: 4
| worker: 7

that causes node to restart - giving the users a bad gateway-response because node isnt ready - any clue on the cause?