Closed makeitcloudy closed 3 years ago
Hi,
Unfortunately i wasn't able to reproduce this with CentOS or Debian. Did you do any related tasks manually like install packages or edit the default configuration file that ships with the script?
Hi ! thank you for prompt response, the fact is that I've been just updating the version, and firstly it turned out that it requires node.js 14.17 I've been having 14.16, and it just failed within the update. Haven't done the snapshot, so I ended up without the xoa, as the update failed. So indeed tried with manually updating the node, and pointing the os towards the required version, but it did not help.
As XS/xcpn-g is redhat based, I just spin up with regular xoa appliance, new vm centos8stream based, and tried with the script on that brand new distro, reaching the similar result. For some reason it did not upgrade the node.js within the upgrade option of xo-install.sh script, unless I screw up something by my own, which is also possible. (no manual modification of the script)
Hi,
Script will check if the major version of node.js is correct and attempt to upgrade it. If major version is already correct, it will attempt to update through repository using apt/yum. No updates will be found if node.js was originally installed via some other method and not using the script. Manual installation is the only reason i can think of right now for it to not update the minor version. Any node.js upgrade/update action also requires that AUTOUPDATE is set to true in xo-install.cfg.
XCP-ng is based on CentOS. Official Xen Orchestra appliance on the other hand runs on Debian.
I'd suggest removing any manually installed node.js completely and just running the update and let the script handle node.js installation via the method it supports. There's been some cases where installation fails for some that have installed node.js on their own. To be honest i haven't bothered debugging those further as the script should handle it and if one decides to install/update it by themself, they should be able to deal with it also :D
@tansei any updates on this?
This issue has been open for 14 days without activity. It will be closed in 5 days if not updated
OS Version: CentOS 8 Stream / Debian 10 Node.js version: node -v : v14.17.0 Yarn version: yarn -v : 1.22.5
Server specs 2vCPU, 4GB RAM
Issue [root@localhost XenOrchestraInstallerUpdater]# systemctl status xo-server ● xo-server.service - XO Server Loaded: loaded (/etc/systemd/system/xo-server.service; disabled; vendor preset: disabled) Active: failed (Result: exit-code) since Mon 2021-06-14 23:37:27 CEST; 5s ago Process: 43467 ExecStart=/opt/xo/xo-server/dist/cli.mjs (code=exited, status=1/FAILURE) Main PID: 43467 (code=exited, status=1/FAILURE)
Jun 14 23:37:27 localhost.localdomain systemd[1]: xo-server.service: Main process exited, code=exited, status=1/FAILURE Jun 14 23:37:27 localhost.localdomain systemd[1]: xo-server.service: Failed with result 'exit-code'. Jun 14 23:37:27 localhost.localdomain systemd[1]: xo-server.service: Service RestartSec=100ms expired, scheduling restart. Jun 14 23:37:27 localhost.localdomain systemd[1]: xo-server.service: Scheduled restart job, restart counter is at 5. Jun 14 23:37:27 localhost.localdomain systemd[1]: Stopped XO Server. Jun 14 23:37:27 localhost.localdomain systemd[1]: xo-server.service: Start request repeated too quickly. Jun 14 23:37:27 localhost.localdomain systemd[1]: xo-server.service: Failed with result 'exit-code'. Jun 14 23:37:27 localhost.localdomain systemd[1]: Failed to start XO Server.
Installation logfile
Any help would be highly appreciated. Everything was working fine with previous releases, tried with update, as well as with brand new install on a VM from a scratch, and reached similar result.