Backup fails with "Body Timeout Error", "all targets have failed, step: writer.run()"
-
I use nfs for my remotes and still get the error occasionally.
Edit - Note i am only seeing this error in my work production environment. I am not seeing this issue in my home lab. Both use NFS for remote storage and vm storage.
-
@pierrebrunet Oh one more thing that I just remembered.
If I recall correctly the first time I saw this issue was right after I patched my XCP-ng hosts without updating Xen Orchestra.
So maybe this is caused by XAPI code changes? -
commit 20bed
SMB
-
-
No worries,
Mine seems to be intermittent and restarting that pools tool stack resolves the issue for now. -
Exactly! I restarted the pools tool stack and made 3 backups. If I restart it again, I'll be able to make more backups.
-
@jb
You have hit on something that ties into what I have discovered. Since July 1, on my XCP-ng / XO-CE cluster, the metadata and xo-config backup job only runs successfully when I have all 3 hosts in my cluster active, and after I have reset the tool stack on the Master host.Because I am running the XCP-ng and XO-CE on an off-grid solar/battery system, independent of my electric bill, I try to limit total power to 250 watts for all devices (network switches, iSCSI NAS, XCP-ng hosts, etc). Consequently, I run only one host on a regular basis. When it is necessary to update XCP-ng, I turn on all hosts and do a rolling pool update. If I manually perform a metadata and xo-config backup while all of the hosts are on, only then will the backup be successful.
Before July 1, the metadata and xo-config back was always successful, whether it was scheduled or manual.
Hopefully, this will turn on a light bulb in the head of a Vates engineer, and he or she will solve this issue!
-
Are you sure it really worked? Because we fixed something that swallowed the error before. Maybe it was successful while in fact not working. When you have some hosts down in a pool, you cannot safely export metadata because XAPI can't tell if the other hosts are dead, disconnected or simply stopped.
-
@JB @gregbinsd @olivierlambert
Yes restarting the tool stack works for me. I currently do not have any host offline at least not intentionally. If there is a network glitch that i am not aware of that might cause the issue if that is the actual cause.
As @olivierlambert stated maybe we were having issues all along and they just changed something that is making the issue visible now. The support tunnel should still be open on my environment if you or the team want to look at logs.
-
@jb
@olivierlambert
Oliver, you may be right, wondering whether they really worked. How can I prove that the metadata and xo-config backups were truly successful?Below, I pasted in the GUI backup log from XO5.
-
All my hosts are online, yet the error still occurs. However, if I restart, the backup works for two or three runs.
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