The underlying ssh process died

Bug #1336770 reported by Pierre-Alain BOURDIL
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
sbackup
Expired
Undecided
Unassigned

Bug Description

Since upgrade to 14.04LTS, i can not backup using neither ssh,nor sftp.
The backup stop and display an alert message :

Erreur interne : The underlying ssh process died

No changes have occured on the local network and i'm able to scp big file from command line without any problems.
I attach the configuration of my backup.

SimpleBackup runs ok when using an extarnal usb disk as destination.

Revision history for this message
Pierre-Alain BOURDIL (pierrealain-bourdil) wrote :
Revision history for this message
Jean-Peer Lorenz (peer.loz) wrote :

Thank you for using sbackup and reporting this error.

Please provide a logfile or commandline output showing this error. Can you connect to your remote destination in Nautilus? Please also give some information about your system (desktop environment etc.). This would help to track down the issue. Thank you.

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

[Expired for sbackup because there has been no activity for 60 days.]

Changed in sbackup:
status: Incomplete → Expired
Revision history for this message
Pierre-Alain BOURDIL (pierrealain-bourdil) wrote :

Sorry for the delay.

I use ubuntu 14.04 LTS ,with default (unity) wm. But the problem also occurs using sbackup command line (v 0.11.6)
I 'm able to connect using Nautilus

Here is the error message outputed from sbackup command line :

2014-10-30 12:05:27,189 - ERROR in backupproc.__notify_error(337): Une erreur est survenue durant la sauvegarde :
Erreur interne : The underlying SSH process died
Traceback (most recent call last):
  File "/usr/share/sbackup/sbackup/backupproc.py", line 284, in run
    self.__bprofilehdl.process()
  File "/usr/share/sbackup/sbackup/core/profile_handler.py", line 209, in process
    self.__snapshot.commit(self.__fam_target_hdl, _publish_progress, _supports_publish)
  File "/usr/share/sbackup/sbackup/core/snapshot.py", line 426, in commit
    self.commitflistFiles()
  File "/usr/share/sbackup/sbackup/core/snapshot.py", line 614, in commitflistFiles
    "\n".join(self.__excludeFlist.getEffectiveFileList()))
  File "/usr/share/sbackup/sbackup/fs_backend/_gio_utils.py", line 855, in writetofile
    _ostr.write(content)
Error: Erreur interne : The underlying SSH process died
2014-10-30 12:05:27,199 - ERROR in backupproc.except_hook(66): Uncaught exception: Backend currently unmounting
2014-10-30 12:05:27,199 - ERROR in backupproc.except_hook(67): Traceback (most recent call last):
  File "/usr/bin/sbackup", line 42, in <module>
    retc = main(sys.argv)
  File "/usr/share/sbackup/sbackup/backupproc.py", line 583, in main
    exitcode = sbackup_app.run()
  File "/usr/share/sbackup/sbackup/backupproc.py", line 563, in run
    self.__exitcode = self.__backupproc.run()
  File "/usr/share/sbackup/sbackup/backupproc.py", line 292, in run
    self.__on_backup_error(error)
  File "/usr/share/sbackup/sbackup/backupproc.py", line 316, in __on_backup_error
    self.__exitcode = self.__bprofilehdl.finish(error)
  File "/usr/share/sbackup/sbackup/core/profile_handler.py", line 319, in finish
    self.__copylogfile()
  File "/usr/share/sbackup/sbackup/core/profile_handler.py", line 290, in __copylogfile
    _op.copyfile(logf_src, logf_target)
  File "/usr/share/sbackup/sbackup/fs_backend/_gio_utils.py", line 487, in copyfile
    _src, _dest = cls._prepare_copy(_src, _dest)
  File "/usr/share/sbackup/sbackup/fs_backend/_gio_utils.py", line 513, in _prepare_copy
    if cls.__isdir(dst_gfile):
  File "/usr/share/sbackup/sbackup/fs_backend/_gio_utils.py", line 682, in __isdir
    _ftype = cls._query_file_type(gfile)
  File "/usr/share/sbackup/sbackup/fs_backend/_gio_utils.py", line 701, in _query_file_type
    cancellable = None)
Error: Backend currently unmounting

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.