duplicity-team team mailing list archive

[edso <question288602@xxxxxxxxxxxxxxxxxxxxx>]

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

    Status: Open => Answered

edso proposed the following answer:
On 14.03.2016 15:42, Hnyk Daniel wrote:
> Question #288602 on Duplicity changed:
> https://answers.launchpad.net/duplicity/+question/288602
> 
>     Status: Answered => Open
> 
> Hnyk Daniel is still having a problem:
> Hey,
> 
> thanks for an answer.
> 
> Version is written in log: "duplicity 0.7.06 (December 07, 2015)".
> 
> When I try:
> 
> duplicity -v5 --exclude-filelist=bckp_excl.txt /
> scp://kmlinux//scratch/home/hnykdan1/dtfiles
> 
> I input my passphrase and I get basically the same output:
> 
> duplicity 0.7.06 (December 07, 2015)
> Args: /usr/bin/duplicity -v5 --exclude-filelist=bckp_excl.txt / scp://kmlinux//scratch/home/hnykdan1/dtfiles
> Linux smecpi 4.1.19-3-ARCH #1 Mon Mar 7 20:04:37 MST 2016 armv6l 
> /usr/bin/python2 2.7.11 (default, Mar  6 2016, 12:21:48) 
> [GCC 5.3.0]
> ================================================================================
> Using temporary directory /tmp/duplicity-29o44a-tempdir
> Temp has 251318272 available, backup will use approx 34078720.
> Local and Remote metadata are synchronized, no sync needed.
> Last full backup left a partial set, restarting.
> Last full backup date: Fri Mar 11 13:57:54 2016
> PASSPHRASE variable not set, asking user.
> GnuPG passphrase: 
> PASSPHRASE variable not set, asking user.
> Retype passphrase to confirm: 
> RESTART: Volumes 81 to 111 failed to upload before termination.
>          Restarting backup at volume 81.
> GPG error detail: Traceback (most recent call last):
>   File "/usr/bin/duplicity", line 1532, in <module>
>     with_tempdir(main)
>   File "/usr/bin/duplicity", line 1526, in with_tempdir
>     fn()
>   File "/usr/bin/duplicity", line 1380, in main
>     do_backup(action)
>   File "/usr/bin/duplicity", line 1496, in do_backup
>     full_backup(col_stats)
>   File "/usr/bin/duplicity", line 567, in full_backup
>     globals.backend)
>   File "/usr/bin/duplicity", line 380, in write_multivol
>     validate_encryption_settings(globals.restart.last_backup, mf)
>   File "/usr/bin/duplicity", line 368, in validate_encryption_settings
>     fileobj.close()
>   File "/usr/lib/python2.7/site-packages/duplicity/dup_temp.py", line 226, in close
>     assert not self.fileobj.close()
>   File "/usr/lib/python2.7/site-packages/duplicity/gpg.py", line 259, in close
>     self.gpg_failed()
>   File "/usr/lib/python2.7/site-packages/duplicity/gpg.py", line 226, in gpg_failed
>     raise GPGError(msg)
> GPGError: GPG Failed, see log below:
> ===== Begin GnuPG log =====
> gpg: encrypted with 2048-bit RSA key, ID 6B574972, created 2016-03-11
> "Daniel Hnyk <hnykda@xxxxxxxxx>"
> gpg: public key decryption failed: Inappropriate ioctl for device
> gpg: decryption failed: No secret key
> ===== End GnuPG log =====
> 
> 
> GPGError: GPG Failed, see log below:
> ===== Begin GnuPG log =====
> gpg: encrypted with 2048-bit RSA key, ID 6B574972, created 2016-03-11
> "Daniel Hnyk <hnykda@xxxxxxxxx>"
> gpg: public key decryption failed: Inappropriate ioctl for device
> gpg: decryption failed: No secret key
> ===== End GnuPG log =====
> 

smells like the gpg2 issue to me, the superuser ticket has a workaround
 http://superuser.com/questions/984977/duplicity-restore-failing-no-secret-key

..ede/duply.net

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