Backup timeout - hang or didn't work

Tristis Oris

Different jobs stil fail only 1 VM from whole backup. Few times in row, then it happens with another job or VM.

Tristis Oris

After bunch of last commits it looks fixed, 9d09a now. Thanks.
Only 1 vm stuck at this state. I already tried remove backup chain to force the full one, move vdi to maybe fix some merging problem. But that don't help.

Also this warnings still here. What to do and how to find them?
1140761d-aba4-498a-aece-d2d413e3635a-изображение.png

"result": {
                "errno": -2,
                "code": "ENOENT",
                "syscall": "open",
                "path": "/mnt/mih-5300-2/xo-vm-backups/5fc68102-9705-4918-317d-dff5e4e58237/vdis/90d0b5ca-9364-4011-adc4-b8c74a534da9/d8b005d2-ca6f-4ae5-a3b3-0cb4ef8a3016/data/1f95640b-b699-4dfd-98ea-9398ccc2b685.vhd/blocks/20/0",
                "syncStack": "Error\n    at LocalHandler.addSyncStackTrace [as _addSyncStackTrace] (/opt/xo/xo-builds/xen-orchestra-202209121459/@xen-orchestra/fs/dist/local.js:28:26)\n    at LocalHandler._readFile (/opt/xo/xo-builds/xen-orchestra-202209121459/@xen-orchestra/fs/dist/local.js:184:23)\n    at LocalHandler.readFile (/opt/xo/xo-builds/xen-orchestra-202209121459/@xen-orchestra/fs/dist/abstract.js:326:29)\n    at LocalHandler.readFile (/opt/xo/xo-builds/xen-orchestra-202209121459/node_modules/limit-concurrency-decorator/dist/index.js:107:24)\n    at VhdDirectory._readChunk (/opt/xo/xo-builds/xen-orchestra-202209121459/packages/vhd-lib/Vhd/VhdDirectory.js:153:40)\n    at VhdDirectory.readBlock (/opt/xo/xo-builds/xen-orchestra-202209121459/packages/vhd-lib/Vhd/VhdDirectory.js:211:35)\n    at VhdDirectory.mergeBlock (/opt/xo/xo-builds/xen-orchestra-202209121459/packages/vhd-lib/Vhd/VhdDirectory.js:277:37)\n    at async asyncEach.concurrency.concurrency (/opt/xo/xo-builds/xen-orchestra-202209121459/packages/vhd-lib/merge.js:181:38)",
                "chain": [
                  "xo-vm-backups/5fc68102-9705-4918-317d-dff5e4e58237/vdis/90d0b5ca-9364-4011-adc4-b8c74a534da9/d8b005d2-ca6f-4ae5-a3b3-0cb4ef8a3016/20220801T221142Z.alias.vhd",
                  "xo-vm-backups/5fc68102-9705-4918-317d-dff5e4e58237/vdis/90d0b5ca-9364-4011-adc4-b8c74a534da9/d8b005d2-ca6f-4ae5-a3b3-0cb4ef8a3016/20220802T221205Z.alias.vhd"
                ],
                "message": "ENOENT: no such file or directory, open '/mnt/mih-5300-2/xo-vm-backups/5fc68102-9705-4918-317d-dff5e4e58237/vdis/90d0b5ca-9364-4011-adc4-b8c74a534da9/d8b005d2-ca6f-4ae5-a3b3-0cb4ef8a3016/data/1f95640b-b699-4dfd-98ea-9398ccc2b685.vhd/blocks/20/0'",
                "name": "Error",
                "stack": "Error: ENOENT: no such file or directory, open '/mnt/mih-5300-2/xo-vm-backups/5fc68102-9705-4918-317d-dff5e4e58237/vdis/90d0b5ca-9364-4011-adc4-b8c74a534da9/d8b005d2-ca6f-4ae5-a3b3-0cb4ef8a3016/data/1f95640b-b699-4dfd-98ea-9398ccc2b685.vhd/blocks/20/0'"
              }

Darkbeldin

@Tristis-Oris The unused VHD warning are normal after failling snapshot, they happen when a previous backup failed and we are removing the "trash" files.
For the other error did you try to launch the job manually to see if you have the same error?

Tristis Oris

@Darkbeldin got it, so it not a problem and no need to do anything.

just started it manually, still error. But shapshot always created, i dont understand why it say failed.

Darkbeldin

@Tristis-Oris @florent will have to take a look at it because i'm not sure.

florent

@Tristis-Oris there is a missing block in the backup of 22:11 . Either a failed transfer or a failed merge that can't be resumed securily

Is it the same backups with the error message when you restart it manually ?

Tristis Oris

@florent yes, same error. But im already removed old backup and start new chain.

Tristis Oris

@olivierlambert More and more vms got this bug btw. i think a rotation can be a cause.

a backup log i see

"message": "merge"
"message": "ENOENT: no such file or directory, rename 

"syscall": "rename",
 "message": "ENOENT: no such file or directory, rename

and that still a successful backup, but with fail status. So it can't do something after backup?
After 30 days it should remove old snapshots. But i can't remove them for some vms. when try it - got same error.
f091b7ba-9dad-4a54-9d1f-fb6c0a06ca14-изображение.png

ENOENT: no such file or directory, open '/mnt/mih-5300-2/xo-vm-backups/2cac5777-cc11-117a-f107-5027fdf10950/20220608T020201Z.json'

Have ~300 old snapshots and can't remove, for a long. Is it the same problem or not?

commit ce78d

olivierlambert

Adding @florent or @julien-f

florent

@Tristis-Oris hi tristis , can you show us the full stack trace got the error on rename ?

can you make a healthcheck on the suspicious backups and see if it can restore ?

Tristis Oris

@florent
backup, 4\4 VMs with fail status https://pastebin.com/JxqEp41Q
error on remove old snapshots https://pastebin.com/sukzKCe1
done healthchecks, all failed https://pastebin.com/AnXLJH64

Now waiting for restore a copy of one vm.

florent

@Tristis-Oris hi,I see two problem :

an older merge failed for all theses VM , and some block ae missing ( 2/49 for the fisrt one, 2/52 for the second one) . These backup are irrecuperable and should be deleted
there is a desynchro between the cached metadata and the file system, you can delete them by running
find /mnt/mih-5300-2/xo-vm-backups/ -name "cache.json.gz" -type f -delete

Tristis Oris

@florent i understand that this backup maybe corrupted. But if some VMs failed first time only yesterday, that mean something continues to corrupt this procedure.

Also some VMs with that error sometimes do backup without errors.

And i already tried to remove the whole backup chain or do backup with another task - to force full backup creation. But anyway got this error.

restored one this backups - VM run and work fine.

florent

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

Tristis Oris

@florent sure, i'm deployed XOA already.
what you need to get access?

Tristis Oris

@florent said in Backup timeout - hang or didn't work:

find /mnt/mih-5300-2/xo-vm-backups/ -name "cache.json.gz" -type f -delete

That works, removed them finally. Thanks.

florent

@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

Tristis Oris

any progress with that problem?

STeffaine

any updates? im also having this issue.

Tristis Oris

After bunch of last fixes i removed some broken backup chains and now all errors gone. Thanks.