Closed michal-rybinski closed 1 year ago
Seems to be due to this commit: https://github.com/vatesfr/xen-orchestra/commit/72c69d791a7808fc68a85cb26a12ca0e633fbfcf
My tests are failing as well. Need to run couple additional tests before reporting that issue to XO repo. Will look into this asap. For now you can set the BRANCH in xo-install.cfg to d6192a4a7a34921370d048da2f629704da784f7d
and run update to get XO up before fix is in place.
E: issue reported: https://github.com/vatesfr/xen-orchestra/issues/6561
Should be fixed now. Can you confirm
Hi, thanks for the updates and quick actioning. I will be able to test it when I get back from work today in the evening UTC time, will provide the result then.
I was having a similar issue last night where XO Server failed to start after install but it is working for me now.
OS Version: Rocky 8, Ubuntu 22.04 (both LXC on Poxmox if that matters) Node.js version: node -v = v16.18.1 Yarn version: yarn -v = 1.22.19
Server specs 2 vCPUs , 3GB RAM
Issue Installed fine, no problems or errors, but when script tries to start the service it bails out with error pointing at wrong "export" from node uuid library. The same process and the same error on both OS platforms.
Installation logfile Attach complete log as a file. xo-install.log-202211281934.log