backup mail report says INTERRUPTED but it's not ?
-
Hi @Pilow,
I've done some more testing and looked at the code, and I wasn't able to reproduce this behaviour once. It's also unclear to me why it can happen.
We may just add the delay as you did, but 10s is probably too long. Could you try to replace it by a 1s delay instead, and tell us if it's enough?
-
@Bastien-Nollet okay i'll do that tonight and will report back
-
26 backups in a row without interruption, spanning 2 days
And i'm on the 1 second fixguess it is enough...
@Bastien-Nollet said in backup mail report says INTERRUPTED but it's not ?:
I've done some more testing and looked at the code, and I wasn't able to reproduce this behaviour once. It's also unclear to me why it can happen.
I didn't tell but my Remotes are S3 Remotes... could it be because of that ?
-
Thanks again @Pilow
I don't think the remotes being S3 changes something here.
-
@Bastien-Nollet oopsy.
sadly, INTERRUPTED is back....
this is what I see in the backup report (a backup job of 12VMs to same S3 remote, only 1 interrupted...)
backup JOB in XOA is all green :
-
Ok so 1s is slightly not enough, thanks for the update.
-
@Bastien-Nollet another interrupted today.
I'll add one second by one second till I see it disappear.just modified to 2s delay.
-
@Bastien-Nollet said in backup mail report says INTERRUPTED but it's not ?:
Ok so 1s is slightly not enough, thanks for the update.
Reply
still had issues with 2 sec delay.
it has now been 2 days with 3 sec delay, and no more. could be the sweet spot
-
We're still carrying a bit of investigations to see if we can find the cause of the problem, but if we don't find it we'll add this delay.
Thanks @Pilow for the tests once again
-
We just merged the delay: https://github.com/vatesfr/xen-orchestra/pull/9400
We increased it to 5s to have a security margin, as the optimal delay may not be the same on different configurations.
-
@Bastien-Nollet many thanks
