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 Unsolved Backup
    103 Posts 20 Posters 11.9k Views 21 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.
    • J Offline
      JB
      last edited by

      0f9a7699-7d49-4dce-a588-e7e999730275-image.jpeg

      commit 9cdaf

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

        Here is my story:
        I responded to the notice regarding the latest update of the main branch, Master, commit 9cdaf, by updating the XO-CE vm, rebooting the XO-CE vm, bringing all 3 XCP-ng hosts on line, and then running the XO-CE GUI and selecting Pool Rolling Update.
        The rolling update cycled through all 3 hosts in the pool.
        I then attempted to run a pool metadata and xo_config backup.
        It failed by timing out at 5 minutes.
        I decided to shutdown the pool master, so I transferred all VMs to the other 2 hosts and shutdown the master for 15 seconds. I powered on the master, and transferred the VMs back to the master.
        I shutdown the other 2 hosts, and then powered them back on. All hosts are indicating "green" status.
        At this point I attempted to run the pool metadata and xo_config backup, and it ran successfully.
        I waited 2 minutes and ran it again, with success again!
        Lastly, I powered down the other 2 hosts, and with the VMs all running on the master, I ran the pool metadata and xo_config backup again, with apparent success.
        If someone can tell me the location of the logs that recorded this operation, I will look at them closely to confirm that the pool metadata and xo_config backups actually took place.
        Thank you.

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

          Here is the log for the GUI Backup function:

          1dab5aec-6f9a-4338-bf7d-dab065e17e43-image.jpeg

          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