Sshfs crash if connection idle by a long time

Bug #539687 reported by the door
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
sshfs-fuse (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

When i use sshfs and don't use the connection for 5 minutes proximately the sshfs crash with nautilus.

this bug is related to this one:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/539686

And tks Ubuntu team, the Lucid Lynx is better every day, when the final version ships, I will recommend to all my friends. =)

ProblemType: Bug
Architecture: i386
Date: Tue Mar 16 13:16:22 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/sshfs
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100224.1)
NonfreeKernelModules: wl
OmitPids: 4769 4767
Package: sshfs 2.2-1build1
ProcCmdline: sshfs guinacom@192.168.0.169:/ /media/guinacom
ProcEnviron:
 SHELL=/bin/bash
 LANG=pt_BR.UTF-8
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
SourcePackage: sshfs-fuse
Title: does not terminate at computer shutdown
Uname: Linux 2.6.32-16-generic i686

Revision history for this message
the door (thiagomoraesp) wrote :
Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Changed in sshfs-fuse (Ubuntu):
status: New → Incomplete
Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

We would really like to get this resolved for you. Since logs with debugging output can be useful for diagnosing the problem. Try running sshfs with the following options:

sshfs -odebug,sshfs_debug,loglevel=debug ...

and attach the full output to this report.

Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in sshfs-fuse (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Benjamin (email-bklocke) wrote :
Download full text (14.8 KiB)

As I have the same problem, have a look at the debug report;

SSHFS version 2.2
executing <ssh> <-x> <-a> <-oClearAllForwardings=yes> <-ologlevel=debug> <-2> <email address hidden> <-s> <sftp>
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to xxx.xom [XX.XX.XX.XX] port 22.
debug1: Connection established.
debug1: identity file /home/xxx/.ssh/id_rsa type -1
debug1: identity file /home/xxx/.ssh/id_dsa type -1
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.2
debug1: match: OpenSSH_5.2 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.3p1 Debian-3ubuntu4
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-md5 none
debug1: kex: client->server aes128-ctr hmac-md5 none
debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP
debug1: SSH2_MSG_KEX_DH_GEX_INIT sent
debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY
debug1: Host 'bklocke.com' is known and matches the RSA host key.
debug1: Found key in /home/xxx/.ssh/known_hosts:1
debug1: ssh_rsa_verify: signature correct
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug1: Next authentication method: publickey
debug1: Trying private key: /home/xxx/.ssh/id_rsa
debug1: Trying private key: /home/xxx/.ssh/id_dsa
debug1: Next authentication method: keyboard-interactive
Password:
debug1: Authentication succeeded (keyboard-interactive).
debug1: channel 0: new [client-session]
debug1: Requesting <email address hidden>
debug1: Entering interactive session.
debug1: Sending environment.
debug1: Sending env LANG = de_DE.utf8
debug1: Sending subsystem: sftp
Server version: 3
Extension: <email address hidden> <1>
Extension: <email address hidden> <2>
Extension: <email address hidden> <2>
FUSE library version: 2.8.1
nullpath_ok: 0
unique: 1, opcode: INIT (26), nodeid: 0, insize: 56
INIT: 7.13
flags=0x0000007b
max_readahead=0x00020000
   INIT: 7.12
   flags=0x00000011
   max_readahead=0x00020000
   max_write=0x00010000
   unique: 1, success, outsize: 40
unique: 2, opcode: LOOKUP (1), nodeid: 1, insize: 47
LOOKUP /.Trash
getattr /.Trash
[00001] LSTAT
unique: 3, opcode: OPENDIR (27), nodeid: 1, insize: 48
   unique: 3, success, outsize: 32
  [00001] STATUS 33bytes (38ms)
   unique: 2, error: -2 (No such file or directory), outsize: 16
unique: 4, opcode: LOOKUP (1), nodeid: 1, insize: 52
LOOKUP /.Trash-1000
getattr /.Trash-1000
[00002] LSTAT
  [00002] STATUS 33bytes (38ms)
   unique: 4, error: -2 (No such file or directory), outsize: 16
unique: 5, opcode: READDIR (28), nodeid: 1, insize: 80
getdir[0]
[00003] OPENDIR
  [00003] HANDLE 17bytes (38ms)
[00004] READDIR
  [00004] NAME 2203bytes (224ms)
[00005] READDIR
  [00005] STATUS 32bytes (38ms)
[00006] CLOSE
   unique: 5, success, outsize: 736
unique: 6, opcode...

Changed in sshfs-fuse (Ubuntu):
status: Invalid → New
Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

 Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time to make Ubuntu better!

Changed in sshfs-fuse (Ubuntu):
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
the door (thiagomoraesp) wrote :

Solved with:

TCPKeepAlive yes

on ssh_config

Revision history for this message
the door (thiagomoraesp) wrote :

i believe that this option need to come activated by default.

Revision history for this message
bas89 (bas89) wrote :

Thanks #7 for the solution. Will this setting be default?

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

Other bug subscribers

Remote bug watches

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