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

    S3 pool metadata backup errors with "The XML you provided was not well-formed or did not validate against our published schema"

    Scheduled Pinned Locked Moved Backup
    6 Posts 2 Posters 18 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.
    • A Offline
      archw
      last edited by

      Pool Metadata backups to S3 will work for a few days then start having an error that says "The XML you provided was not well-formed or did not validate against our published schema".

      I can set up a new backup job which works a few days then starts having the same error.

      This running on Xen Orchestra (commit a0e77) complied from source.

      Thoughts?

      Thanks!

      1 Reply Last reply Reply Quote 0
      • olivierlambertO Offline
        olivierlambert Vates 🪐 Co-Founder CEO
        last edited by olivierlambert

        Hi,

        There's thousands of different S3 providers in the world, and sometimes, some of them are behaving weirdly. We do test our S3 capabilities with the most popular S3 AWS SDK (in Node), so it's very likely that the issue comes fro the provider itself. However, we have no information in your post about which provider you are using, so it's hard to tell.

        A 1 Reply Last reply Reply Quote 0
        • A Offline
          archw @olivierlambert
          last edited by

          @olivierlambert
          Oops...
          Amazon S3

          1 Reply Last reply Reply Quote 0
          • olivierlambertO Offline
            olivierlambert Vates 🪐 Co-Founder CEO
            last edited by

            That's interesting, I assume you are reaching the error when you reach the retention number?

            A 1 Reply Last reply Reply Quote 0
            • A Offline
              archw @olivierlambert
              last edited by

              @olivierlambert
              Hmmmmmmm....good thought and you are right. I had it set at 10 and counted and it crapped out at 10. I just changed it to 100 and it worked fine!

              1 Reply Last reply Reply Quote 0
              • olivierlambertO Offline
                olivierlambert Vates 🪐 Co-Founder CEO
                last edited by

                Okay so it's maybe a bug that's easy to reproduce on our side, with a retention of 1 or 2. Let me ping @florent

                Thanks for your report!

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