duplicity-team team mailing list archive

[constantin <question690828@xxxxxxxxxxxxxxxxxxxxx>]

Question #690828 on Duplicity changed:
https://answers.launchpad.net/duplicity/+question/690828

Description changed to:
Im running duplicity 0.8.13

About 20% of my incremental backups fail with the message:

GPGError: GPG Failed, see log below:
INFO: ===== Begin GnuPG log =====
INFO: gpg: using "XXXXXXXXXXXXXX" as default secret key for signing
INFO: gpg: signing failed: Broken pipe
INFO: gpg: [stdin]: sign+encrypt failed: Broken pipe
INFO: ===== End GnuPG log =====

They run for some hours and then abort with the message above.

This is really annoying, --num-retries has no effect it will abort on
first try always.

The offsite server does not contain any inc files for the aborted
backups.

If i rerun the backup it succeeds.

I could run a for 1..3 loop until duplicity succeeds (exit status 0) but
i dont know if this may break things.

Anyone knows why that gpg error happens and knows a solution for it ?

-- 
You received this question notification because your team duplicity-team
is an answer contact for Duplicity.