duplicity-team team mailing list archive

[edso <question287438@xxxxxxxxxxxxxxxxxxxxx>]

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

    Status: Open => Answered

edso proposed the following answer:
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

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