hello miklos,

it seems that it's all a bit more complicated than i thought. the problem i described in my last mail was caused by the fact that we're erroneously worked with shfs which is not the same as sshfs.

now we're on the right path but there is still a number of problems.

this is what happens and what the debug messages are (hope you can understand them because i had to translate them from german into english...):

$ sshfs -d -osshfs_debug apacheremote@host: mountdirectory
    Password: xxxxx

    Server version: 3
    unique: 2, opcode: INIT (26), nodeid: 0, insize: 44
    INIT: 1.0
      INIT: 7.5
      unique: 2, error: 0 (Success), outsize: 24


That's it. Nothing happens anymore until you Ctrl-C the process.
Running the command without the debug options shows the prompt and mount shows that the devices have been mounted succesfully:

$ mount
    sshfs#apacheremote@host: on /home/admin/mountdirectory type fuse        
    (rw,nosuid,nodev,large_read,max_read=65536,user=admin)


BUT using "ls" in the parent directory causes the following error message:

   ls: mountdirectory: The program aborted the connection.


$ ls mountdirectory

ls: mountdirectory: The socket is not connected

is there a general problem with ls?



here are some additional informations about the machine:

$ sshfs -V
SSHFS version 1.6
FUSE library version: 2.5.3
fusermount version: 2.5.3
using FUSE kernel interface version 7.5

$ uname -r
2.4.27-2-386


Miklos Szeredi schrieb:
i'm not sure if this topic has already been discussed because i found
exactly the same question at the FAQ section in the FUSEWiki
(http://fuse.sourceforge.net/wiki/index.php/SshfsFaq). unfortunately
there is no answer posted.

the problem is that sshfs hangs after it has been running for some time.
at first i thought it might have something to do with the amount of
traffic but obviously it also happens when there is no traffic at all.

i'm running SSHFS version 1.6 on a debian 3.1 stable machine. mounting
the devices works fine and even when it hangs the mount command still
returns correct values.

for me this is a critical problem as i use sshfs to mount the apache
webroot into a production server. so i would be very pleased if someone
could tell me whether this is a known problem and if there is a
workaround or a bugfix or anything else i could do?
    

It's not a known problem.  Can you please run with debugging enabled?

  sshfs -d -osshfs_debug ...


Thanks,
Miklos

  

-- 
schönen gruß,
alexander thomas

Fachhochschule für Technik und Wirtschaft
FB 4, Forschungsgruppe »INKA«
Treskowallee 8
10313 Berlin

Fon:  +49-30-5019-2331
Fax:  +49-30-5019-2494

mailto:a.thomas@fhtw-berlin.de
http://inka.f4.fhtw-berlin.de