Can't mount ftp location

Bug #648754 reported by Nick Baetens
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
sbackup
Fix Released
Low
Jean-Peer Lorenz
sbackup (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Making a backup to a remote server doesn't work in version 0.11.2 but it used to in the previous versions. I tried several settings, including ssh but I still get this error now: File access manager not initialized. The debug log is attached.

Related branches

Revision history for this message
Nick Baetens (nick-baetens) wrote :
Revision history for this message
Matti Laakso (matti-laakso) wrote :

Same here. Log is practically identical.

Changed in sbackup:
status: New → Confirmed
Revision history for this message
Jean-Peer Lorenz (peer.loz) wrote :

Thank you for using SBackup and reporting this issue.

In order to track down the cause of the problem some more information are required. Please answer the following questions:

* what distribution do you use?
* what version of sbackup is installed; from where was it installed (PPA, from source)?
* Is the bug reproducible; does it happen every time?
* do you run sbackup as superuser (root) or as regular user?
* are you able to open your backup destination using Nautilus?
* do you have these packages installed: gvfs, gvfs-fuse, gvfs-backends?

Thanks for your help.

Changed in sbackup:
status: Confirmed → Incomplete
Revision history for this message
Nick Baetens (nick-baetens) wrote : Re: [Bug 648754] Re: Can't mount ftp location

Below my responses to your questions.

Regards,
Nick

On 09/29/2010 11:43 AM, Jean-Peer Lorenz wrote:
> Thank you for using SBackup and reporting this issue.
>
> In order to track down the cause of the problem some more information
> are required. Please answer the following questions:
>
> * what distribution do you use?
Ubuntu 10.10
> * what version of sbackup is installed; from where was it installed (PPA, from source)?
 From the ubuntu repository: version 0.11.2
> * Is the bug reproducible; does it happen every time?
Yes, it happens all the time.
> * do you run sbackup as superuser (root) or as regular user?
The bug occurs in both cases.
> * are you able to open your backup destination using Nautilus?
Yes, I can connect and write files to the destination. There were no
changes to the server and I had no problems using the previous version
of the sbackup.
> * do you have these packages installed: gvfs, gvfs-fuse, gvfs-backends?
Yes, these packages are installed, also from the ubuntu repository
> Thanks for your help.
>
> ** Changed in: sbackup
> Status: Confirmed => Incomplete
>

Revision history for this message
Jean-Peer Lorenz (peer.loz) wrote :

Hum, it works for me most of the time. Occasionally it fails but it's gio/gvfs related then (I experience quite a lot of crashes of gvfs-daemon and Nautilus when using FTP paths in Maverick, mounting in general is not possible etc.). So far, sbackup works as expected.

Could you please have a look at LP Bug #617473 and perform the tests that are proposed there?

Revision history for this message
Jean-Peer Lorenz (peer.loz) wrote :

As a workaround you could use the 'legacy' Fuse plugins: https://answers.launchpad.net/nssbackup/+faq/1256

Revision history for this message
Nick Baetens (nick-baetens) wrote :

  I tried that, but that doesn't work for me.

It seems that the problems only occur in the administrative (root) mode
now, I managed to make a backup in normal mode.

On 09/29/2010 03:14 PM, Jean-Peer Lorenz wrote:
> As a workaround you could use the 'legacy' Fuse plugins:
> https://answers.launchpad.net/nssbackup/+faq/1256
>

Revision history for this message
Matti Laakso (matti-laakso) wrote :

malaakso@lempo:~$ ps aux | grep -i gvfs-fuse-daemon
malaakso 1802 0.0 0.0 78668 2668 ? Ssl Sep28 0:00 /usr/lib/gvfs//gvfs-fuse-daemon /home/malaakso/.gvfs
root 20938 0.0 0.0 78484 2424 ? Ssl 16:19 0:00 /usr/lib/gvfs//gvfs-fuse-daemon /root/.gvfs
malaakso 21070 0.0 0.0 10104 920 pts/15 S+ 16:24 0:00 grep -i gvfs-fuse-daemon

interestingly, when I press "Connect" in the destination tab, the root .gvfs folder contains

malaakso@lempo:~/.gvfs$ sudo ls -l /root/.gvfs
ls: cannot access /root/.gvfs/sftp for malaakso on phys: Input/output error
total 0
?????????? ? ? ? ? ? sftp for malaakso on phys

but a green check mark appears next to the destination text box. When I try to initiate the backup, nothing appears under /root/.gvfs.

Revision history for this message
Jean-Peer Lorenz (peer.loz) wrote :

This is not a bug in sbackup and it works in Lucid. The problem lies somewhere in gvfs or gvfs python binding, I guess.

I've caught an interesting line in apport.log:
executable: /usr/lib/gvfs/gvfsd-ftp (command line "/usr/lib/gvfs/gvfsd-ftp --spawner :1.11 /org/gtk/gvfs/exec_spaw/20")
this executable already crashed 2 times, ignoring

Unfortunately, I've no clue how to debug this further...ideas are welcome.

Revision history for this message
Matti Laakso (matti-laakso) wrote :

The problem indeed only occurs when run with (gk)sudo. However, how can I schedule backups when run as normal user? The schedule tab is grayed out.

My apport.log only contains one entry about firefox (Apport is enabled on Maverick beta).

Changed in sbackup:
status: Incomplete → In Progress
Revision history for this message
Jean-Peer Lorenz (peer.loz) wrote :

Workaround for this issue pushed to 0.11 repository.

Changed in sbackup:
status: In Progress → Fix Committed
importance: Undecided → Low
assignee: nobody → Jean-Peer Lorenz (peer.loz)
milestone: none → 0.11.3
Revision history for this message
Jean-Peer Lorenz (peer.loz) wrote :

debdiff which fixes this is attached to LP Bug #653577

Changed in sbackup (Ubuntu):
status: New → Confirmed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package sbackup - 0.11.3ubuntu1

---------------
sbackup (0.11.3ubuntu1) maverick; urgency=low

  * [Fix] LP: #645543 "Cannot concatenate str and error object" error prevents
                      incremental backups
  * [Fix] LP: #648754 Can't mount ftp location: don't fail when gvfs-fuse is
                      not available; use it only if really required
  * [Fix] LP: #653577 Error 'iter should be a GtkTreeIter' when clicking on
                      Restore with no file selected
  * refer to dependend package 'gvfs-fuse' in install and readme file
  * translations updated
  * translations added: da,el,fa,is,ja,kk,ko,kw,ro,sr,sw
 -- Jean-Peer Lorenz <email address hidden> Sun, 03 Oct 2010 20:43:39 +0200

Changed in sbackup (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Nick Baetens (nick-baetens) wrote :

It works fine now, many thanks!

Revision history for this message
kuntergunt (kuntergunt) wrote :

For some reason the fix in 0.11.3 did not solve this issue for me, though I am not using FTP but SFTP(SSH): I still get "File access manager not initialized" when started in background. Starting Simple Backup from the menu works perfect.

Here are the contents of sbackup-cron.log:

2010-10-24 18:16:11,079 - INFO: Log output for [Default Profile] is directed to file '/var/log/sbackup/sbackup.2010-10-24_18.16.11.067769.log'.
2010-10-24 18:16:11,079 - INFO: Profile settings are being read from file '/etc/sbackup.conf'.
2010-10-24 18:16:11,100 - INFO: Preparation of backup process
2010-10-24 18:16:11,101 - INFO: Initializing GIO File Access Manager.
2010-10-24 18:16:11,592 - ERROR: Error in `_do_mount`: Host key verification failed [ERROR_FAILED - Generic error condition for when any operation fails.]
2010-10-24 18:16:11,620 - ERROR: Uncaught exception: Unable to mount: Host key verification failed
2010-10-24 18:16:11,620 - ERROR: Traceback (most recent call last):
  File "/usr/share/sbackup/sbackup/fs_backend/_gio_utils.py", line 362, in _mount_done_cb
    self.__mount_finish_callback(error)
  File "/usr/share/sbackup/sbackup/fs_backend/_gio_fam.py", line 157, in _mount_cb
    raise exceptions.FileAccessException("Unable to mount: %s" % error)
FileAccessException: Unable to mount: Host key verification failed

2010-10-24 18:16:11,621 - ERROR: An error occurred during the backup: File access manager not initialized
2010-10-24 18:16:11,630 - WARNING: Unable to copy log. File access is not initialized.
2010-10-24 18:16:11,631 - INFO: Terminating GIO File Access Manager.
2010-10-24 18:16:11,631 - WARNING: GIO File Access Manager is not initialized. Nothing to do.
2010-10-24 18:16:11,631 - INFO: Processing of profile failed with error: File access manager not initialized

Updating DISPLAY to: :0
Updating SSH_AUTH_SOCK to: None
Updating GNOME_KEYRING_CONTROL to: None
Updating GNOME_KEYRING_PID to: None
Updating XAUTHORITY to: /var/run/gdm/auth-for-gugu-q0lBnI/database
Updating GPG_AGENT_INFO to: /tmp/seahorse-AKhO1r/S.gpg-agent:1624:1
D-Bus session bus launched
 DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-yA1qscPUqo,guid=7e6d1112a08957644668f1b64cc45bc7
 DBUS_SESSION_BUS_PID=3135
Now launching indicator application (status icon).
Unable to get KDE Session Manager: org.freedesktop.DBus.Error.ServiceUnknown: The name org.kde.ksmserver was not provided by any .service files
Unable to get Gnome Session Manager: org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files
No DE found using D-Bus. Looking for process id.
Indicator application started (PID: 3144)

Revision history for this message
kuntergunt (kuntergunt) wrote :

Some additional information: I am still on Lucid but with all Updates installed.

Revision history for this message
Patrick Dawkins (pjcdawkins) wrote :

If anyone still experiences this problem (SFTP locations mounting for the user but not for root), this solved it for me:

sudo mv /root/.ssh/known_hosts /root/.ssh/old_known_hosts

(You might have an expired or invalid SSH key in /root/.ssh/known_hosts)

Revision history for this message
Jean-Peer Lorenz (peer.loz) wrote :

A fix for this was released in sbackup 0.11.3. I am closing this bug for now, feel free to re-open it if still valid. Thanks.

Changed in sbackup:
status: Fix Committed → Fix Released
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.