@olivierlambert That worked! I now have templates available.
@planedrop and @karlisi what I ended up doing was enabling outbound access from the Management network to two things:
So long as these resources stay secure, I can now run updates against them. No other outbound access is enabled, and inbound continues to be completely blocked.
My apologies @Danp , I had misunderstood the comments on the other commands in that KB article.
Good news, things are working, but it didn't seem like they would be.
xoa run npm i -g --unsafe-perm https://xen-orchestra.com/xoa-updater.tgz Seemed to work. I was then able to run systemctl restart xoa-updater and xoa-updater --upgrade.
After the upgrade command, this is the feedback:
xoa:xoa$ xoa-updater --upgrade
stable channel selected
Downloading packages...
xen-orchestra 5.95.2 . ok ✔
xo-server-telemetry 0.5.0 ...................................... ok ✔
xen-orchestra-web 0.0.3 ................................................... ok ✔
xo-server-xoa 0.29.0 .................................................................................................................. ok ✔
xo-web-free 5.147.0 ................................................................................................................................................................................................................................................................................................................................................................................................................................. ok ✔
xoa-cli 0.38.2 ...................................................................................................................................................................................................................... ok ✔
xen-orchestra-upload-ova 0.1.6 ........................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................ ok ✔
xo-server 5.145.0 ......................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................... ok ✔
Following packages will be removed:
xoa-updater 0.50.0
Removing packages...
Saving current updater version in /usr/local/lib/node_modules/xoa-updater-previous ...ok ✔
xoa-updater ✔
New versions available:
node 18.20.2 (18.19.1 installed)
npm 10.5.0 (10.2.4 installed)
Downloading packages...
node 18.20.2 ...... ok ✔
npm 10.5.0 .................................................................................................................................................................. ok ✔
Installing packages...
Upgrading Node/npm failed, re-installing old packages Command failed with exit code 1: npm i -g --unsafe-perm --quiet /tmp/xoa-updater/node-18.20.2.tgz
npm ERR! code 1
npm ERR! path /usr/local/lib/node_modules/node
npm ERR! command failed
npm ERR! command sh -c ./installer
npm ERR! installing : node-v18.20.2
npm ERR! curl: (28) Failed to connect to nodejs.org port 443 after 261014 ms: Couldn't connect to server
npm ERR!
npm ERR! Error: download preflight failed for '18.20.2' (https://nodejs.org/dist/v18.20.2/node-v18.20.2-linux-x64.tar.xz)
npm ERR! A complete log of this run can be found in: /tmp/.npm/_logs/2024-09-01T16_42_27_685Z-debug-0.log
New packages available:
xoa-updater 0.50.0
Downloading packages...
Installing packages...
xoa-updater ✔
xoa-updater ✔
✖ {
message: 'Command failed with exit code 1: npm i -g --unsafe-perm --quiet /tmp/xoa-updater/node-18.20.2.tgz\n' +
'npm ERR! code 1\n' +
'npm ERR! path /usr/local/lib/node_modules/node\n' +
'npm ERR! command failed\n' +
'npm ERR! command sh -c ./installer\n' +
'npm ERR! installing : node-v18.20.2\n' +
"npm ERR! curl: (28) Failed to connect to nodejs.org port 443 after 261014 ms: Couldn't connect to server\n" +
'npm ERR! \n' +
"npm ERR! Error: download preflight failed for '18.20.2' (https://nodejs.org/dist/v18.20.2/node-v18.20.2-linux-x64.tar.xz)\n" +
'\n' +
'npm ERR! A complete log of this run can be found in: /tmp/.npm/_logs/2024-09-01T16_42_27_685Z-debug-0.log'
}
At this point I thought there was a failure - but then I was able to run systemctl restart xo-server.service and access both the current web UI and the v6 UI.
I'm interested in trying the newer v6 features, so I just changed from the stable channel to latest using the web UI and ran upgrade - but it gave me an error:
9/1/2024, 1:02:48 PM: New versions available:
9/1/2024, 1:02:48 PM: xoa-updater 0.50.1 (0.50.0 installed)
9/1/2024, 1:02:48 PM: Downloading packages...
9/1/2024, 1:02:49 PM: xoa-updater 0.50.1 ....................................................................................................................................................................................... ok ✔
9/1/2024, 1:02:49 PM: Installing packages...
9/1/2024, 1:03:02 PM: Saving current updater version in /usr/local/lib/node_modules/xoa-updater-previous ...ok ✔
9/1/2024, 1:03:03 PM: xoa-updater ✔
9/1/2024, 1:03:14 PM: xoa-updater ✔
9/1/2024, 1:03:14 PM: Lost connection with xoa-updater
9/1/2024, 1:03:14 PM: xoa-updater could not be reached
Using ssh I went back to the command line and ran xoa-updater --upgrade again and this time it is proceeding forward.
And now it all works! Very weird. I think I'm in good shape now.
@Danp said in Ran XOA updater, got 'CANNOT GET /', web UI has stopped working.:
@waveguide I've performed the update via the web interface and the CLI without issues. However, you can use this KB article to correct the missing
xoaandxoa-updater.
Awesome, we're making progress.
I ran npm i -g --unsafe-perm https://xen-orchestra.com/xoa-cli.tgz and xoa is now working, so I was able to run xoa check.
✔ 1/16 - Node version
✔ 2/16 - Memory
✖ 3/16 - XOA status: Error: spawn xoa-updater ENOENT
at ChildProcess._handle.onexit (node:internal/child_process:284:19)
at onErrorNT (node:internal/child_process:477:16)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
errno: -2,
code: 'ENOENT',
syscall: 'spawn xoa-updater',
path: 'xoa-updater',
spawnargs: []
}
✔ 4/16 - xo-server config syntax
✔ 5/16 - Disk space for /
✔ 6/16 - Disk space for /var
✔ 7/16 - Native SMB support
✔ 8/16 - Fetching VM UUID
✔ 9/16 - xoa-support user
✖ 10/16 - NTP synchronization: no
✔ 11/16 - XOA version
✔ 12/16 - /var is writable
✔ 13/16 - Appliance registration
✔ 14/16 - local SSH server
✔ 15/16 - npm version
✔ 16/16 - Internet connectivity
So some sort of issue now with xoa-updater. Running systemctl restart xoa-updater has no effect. I checked the status for both xoa-updater and xo-server.service and both still have 203 errors. xoa-updater still returns command not found.
So I have the xoa-cli working, but nothing else yet.
I could try to deploy and update XOA a third time, but I'm not really clear on what to do differently. If there is something wrong with my infrastructure or setup that is letting a failure occur, it would help to be able to check relevant logs and see where that failure happened.
EDIT: I tried npm install and got
npm ERR! code ENOENT
npm ERR! syscall open
npm ERR! path /home/xoa/package.json
npm ERR! errno -2
npm ERR! enoent ENOENT: no such file or directory, open '/home/xoa/package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent
npm ERR! A complete log of this run can be found in: /root/.npm/_logs/2024-09-01T01_05_37_135Z-debug-0.log
[21:05 31] xoa:xoa$ cat /root/.npm/_logs/2024-09-01T01_05_37_135Z-debug-0.log
I checked /home/xoa and I have a package-lock.json but no package.json.
Is this the package.json I should have?
https://github.com/vatesfr/xen-orchestra/blob/master/package.json
@Danp I ran the update utility from the XOA web UI and didn't touch anything, so I am assuming there wasn't an interruption.
Do I need to know what folder xoa-updater is in? Because this is the result.
ssh xoa@MYIPADDRESS
xoa@MYIPADDRESS's password:
Linux xoa 6.1.0-18-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.76-1 (2024-02-01) x86_64
__ __ ____ _ _
\ \ / / / __ \ | | | |
\ V / ___ _ __ | | | |_ __ ___| |__ ___ ___| |_ _ __ __ _
> < / _ \ '_ \ | | | | '__/ __| '_ \ / _ \/ __| __| '__/ _` |
/ . \ __/ | | | | |__| | | | (__| | | | __/\__ \ |_| | | (_| |
/_/ \_\___|_| |_| \____/|_| \___|_| |_|\___||___/\__|_| \__,_|
Welcome to XOA Unified Edition, with Pro Support.
* Restart XO: sudo systemctl restart xo-server.service
* Display status: sudo systemctl status xo-server.service
* Display logs: sudo journalctl -u xo-server.service
* Register your XOA: sudo xoa-updater --register
* Update your XOA: sudo xoa-updater --upgrade
OFFICIAL XOA DOCUMENTATION HERE: https://xen-orchestra.com/docs/xoa.html
Support available at https://xen-orchestra.com/#!/member/support
In case of issues, use `xoa check` for a quick health check.
Build number: 24.04.01
Based on Debian GNU/Linux 12 (Stable) 64bits in PVHVM mode
Last login: Fri Aug 30 22:16:55 2024
[19:08 31] xoa@xoa:~$ sudo xoa-updater --upgrade
[sudo] password for xoa:
sudo: xoa-updater: command not found
[19:11 31] xoa@xoa:~$
Per the guidance I also tried xoa check and again got command not found.
Just today, I deployed XOA using the Vates online tools which setup a VM on my XCP-ng host. The XOA version date was I believe form April 2024. I want to test the v6 UI so I registered XOA and ran the updater which seemed to work for a while, and then appeared to pause.
After that point, if I tried to reach any page on XOA I would get 'CANNOT GET /'. I restarted the VM and now I'm unable to load any page at all.
I was able to access the console for the XOA. If I run systemctl status xo-sever.service I get the following:
x xo-server.service - XO Server
Loaded: loaded (/etc/systemd/system/xo-server.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since (date)
Duration: 4ms
Process: 1135 ExecStart=/usr/local/bin/xo-server (code-exited, status=203/EXEC)
Main PID: 1135 (code=exited, status=203/EXEC)
CPU: 735us
Date xoa systemd[1]: xo-server.service: Scheduled restart job, restart counter is at 5.
Date xoa systemd[1]: Stopped xo-server.service - XO Service.
Date xoa systemd[1]: xo-server.service: Start request repeated too quickly.
Date xoa systemd[1]: xo-server.service: Failed with result 'exit-code'.
Date xoa systemd[1]: Failed to start xo-server.service - XO Server.
I tried deleting this VM, redeployed, and ran the updater again. Exact same issue. Update appears to pause - this time I noticed it seemed to happen around "installing packages" which was right after updating node and npm.
I found this other post here with a similar issue from 5 years ago, but I don't understand the fix suggested or if that would apply.
: https://xcp-ng.org/forum/topic/1472/cannot-get-error-after-update
This feels like a bug or error if the XOA that's available cannot run the updater without breaking the web UI.
If it helps at all, the node version is now v18.19.1 and the npm version is 10.2.4.
In my homelab I currently am running vSphere ESXi 6.7 on a Dell PowerEdge R710 with an Intel Xeon E5649 CPU. I have a guest VM that is running Windows 11 that I am working on migrating to XCP-ng using Xen Orchestra's import tool. The new server running XCP-ng is also a PowerEdge, but it runs a Xeon X5650.
I have installed "XenServer VM Tools for Windows 9.3.2" located here, and made sure the NIC in the VM was an Intel E1000.
I am successfully able to import the VM into XCP-ng and run it using the V2V capability. I've confirmed that the NIC in Xen Orchestra is configured as an Intel E1000, and that the MAC Address for the NIC is the same as described in the XCP-ng docs.
When I start the VM, Windows is no longer activated. I understand that the CPU has changed, but I thought that changing "one piece of hardware" was okay.
Is there anything else I can do that will preserve the activation when migrating the VM over? This isn't the only Windows VM I have with a license and it would be convenient to not have to reactivate each.
@olivierlambert That worked! I now have templates available.
@planedrop and @karlisi what I ended up doing was enabling outbound access from the Management network to two things:
So long as these resources stay secure, I can now run updates against them. No other outbound access is enabled, and inbound continues to be completely blocked.
@olivierlambert Maybe my issue with the VM templates isn't a network problem like I thought. Here's what I'm running into.
I built XO from source following guides from Lawrence Systems. If I navigate to Home \ VMs, select the "+New VM" button and then select my pool, I get the screen for adding a new VM.
When I go to select a Template, at least initially there were no templates on the list, it was empty. No choices. Without a template, I couldn't successfully add a network interface, couldn't add a disk, and I could not fill out the criteria that would enable the "Create" button. So I could not create new VMs.
I ended up building a VM on ESXi, importing that VM using XO, and then I converted that VM into a template. Now I have a single template that I can use to create new VMs.
I assumed that the templates list being empty was because I didn't provide XO internet access. Maybe that's not the case? Is that a limitation of building XO from source as opposed to using the XOA?
@planedrop I'm using pfSense as the firewall and router for all the networks and have been using pihole instead of pfBlocker. I could provide the management network or just XO access to pihole DNS and configure pfSense to allow outbound access from the management network to the Internet.
@olivierlambert when suggesting to give XO access, do you mean permitting the instance of XO on the Management network to reach the internet (firewall adjustment for this host)? Or adding another IP for XO on the Production network so it has access to the Internet that way?
@planedrop Is there a list of IP addresses I can restrict to for updating XCP-ng and XO? Alternatively, I can temporarily open all outgoing connections up and monitor the targets...
Hello, I'm new to these forums. I understand that the best answer here might be "you shouldn't give these access to the internet." That's actually what I'm doing right now.
I have a homelab and everything hypervisor or otherwise infrastructure-related is on a VLAN for Management. I use a pfSense firewall to block the entire Management network from accessing the internet. I have a few other VLANs setup as well. XCP-ng is configured with networks for all of these VLANs via trunk ports, although it only has its own IP on the Management VLAN today. These networks are:
I am testing XCP-ng and XO (built from source) and I'm running into challenges here and there doing everything on the Management network, completely offline from the internet.
I was wondering how others deal with this challenge. Do you poke holes in your firewall so the Management network can resolve DNS requests and reach the IP addresses where Vates hosts XCP-ng repos? Do I put XO on the Production network? Keep everything offline and import templates, manually install updates?
This is a homelab, but also "production" for me. So I don't want to accidentally break anything, but at the same time this isn't a business that needs perfect security strategies. I can be flexible.