XO SocketError: other side closed

bogikornel

Hello !

When using a freshly installed xcp-ng 8.3 and source compiled XO, the connection between XO and XCP-ng is always broken.

I have attached the log:

un 03 12:45:24 xoa xo-server[572]: 2025-06-03T10:45:24.140Z xo:main INFO + Console proxy (bogi.kornel - ::ffff:172.31.60.45)
Jun 03 12:46:00 xoa xo-server[572]: _watchEvents SocketError: other side closed
Jun 03 12:46:00 xoa xo-server[572]:     at TLSSocket.<anonymous> (/opt/xo5/xo-builds/xen-orchestra-202506021322/node_modules/undici/lib/dispatcher/client-h1.js:701:24)
Jun 03 12:46:00 xoa xo-server[572]:     at TLSSocket.emit (node:events:530:35)
Jun 03 12:46:00 xoa xo-server[572]:     at TLSSocket.patchedEmit [as emit] (/opt/xo5/xo-builds/xen-orchestra-202506021322/@xen-orchestra/log/configure.js:52:17)
Jun 03 12:46:00 xoa xo-server[572]:     at endReadableNT (node:internal/streams/readable:1698:12)
Jun 03 12:46:00 xoa xo-server[572]:     at processTicksAndRejections (node:internal/process/task_queues:90:21) {
Jun 03 12:46:00 xoa xo-server[572]:   code: 'UND_ERR_SOCKET',
Jun 03 12:46:00 xoa xo-server[572]:   socket: {
Jun 03 12:46:00 xoa xo-server[572]:     localAddress: '172.31.30.4',
Jun 03 12:46:00 xoa xo-server[572]:     localPort: 58826,
Jun 03 12:46:00 xoa xo-server[572]:     remoteAddress: '172.31.30.3',
Jun 03 12:46:00 xoa xo-server[572]:     remotePort: 443,
Jun 03 12:46:00 xoa xo-server[572]:     remoteFamily: 'IPv4',
Jun 03 12:46:00 xoa xo-server[572]:     timeout: undefined,
Jun 03 12:46:00 xoa xo-server[572]:     bytesWritten: 49957,
Jun 03 12:46:00 xoa xo-server[572]:     bytesRead: 1673042
Jun 03 12:46:00 xoa xo-server[572]:   },
Jun 03 12:46:00 xoa xo-server[572]:   call: {
Jun 03 12:46:00 xoa xo-server[572]:     duration: 13,
Jun 03 12:46:00 xoa xo-server[572]:     method: 'event.from',
Jun 03 12:46:00 xoa xo-server[572]:     params: [
Jun 03 12:46:00 xoa xo-server[572]:       '* session id *',
Jun 03 12:46:00 xoa xo-server[572]:       [Array],
Jun 03 12:46:00 xoa xo-server[572]:       '00000000000001936776,00000000000001936233',
Jun 03 12:46:00 xoa xo-server[572]:       60.1
Jun 03 12:46:00 xoa xo-server[572]:     ]
Jun 03 12:46:00 xoa xo-server[572]:   }
Jun 03 12:46:00 xoa xo-server[572]: }
Jun 03 12:46:00 xoa xo-server[572]: 2025-06-03T10:46:00.438Z xo:main INFO - Console proxy (bogi.kornel - ::ffff:172.31.60.45)

olivierlambert

Hi,

Do you have anything between the 2 that could explain it? firewall, switch etc.

bogikornel

@olivierlambert

None. The XCP-ng host also runs XO. Same VLAN, same IP range (XCP-ng 172.31.30.3, XO: 172.31.30.4). So the packet doesn't even need to go out to a switch.

The XO has an old Xenserver 7.0 (I'm migrating from it), it runs stable, its IP is 172.31.30.5.

olivierlambert

Do you have the problem with a regular XOA (vs XO source), because I'd like to rule out an environment problem

bogikornel

@olivierlambert
I will check with XOA. For now, it seems to me to be a local problem, because I use quite a few XOs and I haven't had this problem yet. If I find something I will report it.

olivierlambert

Check on the side of the Node version maybe

bogikornel

@olivierlambert

root@xoa:~# node -v
v22.16.0

olivierlambert

Thanks, to rule out a Node issue, can you try with Node 20?

bogikornel

@olivierlambert

downgraded to version 20.19.2 . Unfortunately no change.

olivierlambert

Okay let's see if you have the same problem with an XOA in latest then…

bogikornel

@olivierlambert I updated the XO from source, it looks good for now.

olivierlambert

Excellent news! Thanks for keeping us posted