ERROR 30 AssertionError

Asked by Singpolyma

My duplicity was working fine, but now I get this:

INFO 1
. Reading results of 'rsync -e 'ssh -oBatchMode=yes'
weber-ds.local:/volume1/homes/lisette/badwolf/'

ERROR 30 AssertionError
. 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 1405, in do_backup
. globals.archive_dir).set_values()
. File "/usr/lib/python2.7/dist-packages/duplicity/collections.py",
line 710, in set_values . self.get_backup_chains(partials +
backend_filename_list) . File
"/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 835,
in get_backup_chains . add_to_sets(f) . File
"/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 823,
in add_to_sets . if set.add_filename(filename): . File
"/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 101,
in add_filename . self.set_manifest(filename) . File
"/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 136,
in set_manifest . remote_filename) . AssertionError:
('duplicity-inc.20160215T140628Z.to.20160216T135619Z.manifest.part',
'duplicity-inc.20160215T140628Z.to.20160216T135619Z.manifest.gpg') .

I very likely shut down during a backup (I have it running automatically in the background) -- how should I work around this?

Question information

Language:
English Edit question
Status:
Expired
For:
Duplicity Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
edso (ed.so) said :
#1

On 02.03.2016 02:13, Singpolyma wrote:
> New question #287438 on Duplicity:
> https://answers.launchpad.net/duplicity/+question/287438
>
> My duplicity was working fine, but now I get this:
>
> INFO 1
> . Reading results of 'rsync -e 'ssh -oBatchMode=yes'
> weber-ds.local:/volume1/homes/lisette/badwolf/'
>
> ERROR 30 AssertionError
> . 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 1405, in do_backup
> . globals.archive_dir).set_values()
> . File "/usr/lib/python2.7/dist-packages/duplicity/collections.py",
> line 710, in set_values . self.get_backup_chains(partials +
> backend_filename_list) . File
> "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 835,
> in get_backup_chains . add_to_sets(f) . File
> "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 823,
> in add_to_sets . if set.add_filename(filename): . File
> "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 101,
> in add_filename . self.set_manifest(filename) . File
> "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 136,
> in set_manifest . remote_filename) . AssertionError:
> ('duplicity-inc.20160215T140628Z.to.20160216T135619Z.manifest.part',
> 'duplicity-inc.20160215T140628Z.to.20160216T135619Z.manifest.gpg') .
>
>
> I very likely shut down during a backup (I have it running automatically in the background) -- how should I work around this?
>

what is your duplicity version?

most likely the chain "20160215T140628Z.to.20160216T135619Z" got corrupted (manifest only written partly).

try duplicity cleanup, it should remove it.

alternatively moving away all files containing the above mentioned string should convince duplicity this backup never happened and resolve the issue.

..ede/duply.net

Revision history for this message
Singpolyma (singpolyma) said :
#2

$ duplicity --version
duplicity 0.7.06

$ PASSPHRASE= duplicity cleanup --force --verbosity=8 --asynchronous-upload --hidden-encrypt-key E53D6503 --exclude /home/lisette/Private --exclude /home/lisette/.cache/mozilla --name weber-ds --log-file /home/lisette/.duplicity.log par2+rsync://weber-ds.local//volume1/homes/lisette/badwolf

Using archive dir: /home/lisette/.cache/duplicity/weber-ds
Using backup name: weber-ds
Import of duplicity.backends.azurebackend Succeeded
Import of duplicity.backends.b2backend Succeeded
Import of duplicity.backends.botobackend Succeeded
Import of duplicity.backends.cfbackend Succeeded
Import of duplicity.backends.copycombackend Succeeded
Import of duplicity.backends.dpbxbackend Succeeded
Import of duplicity.backends.gdocsbackend Succeeded
Import of duplicity.backends.giobackend Succeeded
Import of duplicity.backends.hsibackend Succeeded
Import of duplicity.backends.hubicbackend Succeeded
Import of duplicity.backends.imapbackend Succeeded
Import of duplicity.backends.lftpbackend Succeeded
Import of duplicity.backends.localbackend Succeeded
Import of duplicity.backends.megabackend Succeeded
Import of duplicity.backends.multibackend Succeeded
Import of duplicity.backends.ncftpbackend Succeeded
Import of duplicity.backends.onedrivebackend Succeeded
Import of duplicity.backends.par2backend Succeeded
Import of duplicity.backends.pydrivebackend Succeeded
Import of duplicity.backends.rsyncbackend Succeeded
Import of duplicity.backends.ssh_paramiko_backend Succeeded
Import of duplicity.backends.ssh_pexpect_backend Succeeded
Import of duplicity.backends.swiftbackend Succeeded
Import of duplicity.backends.sxbackend Succeeded
Import of duplicity.backends.tahoebackend Succeeded
Import of duplicity.backends.webdavbackend Succeeded
Main action: cleanup
================================================================================
duplicity 0.7.06 ($reldate)
Args: /usr/bin/duplicity cleanup --force --verbosity=8 --asynchronous-upload --hidden-encrypt-key E53D6503 --exclude /home/lisette/Private --exclude /home/lisette/.cache/mozilla --name weber-ds --log-file /home/lisette/.duplicity.log par2+rsync://weber-ds.local//volume1/homes/lisette/badwolf
Linux badwolf 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt20-1+deb8u3 (2016-01-17) x86_64
/usr/bin/python 2.7.9 (default, Mar 1 2015, 12:57:24)
[GCC 4.9.2]
================================================================================
Reading results of 'rsync -e 'ssh -oBatchMode=yes' weber-ds.local:/volume1/homes/lisette/badwolf/'
Local and Remote metadata are synchronized, no sync needed.
Reading results of 'rsync -e 'ssh -oBatchMode=yes' weber-ds.local:/volume1/homes/lisette/badwolf/'
Using temporary directory /tmp/duplicity-Sc6GUU-tempdir
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 1405, in do_backup
    globals.archive_dir).set_values()
  File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 710, in set_values
    self.get_backup_chains(partials + backend_filename_list)
  File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 835, in get_backup_chains
    add_to_sets(f)
  File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 823, in add_to_sets
    if set.add_filename(filename):
  File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 101, in add_filename
    self.set_manifest(filename)
  File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 136, in set_manifest
    remote_filename)
AssertionError: ('duplicity-inc.20160215T140628Z.to.20160216T135619Z.manifest.part', 'duplicity-inc.20160215T140628Z.to.20160216T135619Z.manifest.gpg')

Revision history for this message
edso (ed.so) said :
#3

did you try my suggestions already? what was the result? ..ede/duply.net

Revision history for this message
Singpolyma (singpolyma) said :
#4

The above was the result of my trying your first suggestion (to run "cleanup"). I will try your second suggestion (to rename the files in the error message by hand) today.

Revision history for this message
Singpolyma (singpolyma) said :
#5

The *.part file from the error did not exist. Deleting the *.gpg file from the error seems to have fixed it for now.

It seems like there was a bug in cleanup, though. It would be nice if that worked so that these backups can keep going unattended in the future.

Revision history for this message
Launchpad Janitor (janitor) said :
#6

This question was expired because it remained in the 'Open' state without activity for the last 15 days.