metadata backups suddenly failing

manilx

@olivierlambert Yes, just fine.

olivierlambert

Have you tried the "healthcheck" on the remote? Can you give more info on the remote? Is it visible when doing df -h?

manilx

@manilx XO version 63ee6b7f0 backs up just fine. Updating it to 84e38505c breaks it.

olivierlambert

Okay can you bisect to find the bad commit?

manilx

@olivierlambert Sorry, no programmer or linux specialist here. What do you mean?

olivierlambert

Trying to find the first broken commit where it doesn't work

manilx

@olivierlambert As mentioned:

version 63ee6b7f0 backs up just fine. This is the last one I had installed a few days(3-4?) back and was working.
Updating yesterday/today to 84e38505c breaks it.

olivierlambert

84e38505c is the commit broken, right? The commit just before is working then?

manilx

@olivierlambert Correct! 84e38505c is definitely broken.
63ee6b7f0 was the one I had before is fine, can't tell if there was one in between.

Andrew

@olivierlambert I'll join the it's broken club. S3 backups worked for VMs but not the metadata.

manilx

@Andrew said in metadata backups suddenly failing:

@olivierlambert I'll join the it's broken club. S3 backups worked for VMs but not the metadata.

Yes. VM backups work fine, it's just the Pool metadata and XO config that's broken.

julien-f

Thank you, I'm on it

julien-f

@manilx @Andrew It should be fixed, thanks!

https://github.com/vatesfr/xen-orchestra/commit/ea2c6416044a3bf4a9c4ee5a246d44aa2fa2f4f9

0

julien-f committed to vatesfr/xen-orchestra

fix(backups): fix remote timeout for metadata

Fixes https://xcp-ng.org/forum/post/59356

Introduced by 61b9a4cf2O

Andrew

@julien-f Metadata backup works for me now. Thanks!

manilx

@julien-f Works! Thank You for the quick fix.

olivierlambert

Thank you @manilx and @Andrew for your feedback!