Transport endpoint is not connected

and the settings file

@Ken, Deja Dup always excludes ~/.gvfs from the backup. Do you have any ideas why it would be getting stat'd by duplicity here?

@cement_head, I suspect removing the gvfs-fuse package will fix this for you. It provides the ~/.gvfs directory as a file-level view on remote mounts. It seems to be throwing an error when you try to access it here...

@MT

Can't uninstall gvfs-fuse - it's a dependancy of deja-dup, so it removes deja-dup. Other Ideas?

@cement_head, hmm, whoops. It's an unnecessary dependency in 10.10, and in 11.04 and on it is no longer a dependency.

Can you give me the non-debug console output? The one that shows what duplicity commands we are running? I'm assuming we are excluding ~/.gvfs correctly, but maybe something is out of whack there.

Lastly, a few crazy workaround ideas:
 * Try explicitly excluding ~/.gvfs in your preferences (this *shouldn't* have any effect)
 * You could remove your home directory from the list of included folders and instead add the folders you are interested in
 * You could try deleting ~/.gvfs, though I suspect it will be recreated for you

Try upgrading to the 0.6.13 version. That should fix the problem.

Note, be sure to 'apt-get purge duplicity' before installing from the
tarball.

On Wed, Jun 8, 2011 at 9:40 AM, cement_head <email address hidden>wrote:

> @MT
>
> Can't uninstall gvfs-fuse - it's a dependancy of deja-dup, so it removes
> deja-dup. Other Ideas?
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/794576
>
> Title:
> backup failed with unknown error
>
> Status in Déjà Dup Backup Tool:
> Incomplete
>
> Bug description:
> DejaDup started to fail, here's the complete error message
>
> I tried deleting the local cache, but it didn't fix it
>
>
> Traceback (most recent call last):
> File "/usr/bin/duplicity", line 1257, in <module>
> with_tempdir(main)
> File "/usr/bin/duplicity", line 1250, in with_tempdir
> fn()
> File "/usr/bin/duplicity", line 1232, in main
> incremental_backup(sig_chain)
> File "/usr/bin/duplicity", line 479, in incremental_backup
> bytes_written = dummy_backup(tarblock_iter)
> File "/usr/bin/duplicity", line 161, in dummy_backup
> while tarblock_iter.next():
> File "/usr/lib/python2.6/dist-packages/duplicity/diffdir.py", line 505,
> in next
> result = self.process(self.input_iter.next(), size)
> File "/usr/lib/python2.6/dist-packages/duplicity/diffdir.py", line 187,
> in get_delta_iter
> for new_path, sig_path in collated:
> File "/usr/lib/python2.6/dist-packages/duplicity/diffdir.py", line 265,
> in collate2iters
> relem1 = riter1.next()
> File "/usr/lib/python2.6/dist-packages/duplicity/selection.py", line
> 174, in Iterate
> subpath, val = diryield_stack[-1].next()
> File "/usr/lib/python2.6/dist-packages/duplicity/selection.py", line
> 143, in diryield
> error_handler, Path.append, (path, filename))
> File "/usr/lib/python2.6/dist-packages/duplicity/robust.py", line 37, in
> check_common_error
> return function(*args)
> File "/usr/lib/python2.6/dist-packages/duplicity/path.py", line 506, in
> append
> return self.__class__(self.base, self.index + (ext,))
> File "/usr/lib/python2.6/dist-packages/duplicity/path.py", line 486, in
> __init__
> self.setdata()
> File "/usr/lib/python2.6/dist-packages/duplicity/path.py", line 491, in
> setdata
> self.stat = os.lstat(self.name)
> OSError: [Errno 107] Transport endpoint is not connected:
> '/home/andor/.gvfs'
>
> Here's the requested DEBUG information:
> dpkg-query -W deja-dup duplicity
> deja-dup 16.1.1-0ubuntu1
> duplicity 0.6.10-0ubuntu1
>
> lsb_release -d
> Description: Ubuntu 10.10
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/deja-dup/+bug/794576/+subscribe
>

@Ken, it's way easier to recommend the PPA in such cases. I didn't remember a fix going in for something like this and the CHANGELOG didn't seem to have anything similar. Do you remember the bug number? I can mark it as a dup if so.

@cement_head, try https://launchpad.net/~duplicity-team/+archive/ppa

okay, I've added the PPA and will try it out tomorrow - not in front of my external drive right now

@Michael Terry

Adding the PPA and upgrading duplicity fixed this error in Maverick for me. Please close ze bug!

Thanks,
CH

I'm re-opening. I've gotten other reports on up-to-date systems and can reproduce myself (steps included below). Clearly, this is a bug elsewhere (maybe in gvfs), but we should handle it better. In particular, duplicity should not bother stat'ing files that are excluded.

mkdir /tmp/source
mkdir /tmp/source/gvfs
echo hi > /tmp/source/hi

/usr/lib/gvfs/gvfs-fuse-daemon /tmp/source/gvfs
duplicity --no-encryption --exclude /tmp/source/gvfs /tmp/source file:///tmp/target # this works

killall -9 gvfs-fuse-daemon
duplicity --no-encryption --exclude /tmp/source/gvfs /tmp/source file:///tmp/target # this doesn't

Ken, I've added a duplicity task here for the no-stat work, but if you prefer, I can open a new bug specifically about not stat'ing excluded files.

(I'll take a look at implementing it)

This bug was fixed in the package duplicity - 0.6.14-0ubuntu3

---------------
duplicity (0.6.14-0ubuntu3) oneiric; urgency=low

  * debian/patches/07ignoreENOTCONN.dpatch:
    - Patch to ignore ENOTCONN errors which can happen when gvfs-fuse
      closes without cleaning up. LP: #794576
  * debian/patches/00list:
    - Actually apply 06u1ignores404.dpatch from last upload as well
      as the above 07 patch
 -- Michael Terry <email address hidden> Thu, 07 Jul 2011 16:09:51 -0400

Would it be possible to use this patch and apply it to the release in natty? If so, please upload an updated package.

Could you please add the PPA link to the bug description, so that everyone can easily find and use the bug fix?

This is the Duplicity PPA: https://launchpad.net/~duplicity-team/+archive/ppa