Welcome to the forum @automatyck and thanks for sharing the workaround (sorry it came to that).
however it’d be useful to do some experiments on a system with the issue. For example, the one with
skip-metadata=true was (to get in technical details) a guess that Duplicati’s use of system calls to get information might subject it to the usual system call worry that “slow” ones may be interrupted midway.
From what I read, mono internally uses some signals for its own use. Possibly these must be avoided.
Another advanced study mentioned earlier was use of strace to see if it can name the interrupted call.
If the issue is entirely within mono interpreting code, then that’s likely beyond anything Duplicati can fix.
Not actually suggesting that you need to do this (unless you’re willing), but it’d be nice if someone does.
Interestingly, I don’t see an Issue open on this. That sometimes will get the technical experts involved…
What is always nice is a very rock-solid reproducible case that’s easy for a dev to do with a small setup. Flaky issues (which this one seems to be from the accounts) are a pain to track down (good step to fix).