update failed to start xo-server.

[dsiminiuk]

OS Version: Pre-built VM. Debian 11, kernel 5.10.0-29-amd64 Node.js version: v20.14.0 (updated from 18.x on this update) Yarn version: 1.22.32

Server specs 1 CPU (2 cores). 4GB RAM

Issue

./xo-install.sh --update
[info] Newer version of script available, attempting to self upgrade from 'a4ac7e5' to 'ca43706'
[ok] Self upgrade done
[info] Checking current node.js version
[ok] node.js version is 18, upgrading to 20.x
<snip>
[info] Starting xo-server...
 waiting for port to be open
 waiting for port to be open
 waiting for port to be open
 waiting for port to be open
 waiting for port to be open
 waiting for port to be open
[fail] Update completed, but looks like there was a problem when starting xo-server. Check /opt/XenOrchestraInstallerUpdater/logs/xo-install.log-202406111654 for more details

Installation logfile

From /opt/XenOrchestraInstallerUpdater/logs/xo-install.log-202406111654

Jun 11 16:57:43 xo-ce systemd[4077]: xo-server.service: Failed to locate executable /opt/xo/xo-server/dist/cli.mjs: No such file or directory
Jun 11 16:57:43 xo-ce systemd[4077]: xo-server.service: Failed at step EXEC spawning /opt/xo/xo-server/dist/cli.mjs: No such file or directory
Jun 11 16:57:43 xo-ce systemd[1]: xo-server.service: Main process exited, code=exited, status=203/EXEC
Jun 11 16:57:43 xo-ce systemd[1]: xo-server.service: Failed with result 'exit-code'.

[dsiminiuk]

I resolved it, so this is just for others in case you run into the same thing.

"No such file or directory" tells me I might be running out of disk space. The pre-built VM disk is only 10GB and of course I had to install some things like net-tools for nslookup, etc. So I caused my own issue by using disk space for other things.

I have the xo-install.cfg set to PRESEVE="3" but apparently there wasn't disk space for a 4th build to be ccompleted. I've changed that to PRESERVE="2" and I'll expand the disk later if needed.

Self-inflicted wound.