[SOLVED] problems with sshfs after ssh/ssl upgrades - slackware 14.2
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
problems with sshfs after ssh/ssl upgrades - slackware 14.2
here an sshfs problem : after i upgraded ssh/ssl packages on several slackware v14.2 boxes including the main file server i am unable to use sshfs which worked perfectly fine before. sshfs just hangs - till i press Ctrl-C. all other ssh functions are fine, passwordless in all directions, from any machine to any machine. in the meantime i rebooted all machines as restarting sshd didn't help much. all ssh specific user files should be fine i believe. here the command i use :
the only semi-helpful error message i see is on the server to which i like to connect with sshfs - and only if i press Ctrl-C kind of timely a few seconds after invoking the sshfs command :
sshd[7752]: Did not receive identification string from IP_NUMBER port A_PORT_NUMBER
the /etc/mtab entry seems to list the mounted remote directory but this is actually not the case as df or mount don't show such.
thanks, glorsplitz, for your input.
i actually had the SBo sshfs-fuse package removed right before as its purpose was confusing to me in view of the original Slack sshfs/fuse packages. now, following your suggestion, i recompiled and re-installed sshfs-fuse-2.8-x86_64-1_SBo again - but the result is the same : no luck, no sshfs mounts whatsoever ! but you are right, in the past i had all those ssh/ssl/sshf/fuse packages installed, and sshfs worked just fine...now not anymore...
meanwhile i am wondering if my IPS modem plays a role here : the main server is a VPS out on the web on a public IP while my sshfs clients are behind this modem firewall whose port-forwarding service gets outside ssh calls forwarded to a client in question. but then again - nothing changed except for those ssh/ssl package updates from Slackware64 current...
i tried other sshfs option without success such as :
in any case, i can include/exclude among these three packages whichever i want - no difference : sshfs fails to mount !
lastly, i just tried the same scenario with another slackware box i have out there on the web (no IPS modem interfering with some obscure firewall settings) - and also here the same problem : no sshfs mount possible !
what's wrong here ? as said - a few days ago everything was just fine !
UPDATE : i am able to mount with sshfs any directory from any SERVER to any mount point on any CLIENT - except for the mounting of home directories on home directory mount points ! so, no success so far with something that worked just fine before the ssh/ssl/sshfs upgrades on my Slackware 14.2 boxes.
- is the problem with some new feature(s) with the /etc/ssh/sshd_conf file ?
- is the problem between ssh and sshfs versions ?
- is the problem with some file/directory permission settings ?
- is the problem with some new and more strict ssh requirements ?
i desperately need to get this fixed - a truly big project is on hold because of this silly issue ! thanks, bye, pisti
dear ondoho, thank you for your reply & suggestions ! here my answers :
0) ssh works just fine password-less in all directions - from serverA to serverB and vice versa, and criss-cross between an additional four other machines.
1) now, sshfs works fine too for all scenarios incl password-less mounts and mixed-users mounts (as long as no home2home mounts are used) such as :
^CKilled by signal 2.
remote host has disconnected
sent: 12 messages, 243 bytes
received: 12 messages, 1368 bytes
rtt min/max/avg: 9ms/10ms/9ms
num connect: 1
userX@serverB:~$ ls ~/MNT2/
userX@serverB:~$ df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 4083228 708 4082520 1% /run
devtmpfs 4078300 0 4078300 0% /dev
/dev/sda1 94126244 57309308 32013136 65% /
tmpfs 4083228 68084 4015144 2% /dev/shm
cgroup_root 4083228 0 4083228 0% /sys/fs/cgroup
cgmfs 100 0 100 0% /run/cgmanager/fs
userX@serverB:~$ more /etc/mtab
/dev/sda1 / ext4 rw 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /dev/shm tmpfs rw 0 0
gvfsd-fuse /home/userX/.gvfs fuse.gvfsd-fuse rw,nosuid,nodev,user=userX 0 0
userX@serverB:~$ fusermount -u ~/MNT2/
fusermount: entry for /home/userX/MNT2 not found in /etc/mtab
2) when i try a homeA-to-homeB mount (= mounting userX's homeA@serverA onto userX's homeB@serverB) - or vice versa, or any other combination between the 6 machines, and actually with regular passwords or password-less - then the sshfs process will stall and actually makes 'df' commands or login attempts as userX in another terminal hang for ever - till i terminate the sshfs call with Ctrl-C. here with log output :
Code:
userX@serverB:~$ sshfs serverA:. ~/ -p portA -o nonempty,sshfs_debug,debug,loglevel=debug -C -d -f
SSHFS version 2.8
FUSE library version: 2.9.5
nullpath_ok: 0
nopath: 0
utime_omit_ok: 0
executing <ssh> <-x> <-a> <-oClearAllForwardings=yes> <-oPort=portA> <-ologlevel=debug> <-oCompression=yes> <-2> <serverA> <-s> <sftp>
... waiting ... waiting ...
^C
userX@serverB:~$ df
df: /home/userX/.gvfs: Transport endpoint is not connected
df: /home/userX: Transport endpoint is not connected
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 4083228 708 4082520 1% /run
devtmpfs 4078300 0 4078300 0% /dev
/dev/sda1 94126244 57308396 32014048 65% /
tmpfs 4083228 37380 4045848 1% /dev/shm
cgroup_root 4083228 0 4083228 0% /sys/fs/cgroup
cgmfs 100 0 100 0% /run/cgmanager/fs
userX@serverB:~$ ls ~/
/bin/ls: cannot access '/home/userX/': Transport endpoint is not connected
userX@serverB:~$ more /etc/mtab
/dev/sda1 / ext4 rw 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /dev/shm tmpfs rw 0 0
encfs /home/pisti/enyem fuse.encfs rw,nosuid,nodev,user=pisti 0 0
gvfsd-fuse /home/userX/.gvfs fuse.gvfsd-fuse rw,nosuid,nodev,user=userX 0 0
serverA:. /home/userX fuse.sshfs rw,nosuid,nodev,user=userX 0 0
userX@serverB:~$ fusermount -u ~/
userX@serverB:~$ fusermount -u ~/
fusermount: entry for /home/userX not found in /etc/mtab
userX@serverB:~$ more /etc/mtab
/dev/sda1 / ext4 rw 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /dev/shm tmpfs rw 0 0
encfs /home/pisti/enyem fuse.encfs rw,nosuid,nodev,user=pisti 0 0
gvfsd-fuse /home/userX/.gvfs fuse.gvfsd-fuse rw,nosuid,nodev,user=userX 0 0
userX@serverB:~$ ls ~/
MNT2/ test
userX@serverB:~$
3) and here the corresponding /var/log/{syslog,messages} output on serverB :
Code:
Mar 9 13:26:40 serverB sshd[18754]: Connection from serverA port ArbitraryPort on serverB port portB
Mar 9 13:27:52 serverB sshd[18754]: Did not receive identification string from serverA port ArbitraryPort
i hope this helps... thanks much for looking into this ssh/sshfs issue ! bye, pisti
CORRECTION : the syslog/messages CODE field in my last reply is in parts incorrect as i mixed up serverA with serverB (while hiding my real IP and port numbers). i am very sorry for this confusion in the syslog/messages field !
here the correct statement in a new run using home2home sshfs in terminal#1 (with ssh credentials in a separate directory) :
login for userX in a new terminal#2 is impossible as long as the sshfs process in terminal#1 is not terminated with Ctrl-C. equally blocked are temporarily 'df' and similar commands - even for root.
here the corresponding syslog/messages output on serverA (port number AnyPortX appears arbitrary as it does not correspond to Server's PortA nor to ServerB's PortB - i guess it doesn't have to) :
Code:
Mar 12 17:41:51 serverA sshd[14326]: Connection from serverB port AnyPortX on serverA port PortA
Mar 12 17:42:54 serverA sshd[14326]: Did not receive identification string from serverB port AnyPortX
please, keep in mind that all SSH functions and all non-home2home SSHFS commands work flawlessly...
ok, i got my SSHFS problem finally solved - with the help of Szeredi Miklos (former maintainer of SSHFS and more) who pointed out some features i wasn't aware off. as usual, it boils down to RTFM... :
Quote:
IdentityFile & UserKnownHostsFile
here my steps in short :
0) add new USER0 on CLIENT, create /home/.sshfs/USER0
1) make sure USER0 has pswdless ssh access from SERVER to SERVER
2) rsync ~/.ssh/ files from SERVER to /home/.sshfs/USER0/.ssh/ on CLIENT
3) make sure USER0 has pswdless ssh access from CLIENT to SERVER
dev/sda1 on / type xfs (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
tmpfs on /dev/shm type tmpfs (rw)
USER0@SERVER_IP:/home/USER0 on /home/USER0 type fuse.sshfs (rw,nodev,noatime,default_permissions,allow_other)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
