XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    XO5 breaks after defaulting to XO6 (from source)

    Scheduled Pinned Locked Moved Xen Orchestra
    2 Posts 2 Posters 10 Views 2 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • P Offline
      probain
      last edited by

      XO from source
      Problem: XO5 is disconnected and stuck on "Still Loading" (see picture below)
      When trying later commits after XO6 became default. XO5 has broken entirely. And I have not been able to solve this yet.

      Troubleshooting steps are the following:

      git reset --hard <commit hash>
      rm node_modules/ -rf
      yarn
      yarn build
      

      Whilst XO6 is working as expected. There are lots of functions that need XO5. Which is why I haven't noticed this until just now (today).

      Last known good Commit: 4b4c9b91f3722401a7d3eb2eaf549980fd2f3e5b
      This is also where I had XO6 in preview mode and XO5 working perfectly fine next to each other.

      Screenshots:

      • Still Loading
        3c3292a1-a326-4cab-b69c-6016868bceeb-image.png
      P 1 Reply Last reply Reply Quote 0
      • P Offline
        ph7 @probain
        last edited by

        @probain Well I’ve been running commit 035ee for a few days now and haven't had any problems. But haven't done a lot of work with it.

        When I update, I always run some kind of full/complicated update since I've had some problems before and with this type of update I've never had any issues.

        sudo su
        nvm install 22 && npm install --global yarn && cd ~/xen-orchestra/ && git checkout . && git pull --ff-only && yarn && yarn build --force && yarn run turbo run build --filter @xen-orchestra/web && systemctl restart xo-server.service && cd && systemctl daemon-reload
        

        Or maybe just a simple CTRL F5 in Your browser will work 🙂

        1 Reply Last reply Reply Quote 0
        • First post
          Last post