Manifest mismatch error

[Andrew Fister]

After starting a backup, I cancelled it, and then manually deleted the remote backup. This has caused a major problem on my machine in that I cannot make backups with deja-dup anymore. Every time I try to make any backup, whether to the same or different location, remotely or locally, I get this error:

Fatal Error: Manifest has 204 volumes, remote has 0 volumes

The terminal output shows this:

** (deja-dup:32566): DEBUG: DuplicityInstance.vala:138: Running the following duplicity (32628) command: nice ionice -c2 -n7 duplicity --exclude=/mnt/sshfs/Sky/rawr/backup/notebook/system --exclude=/home/rawr/.cache --exclude=/home/rawr/.thumbnails --exclude=/home/rawr/.gvfs --exclude=/home/rawr/.xsession-errors --exclude=/home/rawr/.recently-used.xbel --exclude=/home/rawr/.recent-applications.xbel --exclude=/home/rawr/.Private --exclude=/tmp --exclude=/proc --exclude=/sys --exclude=/home/rawr/.local/share/Trash --exclude=/home/rawr/.VirtualBox/VDI --exclude=/home/rawr/.thumbnails --include=/etc --include=/var --exclude=** / file:///mnt/sshfs/Sky/rawr/backup/notebook/system --verbosity=9 --volsize=5 --archive-dir=/home/rawr/.cache/deja-dup --log-fd=18

** (deja-dup:32566): DEBUG: DuplicityInstance.vala:449: duplicity (32628) exited with value 1

I have tried removing and purging deja-dup and all its dependencies and reinstalling it. I still can't figure out how to fix the problem. I can't find out where the local copy of the manifest is located. It seems as though this is an undesirable result.

[Michael Terry (mterry)]

As a workaround, try deleting ~/.cache/deja-dup.

[Michael Terry (mterry)]

Ken, is this intended behavior? Seems like a situation where duplicity should defer to the backup's manifest status (i.e. it's gone). Is there something Deja Dup can do to be smarter about this?

[Andrew Fister (andrewfister)]

I'm also getting a manifest mismatch when I break off a backup(hard shut down on computer, etc), and then try to start it again. It was off by one, e.g. 3293 on the local manifest and 3292 on the remote manifest. I tried deleting the last entry on the local manifest, but it doesn't change the result.

[Kenneth Loafman (kenneth-loafman)]

Temposs wrote:
> I'm also getting a manifest mismatch when I break off a backup(hard shut
> down on computer, etc), and then try to start it again. It was off by
> one, e.g. 3293 on the local manifest and 3292 on the remote manifest. I
> tried deleting the last entry on the local manifest, but it doesn't
> change the result.

If you stop duplicity there will be no remote manifest unless its the
one from a previous backup. The manifest and sigtar files are not sent
to the remote until the backup is complete. Prior to that, they will be
named with a *.part.* in their name, uncompressed and not encrypted.

Some log info, as much as you can, would be helpful.

...Ken

[Kenneth Loafman (kenneth-loafman)]

Michael Terry wrote:
> Ken, is this intended behavior? Seems like a situation where duplicity
> should defer to the backup's manifest status (i.e. it's gone). Is there
> something Deja Dup can do to be smarter about this?

I'm going to have to address this in the next release. Duplicity now
needs to have the archive-dir in place and will create one in
~/.duplicity if its not specified. The user needs to clear that as well
if the remote backup has been deleted.

...Ken

[Kenneth Loafman (kenneth-loafman)]

With version 0.6.02 the metadata is synched fully between the local and remote caches. This problem was caused by deleting a remote backup. When the new version runs, the local archive will be cleared of any spurious files, thus this will not happen again.

[Andrew Fister (andrewfister)]

You're awesome, Kenneth :-)