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 Backup
    22 Posts 12 Posters 3.1k Views 11 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.
    • bogikornelB Online
      bogikornel
      last edited by

      Unfortunately, I also get "body timeout error" errors during backups. I run several xen-orchestra servers, but it only occurs where the version is up to date. It also occurs with random VMs, and even with metadata backups. I've attached this morning's log. [xo-server.log](Invalid MIME type)

      nikadeN A P 3 Replies Last reply Reply Quote 1
      • nikadeN Offline
        nikade Top contributor @bogikornel
        last edited by

        @bogikornel We had a very old XO built from sources, which worked fine. One day we decided to deploy a new VM and migrate to a new XO built from sources, and immediately ran into problems.
        All tho it was resolved, after switching machines from HP to Cisco, which makes us believe it has something to do with the NIC, driver or firmware.

        1 Reply Last reply Reply Quote 0
        • B Offline
          Bambos
          last edited by

          I saw that happening sometimes during backend storage failure or internal storage failure.

          bogikornelB 1 Reply Last reply Reply Quote 0
          • bogikornelB Online
            bogikornel @Bambos
            last edited by

            @Bambos It's possible, but with the old version, there was no such problem, and nothing else changed except xen-orchestra.

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

              I'm having the same problem. The issue occurs with the XO config metadata backup.

              1 Reply Last reply Reply Quote 0
              • G Offline
                GregBinSD
                last edited by

                Also seeing the "Body timeout error" only on the metadata and XO-config backups for the past 2 weeks. All the VMs are backing up just fine.
                The Remote is NFS on a share called Backups:
                NFS Backups \192.168.191.8:Port:/Backups Click to edit
                2 TiB / 4.84 TiB 105.4 MiB/s / 1.8 GiB/s None

                I recently needed to restore from the metadata and xo-config backs and was able to find an old one, but can't make any new ones, so it is a source of concern.

                1 Reply Last reply Reply Quote 0
                • G Offline
                  GregBinSD
                  last edited by

                  A little more information about my post...
                  5 minutes ago, I deleted the metadata and xo-config backup job.
                  Next, I deleted the xo-config-backups directory on the remote NFS.
                  I also deleted the xo-pool-metadata-backups directory on the remote NFS.
                  I then created a new "metadata_and_xo_config_backup" job and then ran it.
                  The new job created both a xo-config-backups directory with sub dirs, as well as a xo-pool-metadata-backups directory under the /Backups NFS share on the NAS.
                  The xo-config-backups directory has a subdir and it holds a data.json (size 22.55KB), and a metadata.json (size 233 Bytes).
                  The xo-pool-metadata-backups directory has a subdirectory structure that has no saved data, no files.
                  The job failed after waiting a 5-minute period.

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

                    @bogikornel
                    Same here.....was getting the errors a while back and then they stopped. Over the last week it now happens a lot. I found that it rarely happens on incremental backups.

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

                      It's happening to me every day.

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

                        I try to back it up manually, and after 3 or 4 attempts, the backup succeeds.

                        3fad8119-582d-492d-b2bb-077af3d325ad-image.jpeg

                        1 Reply Last reply Reply Quote 0
                        • P Online
                          pierrebrunet Vates 🪐 XO Team @bogikornel
                          last edited by

                          @bogikornel Can you tell us on which versions you are please?
                          the ones where it works and the ones where it does not work.
                          Thanks for your help!

                          bogikornelB 1 Reply Last reply Reply Quote 0
                          • bogikornelB Online
                            bogikornel @pierrebrunet
                            last edited by

                            @pierrebrunet said:

                            @bogikornel Can you tell us on which versions you are please?
                            the ones where it works and the ones where it does not work.
                            Thanks for your help!

                            Not working: commit bb4da build date: 2026.07.01
                            Not working: commit 3bc70 build date: 2026.07.02
                            Working:: commit 71fa8 build date: ~ 2025.11.29
                            Working: commit 96b76 build date: ~ 2024.07.22

                            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