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

supportcphl

Hi All,

I came across a similar topic, which you can find here: Old Topic.

I initially replied to it but decided it would be better to start a new thread. We have several pools, and a few VMs in some pools consistently fail during the full backup with the below error.

In the previous discussion, it was mentioned that rebooting the host resolved the issue. However, I recently performed a rolling pool upgrade on one of our pools, so all nodes were rebooted, and I also rebooted the VMs. Does anyone have any suggestions on what might be causing this problem? I'm considering cloning the problematic VMs, but that seems a bit drastic.

Build: 2024-10-30
Version: 8.2
DBV: 0.0.1

Thank you

Neil

result": {
                "name": "BodyTimeoutError",
                "code": "UND_ERR_BODY_TIMEOUT",
                "message": "Body Timeout Error",
                "stack": "BodyTimeoutError: Body Timeout Error\n    at Timeout.onParserTimeout [as callback] (/usr/local/lib/node_modules/@xen-orchestra/proxy/node_modules/undici/lib/dispatcher/client-h1.js:626:28)\n    at Timeout.onTimeout [as _onTimeout] (/usr/local/lib/node_modules/@xen-orchestra/proxy/node_modules/undici/lib/util/timers.js:22:13)\n    at listOnTimeout (node:internal/timers:569:17)\n    at process.processTimers (node:internal/timers:512:7)"
              }
```.

olivierlambert

Hi,

We need more info on the XO version you are using XOA or XO from the sources?

supportcphl

@olivierlambert

Hi Oliver thanks for replying, we are using XOA.

Current version: 5.100.2 - XOA build: 20210823

This was only updated today and unfortunately I am not sure what version we was on, however I have tried another backup of a problematic VM today and got the same error.

olivierlambert

Can you try on latest release channel and see if you still have the error? Thanks!

Bambos

Hello everyone,

do we have any news for the body timeout error on backups ?

I've had this error for the last two months, using XOA and XO from sources.

The master is 2 commits behind. (93a11)
XO is 34c1c

what i can do now for this ?

DustinB

@Bambos Did you make a ticket on https://help.vates.tech/ so the support team can get in and take a look?

Bambos

@DustinB yes, i did that some days ago.

julien-f

@Bambos A timeout error means that the host did not reply in the expected delay, which, if I'm remembering correctly is 5 minutes.

I suspect a problem on your host but we will take a look further on your support ticket.