Lates commit breaks install
-
Ping @Team-XO-Backend
-
@olivierlambert we posted at same time...
Saw notation in commit before last -
- name: Setup Node environment uses: actions/setup-node@v4 with: node-version: '20' node-version: '22.3' cache: 'yarn'Edited my config file to use node 22 and install completed and XO is backup and running.
Edit - I need to update my config/script as it did not like me specifying node 22.3. When i just used node 22 it installed v22.22.1
-
Just to confirm the new default node version will be 22.3 not the LTS version 22.22.1? Is it ok to use 22.22.1 or is 22.3 preferred?
Just want to make sure for myself and others that are script is installing the correct supported Node version.
-
@acebmxer Use current Node LTS version... Currently 24.14.0
Or you can use 22.22.1.... use the latest version.22.3 is the oldest version allowed to be supported (don't use one that old).
-
I thought i read somewhere some users having issues using different version of node other then 20. Which is why i defaulted my script to node 20. But if you stating node 24.14.0 is ok to use?
-
@acebmxer I'm running 24.14.0 and it seems to work
-
@acebmxer Yes, 22 or 24 should work correctly. Some early versions of 24 had issues, but not currently. I'm running 24 and it is working.
-
Just yesterday I attempted to update XO-CE from 'aa605639e' to 'fbba05bbd' and received a very similar error to @acebmxer. All subsiquent update attempts have failed, so I remain running on XO on version aa605639e.
I have been using the XenOrchestraInstallerUpdater by Roni Vay since April of 2025 weekly, and it has been very reliable. XO resides on a VM running Ubuntu 24.04.4 LTS \n \l which I apt update/upgrade weekly. There are 3 Intel-based hosts in the cluster (Intel(R) Core(TM) i7-10700 CPU) with 8 VMs and lots of memory.
I am hoping someone will see this and show me a way to fix it.
Thank you.
Below are the very last lines of the xo-install.log:
Updating Xen Orchestra from 'aa605639e' to 'fbba05bbd'
- cd /opt/xo/xo-builds/xen-orchestra-202604171616 && yarn --network-timeout 300000 && yarn --network-timeout 300000 build
yarn install v1.22.22
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
warning bare-fs@4.7.1: The engine "bare" appears to be invalid.
warning bare-os@3.8.7: The engine "bare" appears to be invalid.
error eslint-visitor-keys@5.0.1: The engine "node" is incompatible with this module. Expected version "^20.19.0 || ^22.13.0 || >=24". Got "23.11.0"
error Found incompatible module.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command. - rm -rf /opt/xo/xo-builds/xen-orchestra-202604171616
- cd /opt/xo/xo-builds/xen-orchestra-202604171616 && yarn --network-timeout 300000 && yarn --network-timeout 300000 build
-
Here is the entire log, not very long, but it shows that nodejs and yarn are up to date.
$ cat /home/gsbrown/XenOrchestraInstallerUpdater/logs/xo-install.log-202604171616
- command -v git
/usr/bin/git - cd . && git config --get remote.origin.url
https://github.com/ronivay/XenOrchestraInstallerUpdater.git - cd . && git status --porcelain
?? .yarn/
?? .yarnrc.yml
?? ls
?? nodejsv24-updater-for-24.04-LTS.sh
?? package.json
Running script version 188de7e with config:
PORT="443"
PROXY_PORT="443"
INSTALLDIR="/opt/xo"
SELFUPGRADE=true
CONFIGUPDATE=true
REPOSITORY="https://github.com/vatesfr/xen-orchestra"
BRANCH="master"
PLUGINS="all"
AUTOUPDATE="true"
OS_CHECK="true"
ARCH_CHECK="true"
PRESERVE="3"
PATH_TO_HTTPS_CERT=$INSTALLDIR/xo.crt
PATH_TO_HTTPS_KEY=$INSTALLDIR/xo.key- id -u
0 - uname -m
x86_64 - command -v xe
- grep ^VERSION_ID /etc/os-release | cut -d'=' -f2 | grep -Eo '[0-9]{1,2}' | head -1
24 - grep ^NAME /etc/os-release | cut -d'=' -f2 | sed 's/"//g' | awk '{print $1}'
Ubuntu - grep ^GRUB_DISTRIBUTOR /etc/default/grub | grep 'Xen Orchestra'
- command -v dnf
- command -v apt-get
/usr/bin/apt-get - command -v systemctl
/usr/bin/systemctl - openssl x509 -pubkey -noout -in /opt/xo/xo.crt | openssl md5
MD5(stdin)= ba9cd49e64a4b58a2f1e1a2b60784d60 - openssl pkey -pubout -in /opt/xo/xo.key -outform PEM | openssl md5
MD5(stdin)= ba9cd49e64a4b58a2f1e1a2b60784d60 - df -P -k '/opt' | tail -1 | awk '{print $4}'
5484968 - grep MemTotal /proc/meminfo | awk '{print $2}'
12239640 - node -v 2>/dev/null| grep -Eo '[0-9.]+' | cut -d'.' -f1
23 - curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg -o /etc/apt/trusted.gpg.d/yarn.asc
- curl -sL https://deb.nodesource.com/setup_24.x | bash -
2026-04-17 16:16:35 - Installing pre-requisites
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Hit:1 https://dl.yarnpkg.com/debian stable InRelease
Hit:2 https://deb.nodesource.com/node_24.x nodistro InRelease
Get:3 http://security.ubuntu.com/ubuntu noble-security InRelease [126 kB]
Hit:4 http://us.archive.ubuntu.com/ubuntu noble InRelease
Get:5 http://us.archive.ubuntu.com/ubuntu noble-updates InRelease [126 kB]
Get:6 http://security.ubuntu.com/ubuntu noble-security/main amd64 Components [21.5 kB]
Get:7 http://us.archive.ubuntu.com/ubuntu noble-backports InRelease [126 kB]
Get:8 http://security.ubuntu.com/ubuntu noble-security/restricted amd64 Components [212 B]
Get:9 http://security.ubuntu.com/ubuntu noble-security/universe amd64 Components [74.2 kB]
Get:10 http://security.ubuntu.com/ubuntu noble-security/multiverse amd64 Components [212 B]
Get:11 http://us.archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages [1,901 kB]
Get:12 http://us.archive.ubuntu.com/ubuntu noble-updates/main amd64 Components [177 kB]
Get:13 http://us.archive.ubuntu.com/ubuntu noble-updates/restricted amd64 Components [212 B]
Get:14 http://us.archive.ubuntu.com/ubuntu noble-updates/universe amd64 Packages [1,666 kB]
Get:15 http://us.archive.ubuntu.com/ubuntu noble-updates/universe amd64 Components [386 kB]
Get:16 http://us.archive.ubuntu.com/ubuntu noble-updates/multiverse amd64 Packages [32.5 kB]
Get:17 http://us.archive.ubuntu.com/ubuntu noble-updates/multiverse amd64 Components [940 B]
Get:18 http://us.archive.ubuntu.com/ubuntu noble-backports/main amd64 Components [7,340 B]
Get:19 http://us.archive.ubuntu.com/ubuntu noble-backports/restricted amd64 Components [216 B]
Get:20 http://us.archive.ubuntu.com/ubuntu noble-backports/universe amd64 Components [10.5 kB]
Get:21 http://us.archive.ubuntu.com/ubuntu noble-backports/multiverse amd64 Components [212 B]
Fetched 4,658 kB in 2s (2,921 kB/s)
Reading package lists...
Building dependency tree...
Reading state information...
2 packages can be upgraded. Run 'apt list --upgradable' to see them.WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Reading package lists...
Building dependency tree...
Reading state information...
apt-transport-https is already the newest version (2.8.3).
ca-certificates is already the newest version (20240203).
curl is already the newest version (8.5.0-2ubuntu10.8).
gnupg is already the newest version (2.4.4-2ubuntu17.4).
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Hit:1 https://dl.yarnpkg.com/debian stable InRelease
Hit:2 https://deb.nodesource.com/node_24.x nodistro InRelease
Hit:3 http://us.archive.ubuntu.com/ubuntu noble InRelease
Hit:4 http://us.archive.ubuntu.com/ubuntu noble-updates InRelease
Hit:5 http://security.ubuntu.com/ubuntu noble-security InRelease
Hit:6 http://us.archive.ubuntu.com/ubuntu noble-backports InRelease
Reading package lists...
Building dependency tree...
Reading state information...
2 packages can be upgraded. Run 'apt list --upgradable' to see them.
2026-04-17 16:16:43 - Repository configured successfully.
2026-04-17 16:16:43 - To install Node.js, run: apt install nodejs -y
2026-04-17 16:16:43 - You can use N|solid Runtime as a node.js alternative
2026-04-17 16:16:43 - To install N|solid Runtime, run: apt install nsolid -y- apt-get install -y nodejs
Reading package lists...
Building dependency tree...
Reading state information...
nodejs is already the newest version (24.14.1-1nodesource1).
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. - cd "/opt/xo/xo-src/xen-orchestra" && git remote set-url origin "https://github.com/vatesfr/xen-orchestra" && git fetch --prune && git reset --hard origin/master && git clean -xdff
From https://github.com/vatesfr/xen-orchestra
- [deleted] (none) -> origin/backup-XO-Tasks
- [deleted] (none) -> origin/mra-fix-remote-copy
- [deleted] (none) -> origin/show_backup_merged_size
- [deleted] (none) -> origin/test_replication
6b1a2afc9..fbba05bbd master -> origin/master
- [new branch] doc-xo6-section -> origin/doc-xo6-section
b8b00733e..6c10859a0 encrypt_crendentials -> origin/encrypt_crendentials
48caca99c..b303e7f8c feat/mcp-openapi-bootstrap -> origin/feat/mcp-openapi-bootstrap
- b8eb4af6b...1feb8b695 feat/xo-server-ipmi-sensors -> origin/feat/xo-server-ipmi-sensors (forced update)
- 5d60a1dbb...184117ce1 fix_memory_leak_bis_final -> origin/fix_memory_leak_bis_final (forced update)
- [new branch] hotfix/6.2.2 -> origin/hotfix/6.2.2
- [new branch] mra-acl-backup-jobs -> origin/mra-acl-backup-jobs
dc66c0e29..abdd95198 refactor_backup_clean -> origin/refactor_backup_clean
- 31d488df2...21b79845b web-core/remove-uiObjectLink -> origin/web-core/remove-uiObjectLink (forced update)
- cf6268396...12ccb2e0a xo6/update-system-pages-layout -> origin/xo6/update-system-pages-layout (forced update)
HEAD is now at fbba05bbd feat(backups): use XO Tasks (#9734) - rm -rf "/opt/xo/xo-builds/xen-orchestra-202604171616"
- cp -r "/opt/xo/xo-src/xen-orchestra" "/opt/xo/xo-builds/xen-orchestra-202604171616"
- cd /opt/xo/xo-builds/xen-orchestra-202604171616 && git rev-parse HEAD
fbba05bbde4514c63b2ddd97b5304de1210030e5 - cd /opt/xo/xo-builds/xen-orchestra-202604171616 && git rev-parse --short HEAD
fbba05bbd - cd .
- readlink -e /opt/xo/xo-server
/opt/xo/xo-builds/xen-orchestra-202604111527/packages/xo-server - cd /opt/xo/xo-server && git rev-parse HEAD
aa605639e46568061635695bb61492c0c990ead2 - cd /opt/xo/xo-server && git rev-parse --short HEAD
aa605639e - cd .
Updating Xen Orchestra from 'aa605639e' to 'fbba05bbd' - cd /opt/xo/xo-builds/xen-orchestra-202604171616 && yarn --network-timeout 300000 && yarn --network-timeout 300000 build
yarn install v1.22.22
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
warning bare-fs@4.7.1: The engine "bare" appears to be invalid.
warning bare-os@3.8.7: The engine "bare" appears to be invalid.
error eslint-visitor-keys@5.0.1: The engine "node" is incompatible with this module. Expected version "^20.19.0 || ^22.13.0 || >=24". Got "23.11.0"
error Found incompatible module.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command. - rm -rf /opt/xo/xo-builds/xen-orchestra-202604171616
- command -v git
-
Who's script are you using? I have been making updates to mine and just used it earlier. Currently (3 commits behind)
https://github.com/acebmxer/install_xen_orchestra
I have a note - Node.js version (must be 22 or lower; higher versions are not compatible with Yarn Classic v1). As i did have issues with v24. If someone is able to verify that is the reason for v24 having issues.
I probably need to adjust the warning to remove the word "lower"
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login