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

    XOA Updater fails

    Scheduled Pinned Locked Moved Unsolved Xen Orchestra
    4 Posts 2 Posters 643 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.
    • andibingA Offline
      andibing
      last edited by

      I'm seeing this on XOA:

      xoa@xoa:~$ sudo xoa-updater --upgrade
      โœ– { message: 'missing string at offset 151' }
      xoa@xoa:~$
      

      Unless the sun has got to me, I don't seen any other references to this error. And Gemini was confused too!

      Any thoughts?

      J 1 Reply Last reply Reply Quote 0
      • J Offline
        john.c @andibing
        last edited by john.c

        @andibing said:

        I'm seeing this on XOA:

        xoa@xoa:~$ sudo xoa-updater --upgrade
        โœ– { message: 'missing string at offset 151' }
        xoa@xoa:~$
        

        Unless the sun has got to me, I don't seen any other references to this error. And Gemini was confused too!

        Any thoughts?

        Can you please run โ€œdf -hโ€ to start? If either / or /tmp/xoa-updater are low on space please increase disk space or run a clean up. The disk space on the VM and/or the SR may be too low, for the update to succeed.

        The XOA update metadata cache may have become corrupted and need to be cleared, before re-attempting the update. Checking the logs will help to determine if thatโ€™s the case.

        andibingA 1 Reply Last reply Reply Quote 0
        • J Offline
          john.c
          last edited by

          This post is deleted!
          1 Reply Last reply Reply Quote 0
          • andibingA Offline
            andibing @john.c
            last edited by

            @john.c said:

            nd need to be cleared, before re-attempting the update. Checking the logs will help

            Just for completeness... it kept doing this after all the typical diagnosis steps. So never found a solution ๐Ÿ˜ž Definitely wasn't cache or disc space related.

            In the end I built the XOA from source on the same VM and that worked fine.
            Although subsequent to that I've moved XOA to the containerised version thus saving an extra VM!.

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

            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