Duplicity returns 1 when continuing an interrupted backup

[Matej Kovacic]

Hi,

I am trying to backup to metwork disk. First time it went OK, but now I am getting this error:
"Failed with an unknown error."

I tried to run Deja Dup from comamnd line, and here is the listing:

[snip]

** (deja-dup:20618): DEBUG: DuplicityInstance.vala:118: Running the following duplicity (20664) command: nice ionice -c2 -n7 duplicity --exclude=/home/matej/.cache --exclude=/home/matej/.thumbnails --exclude=/home/matej/.gvfs --exclude=/home/matej/.xsession-errors --exclude=/home/matej/.recently-used.xbel --exclude=/home/matej/.recent-applications.xbel --exclude=/home/matej/.Private --exclude=/tmp --exclude=/proc --exclude=/sys --exclude=/home/matej/.local/share/Trash --include=/home/matej --exclude=** --dry-run --gio --volsize=10 / smb://10.0.0.200/public/Matej_backup --verbosity=9 --archive-dir=/home/matej/.cache/deja-dup --log-fd=21

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

[Matej Kovacic (matej-kovacic)]

dpkg-query -W deja-dup duplicity

deja-dup 11.1-0ubuntu0karmic1
duplicity 0.6.08-0ubuntu0karmic1

lsb_release -d

Description: Ubuntu 9.10

[Michael Terry (mterry)]

Can I see the file /tmp/deja-dup.log after running the following line and reproducing the problem?

DEJA_DUP_DEBUG=1 deja-dup | tail -n 200 > /tmp/deja-dup.log

[Matej Kovacic (matej-kovacic)]

Please see attached file:

DEJA_DUP_DEBUG=1 deja-dup | tail -n 200 > /tmp/deja-dup.log

[Paul (paulnoel)]

This problem has been switching off and on every time I receive an upgrade (starting with alpha 2) it works then after the next upgrade it fails. it was working fine (again) until the last upgrade about a week ago.

[Paul (paulnoel)]

The problem seem to be in its permissions. I tried as root "sudo psswd"and it worked. I mounted my esata drive added my folder"user home" and deleted the "root home" folder.This is a work around but hardly satisfactory and not accessible to all users. Gives a good clue as to where the problem is though. <email address hidden> Per note 2010-04-21above

[Tomaz Muraus (tomaz-muraus)]

I am having the same problem (trying to backup to local drive).

My setup:

Ubuntu 9.10 (x64)
Deja Dup: 14.0.3-0ubuntu0karmic1
Duplicity: 0.6.08-0ubuntu0karmic1

It used to work fine, but when I switched the backup destination path, it stopped working.
First I was storing backups on a locally mounted NTFS partition and not long ago, I moved it to a locally mounted ext4 partition - permissions and everything are correct.

I have attached the log file when starting Deja Dup in debug mode.

[Eric Christensen (sparks)]

I'm having similar problems as well. Backing up across LAN without encryption. Full backup worked a couple of days ago. Diffs seemed to be working each day this week. Last night started getting errors.

[Eric Christensen (sparks)]

I should mention that I'm running Fedora F13 Beta. Deja Dup version 14.0.3.

[Michael Terry (mterry)]

@Tomaz, you have the same issue as bug 569418, which is fixed in trunk.

@Eric, you look like you have the same issue as Matej.

I'm going to open a task against duplicity, because it shouldn't be exiting 1 after seeing that it should continue an interrupted backup (which is what Matej's log looks like).

[Clic (clic-ac)]

Havin the same problem with hanging on "Unknown Error".
Backup works finde the first time, after that ne more.

My Setup:
Ubuntu 10.4. Lucid
Deja-Dup 14.0.3-0ubuntu1
Duplicity 0.6.08b-0ubuntu1

DebuLog attached.

thanks in advance,
Clic

[giovano iannotti (iannotti)]

This affects me, too.

First backup went fine. But now I have that "Unknown Error".

Ubuntu 10.04 Lucid
Deja-Dup 14.0.3-0

Thank you.

Giovano Iannotti

[Michael Terry (mterry)]

@Clic, yours is an interesting log, though it is not the same as this bug. I think 14.1 from the PPA might fix your issue. If not, please file a new bug.

@giovani, that log isn't very useful to me. But I suspect yours is a different bug, until proven otherwise. Please file a new bug and follow the steps in the instructions to attach the correct log.

Right now, this bug is just about Matej's log and the issue of duplicity returning 1 instead of continuing an interrupted backup.

[Clic (clic-ac)]

Hi Michael,

thanks for advice, it seems to work with 14.1. Ran through flawlwessly. Checking tomorrow if scheduled backup works as well; I'll file a bug if not. Thanks very much für your quick and kind support!

BR,
Clic

P.S: maybe what's interesting an my log: I backup on a partition of the systems harddrive; I had a hard time to automount it ;-)

[giovano iannotti (iannotti)]

Dear Michael,

Version 14.1 seems to work here too. In case of any other bug, I'll let you know. Thank you very much.

Best wishes,

Giovano.

[Stephen Rees-Carter (valorin)]

I have experienced a similar problem - the way I have resolved it each time is to empty the cache folder: ~/.cache/deja-dup

[Martin Božič (martin-bozic)]

I confirm this bug at using NTFS local drive, Ubuntu 10.04 LTS, Deja-Dup 14.0.3. First encrypted backup worked, now it doesn't anymore. Emptying the ~/.cache/deja-dup unfortunately didn't work for me...

[Michael Terry (mterry)]

@Martin, you probably have hit the very popular bug 569418, which is about backing up to external drives and is waiting on an SRU review for a fix.

This bug is about Martej's log when he was backing up to a networked disk.

[Christopher Berner (cberner)]

Ubuntu 10.04
Deja Dup 14.1

I'm having this same problem, even with 14.1. I'm trying to back up to a SMB share, but get "failed with unknown error" every time. Let me know what logs you need, and I'll be happy to provide them.

[Kenneth Loafman (kenneth-loafman)]

Can anyone provide me with a duplicity debug (-v9) log? I've looked through the code and just don't see where a return of 1 could be coming from.

[Christopher Berner (cberner)]

Sure. How do I do that?

[Kenneth Loafman (kenneth-loafman)]

Just like deja-dup would, but without the log-fd.

duplicity --exclude=/home/matej/.cache --exclude=/home/matej/.thumbnails --exclude=/home/matej/.gvfs --exclude=/home/matej/.xsession-errors --exclude=/home/matej/.recently-used.xbel --exclude=/home/matej/.recent-applications.xbel --exclude=/home/matej/.Private --exclude=/tmp --exclude=/proc --exclude=/sys --exclude=/home/matej/.local/share/Trash --include=/home/matej --exclude=** --dry-run --gio --volsize=10 / smb://10.0.0.200/public/Matej_backup --verbosity=9 --archive-dir=/home/matej/.cache/deja-dup >& /tmp/duplicity.log

Then post /tmp/duplicity.log to this bug report. Thanks!

[Christopher Berner (cberner)]

Here's, the log you asked for. Also, I see about 15 of there errors from Deja-Dup: "** (deja-dup:3340): CRITICAL **: deja_dup_duplicity_cmp_prefix: assertion `b != NULL' failed"

[Kenneth Loafman (kenneth-loafman)]

This is an assertion error that caused the exit 1 (unknown error to Deja Dup).

"AssertionError: time not moving forward at appropriate pace - system clock issues?"

Michael, you probably need to put in 1 as an error code and echo the last line of output from duplicity.

As to the error, the current repository is fixed and it will be out in the next release.

[Kenneth Loafman (kenneth-loafman)]

Fixed in #579958 Assertion error "time not moving forward at appropriate pace"

[Thiago Henrique Santos (thenriques45)]

Same problem here on Lucid Lynx

Delete the ~/.cache/deja-dup and try again did the trick for me. Thanks to Stephen Rees-Carter who suggest this solution.

[Michael Terry (mterry)]

Hrm, I don't see that error message in Martej's log. I'm not sure that the original reporter was experiencing the 'time not moving forward at appropriate pace' issue.

[Michael Terry (mterry)]

As Thiago mentions, deleting the ~/.cache/deja-dup directory seems to fix this. I've had another confirmation of this by a friend that ran into this.

[Christopher Berner (cberner)]

deleting ~/.cache/deja-dup worked for me too.

[Murali (murali-r9+launchpad)]

I started having the same problem... Deleted ~/.cache/deja-dup and everything is all right...
But spent two days trying to figure out what was wrong with autofs/nfs4 server...

[Jens Getreu (getreu)]

for me this bug is fixed in 0.6.09, thanks

[Michael Terry (mterry)]

So this was either the common-for-a-while bug 569418, bug 654111 (which is about bugs where duplicity returns 1 and deleting the cache helps), or the bug fixed in duplicity about "time not moving forward". In each case, it's either already covered by another bug or fixed in duplicity. So I'm marking this bug invalid for deja-dup.