XO SocketError: other side closed
-
Hi,
Do you have anything between the 2 that could explain it? firewall, switch etc.
-
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.
-
Do you have the problem with a regular XOA (vs XO source), because I'd like to rule out an environment problem
-
@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. -
Check on the side of the Node version maybe
-
root@xoa:~# node -v v22.16.0 -
Thanks, to rule out a Node issue, can you try with Node 20?
-
downgraded to version 20.19.2 . Unfortunately no change.
-
Okay let's see if you have the same problem with an XOA in latest then…
-
@olivierlambert I updated the XO from source, it looks good for now.
-
O olivierlambert marked this topic as a question on
-
O olivierlambert has marked this topic as solved on
-
Excellent news! Thanks for keeping us posted
