Hello list!
We have an issues from time to time where duplicity tries to check the synchronization between the cache and back-end. It ask for the private key passphrase (key which isn't installed) and the backup fails The error: > Synchronizing remote metadata to local cache... > PASSPHRASE variable not set, asking user. > GnuPG passphrase: We do not want to installed the GPG private key on our hosts (only the public one). From our understanding, this key is only required to decrypt backups that are stored encrypted in our Swift back-end. I'd like to know if this kind of setup is supposed to work without any issue. And what could cause the need of a synchronization? Or is the synchronization a process which has to happens regularly (even if the sync is actually good)? If yes, what's the frequency/or reason triggering it? This would make the presence of the private key on the hosts mandatory to work with encrypted backups, correct? We use duplicity 0.7.10 with duply 2.0.1. Thank you, Joshua _______________________________________________ Duplicity-talk mailing list [hidden email] https://lists.nongnu.org/mailman/listinfo/duplicity-talk |
Please upgrade to the current version of duplicity. This will assure that any bugs fixed since your release are available and may fix your issue.
NOTE: This applies especially to duplicity versions between 0.7.03 and 0.7.14 inclusive. There was a fix in 0.7.15 that reduced memory usage drastically, and will help with memory errors and inability to start new threads. There are three options:
NOTE: UNinstall duplicity first if it was installed via the distribution repository! For Ubuntu, that would be "sudo apt-get purge duplicity".
On Wed, Jul 11, 2018 at 6:31 PM Joshua M. Boniface via Duplicity-talk <[hidden email]> wrote: Hello list! _______________________________________________ Duplicity-talk mailing list [hidden email] https://lists.nongnu.org/mailman/listinfo/duplicity-talk |
Free forum by Nabble | Edit this page |