"No such file or directory" when backing up second time

Bug #395826 reported by Michael Terry
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Duplicity
Fix Released
Medium
Unassigned

Bug Description

With duplicity 0.6.01 from the PPA, I was testing Deja Dup. This is Ubuntu Karmic 9.10 (alpha).

I backed up the first time, with no problem. Simplified command line (took out some include/excludes and the --log-fd bit):

duplicity --include=/home/mike/Code/deja-dup/full/tests --exclude=** --gio --no-encryption / file:///tmp/date/local --verbosity=9 --volsize=5 --archive-dir=/tmp/date/cache/deja-dup

This left me with:

/tmp/date/cache/deja-dup/335437b100214c69b7ae514cc58fad1e/
  duplicity-full.20090705T172023Z.manifest
  duplicity-full-signatures.20090705T172023Z.sigtar.gz
/tmp/date/local/
  duplicity-full.20090705T172023Z.manifest -> /tmp/date/cache/deja-dup/335437b100214c69b7ae514cc58fad1e/duplicity-full.20090705T172023Z.manifest.part
  duplicity-full.20090705T172023Z.vol1.difftar.gz
  duplicity-full-signatures.20090705T172023Z.sigtar.gz

Note that the manifest link is a broken link.

OK. So I then tried to backup immediately again. Same command line. I got the following traceback:

Traceback (most recent call last):
  File "./duplicity/duplicity-0.6.01/usr/local/bin/duplicity", line 1145, in <module>
    with_tempdir(main)
  File "./duplicity/duplicity-0.6.01/usr/local/bin/duplicity", line 1138, in with_tempdir
    fn()
  File "./duplicity/duplicity-0.6.01/usr/local/bin/duplicity", line 1119, in main
    check_last_manifest(col_stats) # not needed for full backup
  File "./duplicity/duplicity-0.6.01/usr/local/bin/duplicity", line 913, in check_last_manifest
    last_backup_set.check_manifests()
  File "/home/mike/Code/deja-dup/full/tests/duplicity/duplicity-0.6.01/usr/local/lib/python2.6/dist-packages/duplicity/collections.py", line 163, in check_manifests
    remote_manifest = self.get_remote_manifest()
  File "/home/mike/Code/deja-dup/full/tests/duplicity/duplicity-0.6.01/usr/local/lib/python2.6/dist-packages/duplicity/collections.py", line 197, in get_remote_manifest
    manifest_buffer = self.backend.get_data(self.remote_manifest_name)
  File "/home/mike/Code/deja-dup/full/tests/duplicity/duplicity-0.6.01/usr/local/lib/python2.6/dist-packages/duplicity/backend.py", line 453, in get_data
    fin = self.get_fileobj_read(filename, parseresults)
  File "/home/mike/Code/deja-dup/full/tests/duplicity/duplicity-0.6.01/usr/local/lib/python2.6/dist-packages/duplicity/backend.py", line 416, in get_fileobj_read
    return tdp.filtered_open_with_delete("rb")
  File "/home/mike/Code/deja-dup/full/tests/duplicity/duplicity-0.6.01/usr/local/lib/python2.6/dist-packages/duplicity/dup_temp.py", line 114, in filtered_open_with_delete
    fh = FileobjHooked(path.DupPath.filtered_open(self, mode))
  File "/home/mike/Code/deja-dup/full/tests/duplicity/duplicity-0.6.01/usr/local/lib/python2.6/dist-packages/duplicity/path.py", line 726, in filtered_open
    return self.open(mode)
  File "/home/mike/Code/deja-dup/full/tests/duplicity/duplicity-0.6.01/usr/local/lib/python2.6/dist-packages/duplicity/path.py", line 514, in open
    result = open(self.name, mode)
IOError: [Errno 2] No such file or directory: '/tmp/duplicity-O2HlW1-tempdir/mktemp-smNVxJ-2'

I'll attach the entire log, which is small.

Revision history for this message
Michael Terry (mterry) wrote :
Changed in duplicity:
importance: Undecided → Medium
milestone: none → 0.6.02
status: New → Fix Committed
Changed in duplicity:
status: Fix Committed → Fix Released
Revision history for this message
Tobias Baldauf (technopagan) wrote :

I apologize beforehand if what I'm about to post is NOT the identical bug still active in 0.6.02, but the "IOError: [Errno 2] No such file or directory" seems identical. If my problem is NOT the same bug, I'll gladly open another bugreport.

Anyway, here's the error-message output of Déjà Dup 10.1:

Traceback (most recent call last):
  File "/usr/bin/duplicity", line 1200, in <module>
    with_tempdir(main)
  File "/usr/bin/duplicity", line 1193, in with_tempdir
    fn()
  File "/usr/bin/duplicity", line 1094, in main
    sync_archive()
  File "/usr/bin/duplicity", line 945, in sync_archive
    copy_to_local(fn)
  File "/usr/bin/duplicity", line 896, in copy_to_local
    fileobj = globals.backend.get_fileobj_read(rem_name)
  File "/usr/lib/python2.6/dist-packages/duplicity/backend.py", line 414, in get_fileobj_read
    self.get(filename, tdp)
  File "/usr/lib/python2.6/dist-packages/duplicity/backends/localbackend.py", line 62, in get
    local_path.writefileobj(source_path.open("rb"))
  File "/usr/lib/python2.6/dist-packages/duplicity/path.py", line 516, in open
    result = open(self.name, mode)
IOError: [Errno 2] No such file or directory: '/home/baldur/.gvfs/SFTP als tobias auf www.the-backup-server.com/home/user/username/Backups/duplicity-full.2009-02-04T17:37:34+01:00.manifest.gz'

Revision history for this message
Kenneth Loafman (kenneth-loafman) wrote :

What was the command line? Please don't munge it unless its to obscure a password.

Revision history for this message
Tobias Baldauf (technopagan) wrote :

Kenneth: It is necessary to remove certain aspects of logfiles / debugging messages to protect my privacy. However, I do always pay great detail to not messing things up so that the output stays useful.

Anyway, here's the tty-output:

** (deja-dup:4244): DEBUG: DuplicityInstance.vala:138: Running the following duplicity (4264) command: nice ionice -c2 -n7 duplicity collection-status --exclude=/home/username/.cache --exclude=/home/username/.thumbnails --exclude=/home/username/.gvfs --exclude=/home/username/.xsession-errors --exclude=/home/username/.recently-used.xbel --exclude=/home/username/.recent-applications.xbel --exclude=/home/username/.Private --exclude=/tmp --exclude=/proc --exclude=/sys --exclude=/home/username/.local/share/Trash --exclude=/home/username/.thumbnails --include=/home/username --exclude=** --no-encryption file:///home/username/.gvfs/SFTP als username auf www.the-backup-server.com/home/user/username/Backups --verbosity=9 --volsize=5 --archive-dir=/home/username/.cache/deja-dup --log-fd=17

** (deja-dup:4244): DEBUG: DuplicityInstance.vala:449: duplicity (4264) exited with value 30

Revision history for this message
Kenneth Loafman (kenneth-loafman) wrote : Re: [Bug 395826] Re: "No such file or directory" when backing up second time

Tobias Baldauf wrote:
> Kenneth: It is necessary to remove certain aspects of logfiles /
> debugging messages to protect my privacy. However, I do always pay great
> detail to not messing things up so that the output stays useful.
>
> Anyway, here's the tty-output:
>
> ** (deja-dup:4244): DEBUG: DuplicityInstance.vala:138: Running the
> following duplicity (4264) command: nice ionice -c2 -n7 duplicity
> collection-status --exclude=/home/username/.cache
> --exclude=/home/username/.thumbnails --exclude=/home/username/.gvfs
> --exclude=/home/username/.xsession-errors --exclude=/home/username
> /.recently-used.xbel --exclude=/home/username/.recent-applications.xbel
> --exclude=/home/username/.Private --exclude=/tmp --exclude=/proc
> --exclude=/sys --exclude=/home/username/.local/share/Trash
> --exclude=/home/username/.thumbnails --include=/home/username
> --exclude=** --no-encryption file:///home/username/.gvfs/SFTP als
> username auf www.the-backup-server.com/home/user/username/Backups
> --verbosity=9 --volsize=5 --archive-dir=/home/username/.cache/deja-dup
> --log-fd=17
>
> ** (deja-dup:4244): DEBUG: DuplicityInstance.vala:449: duplicity (4264)
> exited with value 30

OK, this is going to be a new bug. Would you mind reporting this as such?

I suspect this has something to do with the duplicity's interaction with
the ~/.gvfs filesystem and we'll need a bit of time to figure it out.
I've never used it like that, so I'll need to do some research.

Revision history for this message
Tobias Baldauf (technopagan) wrote :

Kenneth: I reported it as a new bug now. See https://bugs.launchpad.net/duplicity/+bug/402989

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.