Backup fails with "Body Timeout Error", "all targets have failed, step: writer.run()"
-
For the last week or so, the backup on one paticular VM gives this error:
VM1 (xcp-ng-1) • Snapshot Start: 2024-05-12 04:00 End: 2024-05-12 04:00 • NFS2 o transfer Start: 2024-05-12 04:00 End: 2024-05-12 05:21 Duration: an hour Error: Body Timeout Error • Start: 2024-05-12 04:00 • End: 2024-05-12 05:21 • Duration: an hour • Error: Body Timeout Error NFS2 o transfer Start: 2024-05-12 04:00 End: 2024-05-12 05:21 Duration: an hour Error: Body Timeout Error • Start: 2024-05-12 04:00 • End: 2024-05-12 05:21 • Duration: an hour • Error: Body Timeout Error Start: 2024-05-12 04:00 End: 2024-05-12 05:23 Duration: an hour Error: all targets have failed, step: writer.run() Type: full
The host is running xcp beta 3 (updated through 5-12-24), XO is version "Xen Orchestra, commit 9b9c7".
This VM and numerous other VM's back up the same way (goes to two different NFS targets) for the last five months.
I've tried running it in the middle of the day (when other backups are not running) but it didn't help.
"Number of retries if VM backup fails"=0 "Timeout " = <blank> "Compression"="zstd"
Any ideas?
-
@archw
FWIW...It happened again last night.Start: 2024-05-15 04:00
End: 2024-05-15 07:07
Duration: 3 hours
Error: Body Timeout Error
Duration: 3 hours
Error: all targets have failed, step: writer.run()
Type: full -
@archw did you find a solution for this? We expiriencing this error on all of our backup jobs since two days.
Start: 2024-06-28 14:07 End: 2024-06-28 14:28 Duration: 21 minutes Error: Body Timeout Error Type: delta
-
In the words of Ronald Reagan "I don't recall the answer to that question"
If I remember correctly (subject to the after effects of many happy hours since 5-12-24), I ended up rebooting the host that had that VM. It has never done it since.
Arch