Backup failed after "verifying backup" step

[Rainer Rohde]

I get the following error message after the backup procedure moves on to the "verifying backup" stage; also, see screenshot attached.

Traceback (most recent call last):
  File "/usr/bin/duplicity", line 1411, in <module>
    with_tempdir(main)
  File "/usr/bin/duplicity", line 1404, in with_tempdir
    fn()
  File "/usr/bin/duplicity", line 1338, in main
    restore(col_stats)
  File "/usr/bin/duplicity", line 632, in restore
    restore_get_patched_rop_iter(col_stats)):
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 526, in Write_ROPaths
    for ropath in rop_iter:
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 499, in integrate_patch_iters
    final_ropath = patch_seq2ropath( normalize_ps( patch_seq ) )
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 466, in patch_seq2ropath
    assert len( patch_seq ) == 1, len( patch_seq )
AssertionError: 6

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: duplicity 0.6.21-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-8.17-generic 3.8.0
Uname: Linux 3.8.0-8-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.9.2-0ubuntu2
Architecture: amd64
Date: Sun Mar 24 15:26:31 2013
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: duplicity
UpgradeStatus: No upgrade log present (probably fresh install)

[Rainer Rohde (rainer-rohde)]

I forgot to add that I am backing up to a 1TB external disk via USB3 connection.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Paolo Melchiorre (paulox)]

I upgraded Ubuntu 12.10 64bit to Ubuntu 13.04 64bit, then I tryed do use dejadup but I receive this error:

Traceback (most recent call last):
  File "/usr/bin/duplicity", line 1411, in <module>
    with_tempdir(main)
  File "/usr/bin/duplicity", line 1404, in with_tempdir
    fn()
  File "/usr/bin/duplicity", line 1338, in main
    restore(col_stats)
  File "/usr/bin/duplicity", line 632, in restore
    restore_get_patched_rop_iter(col_stats)):
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 526, in Write_ROPaths
    for ropath in rop_iter:
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 499, in integrate_patch_iters
    final_ropath = patch_seq2ropath( normalize_ps( patch_seq ) )
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 466, in patch_seq2ropath
    assert len( patch_seq ) == 1, len( patch_seq )
AssertionError: 4

I backup a list of subdirectories of my home in a local directory mounted by NFS on my NAS in LAN.

Before upgrade to Ubuntu 13.04 backup and restore operation was fine.

[Paolo Melchiorre (paulox)]

I read a lot of messages in duplicity and dejadup bug on launchpad.

I deleted dejadup chache directory
rm -rf .cache/deja-dup/
and restarted my laptop.

I started again backup from command line
deja-dup --backup

After 15min in my monitor session I read ~7GByte received and ~350MByte send over my LAN Gigabit to/from my Qnap NAS.

At the end I got this error message:

Traceback (most recent call last):
  File "/usr/bin/duplicity", line 1411, in <module>
    with_tempdir(main)
  File "/usr/bin/duplicity", line 1404, in with_tempdir
    fn()
  File "/usr/bin/duplicity", line 1338, in main
    restore(col_stats)
  File "/usr/bin/duplicity", line 632, in restore
    restore_get_patched_rop_iter(col_stats)):
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 526, in Write_ROPaths
    for ropath in rop_iter:
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 499, in integrate_patch_iters
    final_ropath = patch_seq2ropath( normalize_ps( patch_seq ) )
  File "/usr/lib/python2.7/dist-packages/duplicity/patchdir.py", line 466, in patch_seq2ropath
    assert len( patch_seq ) == 1, len( patch_seq )
AssertionError: 5

[Jannik Grube (nulldeluxe)]

After upgrading to 13.04 I was also experiencing the exact same bug in deja-dup.

However, backing up to a new location does not trigger the error.

So I moved my old backup destination (a nfs folder on the network) out of the way and started the backup from scratch. Since then, no errors in the backup. Of course I do not have a seemless backup history that way, but at least as a workaround it's working.

[Felipe Castillo (fcastillo.ec)]

It's been 4 moths since the last post and 6 since this bug was reported. This problem still persist and I found a question on askubuntu which suggested to install python-boto, this didn't make any difference.

http://askubuntu.com/a/268570/6211