xoa updater stalls

xo-xen

Hi all,

thank you for the great work providing XCP-ng and XOA.

I have a XCP-ng installation with an XOA VM running the XOA webinterface.

Some days ago I had a look into the webinterface. The current version is 5.103.1. When I hit the 'Refresh' button nothing happens. I just get the initial message 'Start updating...' and then it hangs for days without progress.

I also tried xoa-updater from ssh console and also xoa-updater ---upgrade. In both cases the command hangs without any output for hours and days.

If I run xoa check it hangs at the last test:

$ xoa check
✔  1/16 - Node version
✔  2/16 - Memory
✔  3/16 - xo-server config syntax
✔  4/16 - Disk space for /
✔  5/16 - Disk space for /var
✔  6/16 - Native SMB support
✔  7/16 - Fetching VM UUID
✔  8/16 - xoa-support user
✔  9/16 - XOA version
✔ 10/16 - /var is writable
✔ 11/16 - Appliance registration
✔ 12/16 - NTP synchronization
✔ 13/16 - npm version
✔ 14/16 - Internet connectivity
✔ 15/16 - local SSH server

I checked the internet connectivity and that seems to be fine in my eyes. No proxy involved - just a firewall that prevents XOA being accessible from the internet, but granting now full access from the XOA VM to the internet (which I would like to restrikt again further once the issue is solved).

I don't have a clue.

Just for a comparison: Im am running a XCP-ng instance in a different network with identical components, that runs all the updates and checks like a charm. It made it to version 5.106.4 without any trouble. Here is, what I would expect in the output of the above described host as well:

15.7.2025, 11:38:31: Start updating...
15.7.2025, 11:38:31: stable channel selected
15.7.2025, 11:38:31: All up to date

So: Is this a common issue? What could be the cause of the xoa-updater to stall this way?

Kind regards
Olaf

Danp

There was a change a while back with the way Node handles timeouts, which affected instances of XOA where both IPv4 and IPv6 were assigned.

Temporarily adding the following entry to /etc/hosts will likely resolve the issue --
185.78.159.93 xen-orchestra.com

xo-xen

Thank you so much for that hint.

Yes, after restarting some xoa service this now works. So cool. You are great. Thank you.