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

    Backup fails with "Body Timeout Error", "all targets have failed, step: writer.run()"

    Scheduled Pinned Locked Moved Solved Backup
    114 Posts 21 Posters 16.1k Views 22 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.
    • christopher-petzelC Offline
      christopher-petzel @JB
      last edited by

      @JB @gregbinsd The fix has not been merged with the master branch yet, so you won't have the fix yet. Follow this pull request https://github.com/vatesfr/xen-orchestra/pull/10282

      When you see an entry at the end of the activity log which says something like ' merged commit [commit ID] into master' then you'll know the fix has been added to the master branch.

      It's important to know that they could close this pull request without committing it to the master branch if they want to approach the resolution in a different way (this has already happened once with this issue).

      J K 2 Replies Last reply Reply Quote 0
      • J Offline
        JB @christopher-petzel
        last edited by

        @christopher-petzel Ok! Thanks!

        1 Reply Last reply Reply Quote 0
        • K Offline
          Kajetan321 @christopher-petzel
          last edited by

          @christopher-petzel Hello. Has the fix been merged yet? I'm on commit 03865 and I'm still getting this problem.

          K 1 Reply Last reply Reply Quote 0
          • K Offline
            Kajetan321 @Kajetan321
            last edited by

            Looking at Git, it doesn't seem like it, so I guess that answers my question.

            1 Reply Last reply Reply Quote 0
            • christopher-petzelC Offline
              christopher-petzel
              last edited by

              The fix has been merged into the master branch.

              88f787a0-138b-40c5-9dde-dacfff97c1cf-image.jpeg

              I've updated from master and tested the metadata backup by manually triggering it 10 times. I had no errors. This issue seems to be resolved.

              Thanks to the XO team for this fix!

              poddingueP 1 Reply Last reply Reply Quote 2
              • poddingueP Online
                poddingue Vates 🪐 @christopher-petzel
                last edited by

                Thanks a lot for the feedback, @christopher-petzel ! 👍

                1 Reply Last reply Reply Quote 0
                • J Offline
                  JB
                  last edited by

                  4ce59e56-d379-49fc-83dd-575a82838aec-image.jpeg

                  That's wonderful! Thank you, XenOrchestra team!

                  P 1 Reply Last reply Reply Quote 1
                  • P Offline
                    pierrebrunet Vates 🪐 XO Team @JB
                    last edited by

                    @JB @christopher-petzel Thanks for your patience! We are glad it works well!

                    1 Reply Last reply Reply Quote 0
                    • poddingueP poddingue has marked this topic as solved
                    • G Offline
                      GregBinSD
                      last edited by

                      @pierrebrunet @poddingue @jb

                      FYI, I waited until after the automated backups occurred this morning to tell you that the pool_metada and xo_config backups are now working well to my NFS BR, after I had processed the global update and did a rolling pool update last week.

                      My thanks to the XO team.

                      1 Reply Last reply Reply Quote 0
                      • acebmxerA Offline
                        acebmxer
                        last edited by

                        Vates tech responded to my ticket - Ticket#7762089 stated there was patch to apply to my XOA. After it was applied the rep stated to reboot XOA..

                        From then XOA would not connect to either remote proxy with error about unknown state (logs in ticket) XOA keep running into OOM issues after about 5 min idle trying to reconnect to remotes... Multiple reboots of xoa or proxy would not let them reconnect or memory issue to stop...

                        I had issues trying to revert back to previous snapshot taken during on of the upgrades... Eventualy got to to revert back to 6.8.1 proxies reconnected instantly...

                        poddingueP 1 Reply Last reply Reply Quote 0
                        • poddingueP Online
                          poddingue Vates 🪐 @acebmxer
                          last edited by

                          Thanks a lot for your feeback, folks! 👍

                          1 Reply Last reply Reply Quote 0

                          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