XO Team

@maverick No hurries, we have a lot on our plates too.

@maverick npm i replace yarn, not yarn build.

Hello,

We could reproduce it with a job with only continuous replication. the PR with the fix is here : https://github.com/vatesfr/xen-orchestra/pull/6437/files

Can you confirm it fixes the problem ?

Regards
Florent

fbeauchamp created this issue in vatesfr/xen-orchestra

open fix(backup): handle *couldn't instantiate any remote* on continuous replication #6437

@maverick

1. Do not run yarn, it is replaced by npm i
2. Start with --legacy-peer-deps, only if it does not work try --force
3. If it still does not work, yes please, retry from scratch.

@maverick I have no idea what you get this npm error, we haven't been able to reproduce.

Have you tried running npm with --force or --legacy-peer-deps like the error message suggests?

@Andrew Have you got any retrying writing file message in the logs ?

@maverick We are unable to reproduce this on our side, even with npm@8.1.0. Which version of Node are you using?

Can you retry with npm@8.15.0?

@Tristis-Oris can you open a support tunnel and give me the access code ( by direct message ) ?
https://help.vates.fr/help/en-us/8-technical-support/16-create-a-support-tunnel

I would like to look into this in detail since we made quite a lot of changes on the merge and the caching recently
regards

@Andrew hi ,

I made a PR that retries 5 times even on error 400, can you test it ?
https://github.com/vatesfr/xen-orchestra/pull/6433

Regards
Florent

fbeauchamp created this issue in vatesfr/xen-orchestra

open fix(s3): retry upload even on error 400 #6433

@Tristis-Oris have you got a XOA which we could use to access your system ?