xo-server.service fails to start because "The requested module 'uuid' does not provide an export named 'uuid'"

[UntouchedWagons]

Describe the bug

The XO-Server service fails to start because the module uuid does not have an export named uuid

To Reproduce Steps to reproduce the behavior:

1. Run install script in Ubuntu 22.04 server VM
2. Service fails to start

Expected behavior The service to start.

Desktop/Server details (please complete the following information):

• OS: Ubuntu Server 22.04
• Browser: Not Applicable
• Version: 22.04

Confirm XOCE services are running Please run systemctl status xo-server.service and paste the resulting output below.

# systemctl status xo-server.service
× xo-server.service - XO Server
     Loaded: loaded (/lib/systemd/system/xo-server.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Mon 2022-11-28 18:50:23 EST; 5min ago
    Process: 5339 ExecStart=/usr/local/bin/node ./dist/cli.mjs (code=exited, status=1/FAILURE)
   Main PID: 5339 (code=exited, status=1/FAILURE)
        CPU: 1.540s

Nov 28 18:50:23 XenOrchestra systemd[1]: xo-server.service: Scheduled restart job, restart counter is at 5.
Nov 28 18:50:23 XenOrchestra systemd[1]: Stopped XO Server.
Nov 28 18:50:23 XenOrchestra systemd[1]: xo-server.service: Consumed 1.540s CPU time.
Nov 28 18:50:23 XenOrchestra systemd[1]: xo-server.service: Start request repeated too quickly.
Nov 28 18:50:23 XenOrchestra systemd[1]: xo-server.service: Failed with result 'exit-code'.
Nov 28 18:50:23 XenOrchestra systemd[1]: Failed to start XO Server.

Provide the output of journalctl logs Please run journalctl -u xo-server -f -n 50 and paste the resulting output below.

# journalctl -u xo-server -f -n 50
Nov 28 18:50:20 XenOrchestra xo-server[5316]:     at async Promise.all (index 0)
Nov 28 18:50:20 XenOrchestra xo-server[5316]:     at async ESMLoader.import (node:internal/modules/esm/loader:530:24)
Nov 28 18:50:20 XenOrchestra xo-server[5316]:     at async loadESM (node:internal/process/esm_loader:91:5)
Nov 28 18:50:20 XenOrchestra xo-server[5316]:     at async handleMainPromise (node:internal/modules/run_main:65:12)
Nov 28 18:50:20 XenOrchestra xo-server[5316]: Node.js v18.12.1
Nov 28 18:50:20 XenOrchestra systemd[1]: xo-server.service: Main process exited, code=exited, status=1/FAILURE
Nov 28 18:50:20 XenOrchestra systemd[1]: xo-server.service: Failed with result 'exit-code'.
Nov 28 18:50:20 XenOrchestra systemd[1]: xo-server.service: Consumed 1.692s CPU time.
Nov 28 18:50:20 XenOrchestra systemd[1]: xo-server.service: Scheduled restart job, restart counter is at 3.
Nov 28 18:50:20 XenOrchestra systemd[1]: Stopped XO Server.
Nov 28 18:50:20 XenOrchestra systemd[1]: xo-server.service: Consumed 1.692s CPU time.
Nov 28 18:50:20 XenOrchestra systemd[1]: Started XO Server.
Nov 28 18:50:22 XenOrchestra xo-server[5327]: file:///opt/xen-orchestra/packages/xo-server/dist/xo-mixins/migrate-vm.mjs:2
Nov 28 18:50:22 XenOrchestra xo-server[5327]: import { uuid } from 'uuid';
Nov 28 18:50:22 XenOrchestra xo-server[5327]:          ^^^^
Nov 28 18:50:22 XenOrchestra xo-server[5327]: SyntaxError: The requested module 'uuid' does not provide an export named 'uuid'
Nov 28 18:50:22 XenOrchestra xo-server[5327]:     at ModuleJob._instantiate (node:internal/modules/esm/module_job:123:21)
Nov 28 18:50:22 XenOrchestra xo-server[5327]:     at async ModuleJob.run (node:internal/modules/esm/module_job:189:5)
Nov 28 18:50:22 XenOrchestra xo-server[5327]:     at async Promise.all (index 0)
Nov 28 18:50:22 XenOrchestra xo-server[5327]:     at async ESMLoader.import (node:internal/modules/esm/loader:530:24)
Nov 28 18:50:22 XenOrchestra xo-server[5327]:     at async loadESM (node:internal/process/esm_loader:91:5)
Nov 28 18:50:22 XenOrchestra xo-server[5327]:     at async handleMainPromise (node:internal/modules/run_main:65:12)
Nov 28 18:50:22 XenOrchestra xo-server[5327]: Node.js v18.12.1
Nov 28 18:50:22 XenOrchestra systemd[1]: xo-server.service: Main process exited, code=exited, status=1/FAILURE
Nov 28 18:50:22 XenOrchestra systemd[1]: xo-server.service: Failed with result 'exit-code'.
Nov 28 18:50:22 XenOrchestra systemd[1]: xo-server.service: Consumed 1.567s CPU time.
Nov 28 18:50:22 XenOrchestra systemd[1]: xo-server.service: Scheduled restart job, restart counter is at 4.
Nov 28 18:50:22 XenOrchestra systemd[1]: Stopped XO Server.
Nov 28 18:50:22 XenOrchestra systemd[1]: xo-server.service: Consumed 1.567s CPU time.
Nov 28 18:50:22 XenOrchestra systemd[1]: Started XO Server.
Nov 28 18:50:23 XenOrchestra xo-server[5339]: file:///opt/xen-orchestra/packages/xo-server/dist/xo-mixins/migrate-vm.mjs:2
Nov 28 18:50:23 XenOrchestra xo-server[5339]: import { uuid } from 'uuid';
Nov 28 18:50:23 XenOrchestra xo-server[5339]:          ^^^^
Nov 28 18:50:23 XenOrchestra xo-server[5339]: SyntaxError: The requested module 'uuid' does not provide an export named 'uuid'
Nov 28 18:50:23 XenOrchestra xo-server[5339]:     at ModuleJob._instantiate (node:internal/modules/esm/module_job:123:21)
Nov 28 18:50:23 XenOrchestra xo-server[5339]:     at async ModuleJob.run (node:internal/modules/esm/module_job:189:5)
Nov 28 18:50:23 XenOrchestra xo-server[5339]:     at async Promise.all (index 0)
Nov 28 18:50:23 XenOrchestra xo-server[5339]:     at async ESMLoader.import (node:internal/modules/esm/loader:530:24)
Nov 28 18:50:23 XenOrchestra xo-server[5339]:     at async loadESM (node:internal/process/esm_loader:91:5)
Nov 28 18:50:23 XenOrchestra xo-server[5339]:     at async handleMainPromise (node:internal/modules/run_main:65:12)
Nov 28 18:50:23 XenOrchestra xo-server[5339]: Node.js v18.12.1
Nov 28 18:50:23 XenOrchestra systemd[1]: xo-server.service: Main process exited, code=exited, status=1/FAILURE
Nov 28 18:50:23 XenOrchestra systemd[1]: xo-server.service: Failed with result 'exit-code'.
Nov 28 18:50:23 XenOrchestra systemd[1]: xo-server.service: Consumed 1.540s CPU time.
Nov 28 18:50:23 XenOrchestra systemd[1]: xo-server.service: Scheduled restart job, restart counter is at 5.
Nov 28 18:50:23 XenOrchestra systemd[1]: Stopped XO Server.
Nov 28 18:50:23 XenOrchestra systemd[1]: xo-server.service: Consumed 1.540s CPU time.
Nov 28 18:50:23 XenOrchestra systemd[1]: xo-server.service: Start request repeated too quickly.
Nov 28 18:50:23 XenOrchestra systemd[1]: xo-server.service: Failed with result 'exit-code'.
Nov 28 18:50:23 XenOrchestra systemd[1]: Failed to start XO Server.

Provide answers to these questions:

• Is this a fresh install or an upgrade? Fresh

• Version of XOCE server and web interface you're running I have no idea

• What OS is XOCE running on? Ubuntu 22.04

• A link to the ISO you've used as as the server (so we can verify/troubleshoot) https://ubuntu.com/download/server

• What method did you use to install XOCE (xo_install.sh, manual installation, etc) This repo's installer script

• What specific XOCE page you're on, and what specific element you're interacting with to trigger the error Not applicable

• If a stacktrace is provided in the error, include that too. Already done

• Any errors that appear in your browser's error console. Not applicable

• Include what you've done so far in the installation, and if you got any error messages along the way. Installation completed, no known errors

• Indicate whether or not you've manually edited any data directly. Not done

[Danp2]

I believe that this issue has nothing to do with this installation script. It is due to a recent change in the XO source that would fail even when built manually.

[Danp2]

This appears to be resolved by today's commits in the XO repo. Please retry and report back.

[UntouchedWagons]

Yeah it's good now.