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

    After Update XO wont start

    Scheduled Pinned Locked Moved Unsolved Xen Orchestra
    6 Posts 5 Posters 840 Views 5 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.
    • E
      ElFritto
      last edited by

      After falling 23 commits behind, I updated my Xo again today. Now, when I try to start it, the following message appears. I’ve already tried a few things, but I’m not getting anywhere.

      Can anyone help me?

      75bb266b-78cd-4e6e-8bd4-50b04aa49328-image.jpeg

      siemsenitS florentF D 3 Replies Last reply
      Reply Quote 1
      • siemsenitS
        siemsenit @ElFritto
        last edited by

        @ElFritto same here. But commit 5bdd76a95 (latest from yesterday) still works.

        1 Reply Last reply
        Reply Quote 0
        • florentF
          florent Vates 🪐 XO Team @ElFritto
          last edited by florent

          @ElFritto can you do a yarn && yarn build at the root of xen-orchestra ?

          edit : found it, we will do a patch

          florentF 1 Reply Last reply
          Reply Quote 2
          • florentF
            florent Vates 🪐 XO Team @florent
            last edited by

            patch done by @bastien-nollet

            1 Reply Last reply
            Reply Quote 2
            • O
              Oreckman
              last edited by Oreckman

              @geometry game 2 This usually happens when dependencies are out of sync after pulling updates. Did you try removing node_modules and the lock file and then running yarn install again before starting XO?

              1 Reply Last reply
              Reply Quote 0
              • D
                David Brown1331 @ElFritto
                last edited by David Brown1331

                Hey, that sucks after catching up on 23 commits. Looks like something broke in the log module during the update. I’d try a clean reinstall of the dependencies first, or drop back to an older Node version for a bit since Node 24 can be fussy with these packages. When you need a quick mental break from troubleshooting npm issues, checking out TonyBet is a great way to enjoy some online gaming and sports betting. Hope getting those modules reinstalled gets your build running smoothly again soon!

                1 Reply Last reply
                Reply Quote 0
                • poddingueP poddingue marked this topic as a question on

                Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                With your input, this post could be even better 💗

                Register Login
                • First post
                  Last post