Trying an auto backup ~10GB déjà dup restarts the whole procedure at about 10 to 50 %

[benste]

Binary package hint: deja-dup

-> Backing up on an encrypted Samba DIR on a wired network

ProblemType: Bug
Architecture: i386
Date: Tue Dec 1 20:46:37 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: deja-dup 10.2-0ubuntu1
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-15.50-generic
SourcePackage: deja-dup
Uname: Linux 2.6.31-15-generic i686

[Michael Terry (mterry)]

Can you describe what happens in a bit more detail? An automatic backup begins; you see the icon in the notification area. What do you mean by 'restarts the whole procedure'? The progress count is up to 50% and then it starts again at 0%?

[benste (benste)]

Randomly somewhere between 10% and 50% complete it starts again from 0%

[benste (benste)]

looks like this happens only from time to time, as some backups finished in the meantime

[benste (benste)]

-> News ?

for me the backups are restarted now at random positions like e.g. 77,6% and then restarting from 0%

=> one backup takes more than 8h cause it restarts the whole time

[Dan Work (dbwork)]

I have a similar problem when backing up a large dataset >10GB to S3. System Monitor shows several zombie instances of duplicity after autobackup has been running for a few hours. I'm happy to provide more info if you explain what is needed. I'm new at this.

[Michael Terry (mterry)]

I'd love to see this info:

1. The file /tmp/deja-dup.log after running the following line and replicating the problem:
    DEJA_DUP_DEBUG=1 deja-dup | tail -n 1000 > /tmp/deja-dup.log

2. The file /tmp/deja-dup.gconf after running the following line:
    gconftool-2 --dump /apps/deja-dup > /tmp/deja-dup.gconf

3. The version of deja-dup and duplicity:
    (if on Ubuntu or Debian:)
    dpkg-query -W deja-dup duplicity

4. The distribution of Linux you're using:
    lsb_release -d

[Dan Work (dbwork)]

OK here's the easy stuff:
2. see deja-dup.gconf attached.
3. deja-dup: 10.2-0ubuntu1.1, duplicity: 0.5.18-0ubuntu1
4. Ubuntu 9.10

For 1., the problem occurred with an auto backup, I'm not sure if it is reproducible from the command line, but I'll see. Let me try again, I'll send the log when I see it reoccur.

[benste (benste)]

It's not reproducable on a usual login

- is there a possibility to run the auto daemon in debug mode printing the file ?

+ I've had the idea that moving a file during the backup may cause this - moved a file this time but backup was successful

PS: I'm not that exited that it lists all files including the confidental ones :-)

[Michael Terry (mterry)]

Sorry, should have warned you to edit it before uploading. But looks like you noticed.

So this log is from a successful build? Hrm. I want one from an unsuccessful build. To get the daemon to run in debug mode, you could... hmmm. Maybe:

killall deja-dup-monitor
DEJA_DUP_DEBUG=1 deja-dup-monitor > log

I'm not actually sure if that will work. :-/

[Dan Work (dbwork)]

I didn't have any problems when starting from the command line.

Running:

killall deja-dup-monitor
DEJA_DUP_DEBUG=1 deja-dup-monitor

returns:

** (deja-dup-monitor:3985): DEBUG: monitor.vala:219: Waiting 529323 seconds until next backup.

I agree, it would be nice to give an option to block out the file names when running debug mode.

[benste (benste)]

I've edited my startup applications to run in debug mode:

DEJA_DUP_DEBUG=1 deja-dup-monitor > ~/Desktop/deja.log

-> guess next time it fails I'll get the log :-)
Lookoing forward for a reply (guess next week :-.)

[Dan Work (dbwork)]

OK I also modified my startup applications to do the same.

[benste (benste)]

Pls notice that dejadup auto corrects the entry in startup apps on every login - I've had to create a 2nd starter for the debug mode today