Try restarting your gpg-agent. It's not talking to duplicity. gpg: encrypted with 4096-bit ELG key, ID AA5ACFC9, created 2010-12-14 "FM Duplicity (Backup Key) <[email protected]>" gpg: public key decryption failed: Bad passphrase gpg: decryption failed: No secret key can't connect to `/root/.gnupg/S.gpg-agent': No such file or directory <<<------ HERE!
...Ken On Wed, Jan 4, 2012 at 8:25 AM, Chris Stankaitis < [email protected]> wrote: > New question #183711 on Duplicity: > https://answers.launchpad.net/duplicity/+question/183711 > > Running a rather large full backup around 350GB as it's the beginning of > the month. backup kacked out. When trying to resume it I get the > following error. > > Found primary backup chain with matching signature chain: > ------------------------- > Chain start time: Tue Jan 3 09:58:12 2012 > Chain end time: Tue Jan 3 09:58:12 2012 > Number of contained backup sets: 1 > Total number of contained volumes: 4633 > Type of backup set: Time: Num volumes: > Full Tue Jan 3 09:58:12 2012 4633 > ------------------------- > No orphaned or incomplete backup sets found. > RESTART: Volumes 4633 to 4633 failed to upload before termination. > Restarting backup at volume 4633. > GPG error detail: Traceback (most recent call last): > File "/usr/bin/duplicity", line 1377, in <module> > with_tempdir(main) > File "/usr/bin/duplicity", line 1370, in with_tempdir > fn() > File "/usr/bin/duplicity", line 1340, in main > full_backup(col_stats) > File "/usr/bin/duplicity", line 500, in full_backup > globals.backend) > File "/usr/bin/duplicity", line 338, in write_multivol > validate_encryption_settings(globals.restart.last_backup, mf) > File "/usr/bin/duplicity", line 326, in validate_encryption_settings > fileobj.close() > File "/usr/lib64/python2.6/site-packages/duplicity/dup_temp.py", line > 222, in close > assert not self.fileobj.close() > File "/usr/lib64/python2.6/site-packages/duplicity/gpg.py", line 239, in > close > self.gpg_failed() > File "/usr/lib64/python2.6/site-packages/duplicity/gpg.py", line 206, in > gpg_failed > raise GPGError, msg > GPGError: GPG Failed, see log below: > ===== Begin GnuPG log ===== > gpg: encrypted with 4096-bit ELG key, ID AA5ACFC9, created 2010-12-14 > "FM Duplicity (Backup Key) <[email protected]>" > gpg: public key decryption failed: Bad passphrase > gpg: decryption failed: No secret key > can't connect to `/root/.gnupg/S.gpg-agent': No such file or directory > ===== End GnuPG log ===== > > > GPGError: GPG Failed, see log below: > ===== Begin GnuPG log ===== > gpg: encrypted with 4096-bit ELG key, ID AA5ACFC9, created 2010-12-14 > "FM Duplicity (Backup Key) <[email protected]>" > gpg: public key decryption failed: Bad passphrase > gpg: decryption failed: No secret key > can't connect to `/root/.gnupg/S.gpg-agent': No such file or directory > ===== End GnuPG log ===== > > > My Passphrase is exported in the same manor as any other backup which I > have done. please advise how I can get this backup to resume, It was > nearly done and I would like to finish it off rather then have to start it > again since it takes over 24 hours for duplicity to backup that much data. > > > Thanks > > OS: RHEL6 > Dup ver: 0.6.17 > Python 2.6.6 > > > -- > You received this question notification because you are a member of > duplicity-team, which is an answer contact for Duplicity. > > _______________________________________________ > Mailing list: https://launchpad.net/~duplicity-team > Post to : [email protected] > Unsubscribe : https://launchpad.net/~duplicity-team > More help : https://help.launchpad.net/ListHelp >
_______________________________________________ Mailing list: https://launchpad.net/~duplicity-team Post to : [email protected] Unsubscribe : https://launchpad.net/~duplicity-team More help : https://help.launchpad.net/ListHelp
