Xen Orchestra Node 24 compatibility
-
Hey Vates team and XCP-ng community,
since version 24 just became the new LTS release of Node.js I was wondering:
is Xen Orchestra expected to be fully compatible with this version?
Can XO from sources users safely transition to the new version without sacrificing stability?Node 24 LTS blog announcement: https://nodejs.org/en/blog/release/v24.11.0
In case somebody already tested this or have any insights I would be very grateful.
Thanks in advance!
Best regards
MajorP -
Hi!
- Yes, as usual for each LTS node version, it's expected to become fully compatible
- You are already on the sources, so there's no guarantee of stability. Might be interesting to provide feedback if you have issues, helping everyone and making us fix bugs sooner
-
@MajorP93 I'm running with Node v24.11.0 now (on Debian 11 and 12). There have been some issues with older versions of 24, but to seems fine at this time.
-
After moving from Node 22 to Node 24 on my XO instance I started to see more "Error: ENOMEM: not enough memory, close" for my backup jobs even though my XO VM has 8GB of RAM...
I will revert back to Node 22 for now.
-
said in Xen Orchestra Node 24 compatibility:
After moving from Node 22 to Node 24 on my XO instance I started to see more "Error: ENOMEM: not enough memory, close" for my backup jobs even though my XO VM has 8GB of RAM...
I will revert back to Node 22 for now.
I did some further troubleshooting and was able to pinpoint it down to SMB encryption on Xen Orchestra backup remotes ("seal" CIFS mount flag).
"ENOMEM" errors seem to occur only when I enable previously explained option.
Seems to be related to some buffering that is controlled by Linux kernel CIFS implementation that is failing when SMB encryption is being used.
CIFS operation gets killed due to buffer exhaustion caused by encryption and Xen Orchestra shows "ENOMEM".
Somehow this issue gets more visible when using Node 24 vs Node 22 which is why I thought it was caused by the Node version + XO version combination. I switched Node version at the same time I enabled SMB encryption.
However this seems to be not directly related to Xen Orchestra and more a Node / Linux kernel CIFS implementation thing.
Apparently not a Xen Orchestra bug per se. -
Can you reproduce the issue on XOA? Or it's only on the sources + your current OS?
-
@olivierlambert said in Xen Orchestra Node 24 compatibility:
Can you reproduce the issue on XOA? Or it's only on the sources + your current OS?
We do not have a XOA license (yet) which is why I am currently solely using XO from sources. Therefore currently not able to reproduce on XOA. OS is Debian 13.
