You are not logged in.
Been using sshfs to mount remote filesystems for years. New to Arch and have just installed it on my "server" box in my office.
The client box is my Mythbox in the living room.
Been trying for hours and it just won't mount from the client. I get prompted for my password and then the infamous "Remote host has disconnected" error message:
I can ssh in fine.
I can sftp in fine.
I installed openssh via pacman but copied over my last working version of my ssh_config and sshd_config files from my previous working configuration.
For your consideration:
sshfs -odebug,sshfs_debug,loglevel=debug tv@192.168.1.2:/mnt/video/miro /mnt/miro
SSHFS version 2.2
executing <ssh> <-x> <-a> <-oClearAllForwardings=yes> <-ologlevel=debug> <-2> <tv@192.168.1.2> <-s> <sftp>
debug1: Reading configuration data /home/tv/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to 192.168.1.2 [192.168.1.2] port 22.
debug1: Connection established.
debug1: identity file /home/tv/.ssh/id_rsa type 1
debug1: Checking blacklist file /usr/share/ssh/blacklist.RSA-2048
debug1: Checking blacklist file /etc/ssh/blacklist.RSA-2048
debug1: Remote protocol version 2.0, remote software version OpenSSH_5.4
debug1: match: OpenSSH_5.4 pat OpenSSH*
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_5.1p1 Debian-6ubuntu2
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-cbc hmac-md5 none
debug1: kex: client->server aes128-cbc 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 '192.168.1.2' is known and matches the RSA host key.
debug1: Found key in /home/tv/.ssh/known_hosts:2
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: Offering public key: /home/tv/.ssh/id_rsa
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug1: Next authentication method: keyboard-interactive
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug1: Next authentication method: password
tv@192.168.1.2's password:
debug1: Authentication succeeded (password).
debug1: channel 0: new [client-session]
debug1: Requesting no-more-sessions@openssh.com
debug1: Entering interactive session.
debug1: Sending environment.
debug1: Sending env LANG = en_US.UTF-8
debug1: Sending subsystem: sftp
debug1: client_input_channel_req: channel 0 rtype exit-signal reply 0
debug1: client_input_channel_req: channel 0 rtype eow@openssh.com reply 0
debug1: channel 0: free: client-session, nchannels 1
debug1: fd 0 clearing O_NONBLOCK
Transferred: sent 1856, received 2104 bytes, in 0.0 seconds
Bytes per second: sent 74270.0, received 84194.1
debug1: Exit status -1
remote host has disconnected
Anyone see anything?
Thanks.
Last edited by whatshisname (2010-05-30 01:59:48)
Offline
Another related issue that might mean something for this problem.
I also cannot log into my Arch server using RSA keys. I always have to use a password.
I definitely have something misconfigured on my Arch box. I do password-less logins all the time at work on my other servers.
Thanks again.
Offline
As far as I remember I had analogous problems when moved from Mandriva to Arch. (Mine was about X forwarding.) Maybe it is just a pseudo-explanation, but I suppose ssh(d) is compiled with different defaults for different distros. So a config file not telling anything about a particular function, finally results in different on/off state of that function. I advice you not to simply transfer the config files, rather take the raw Arch config file, and manually apply all modifications according to your old and working config file.
(In my case I had no X forwarding on Arch with the config file I used under Mandriva with successful X forwarding. Background: the raw Arch config file contained '#XForwarding no', my original Mandriva config file contained '#XForwarding yes' demonstrating the different defaults. The Mandriva config file just told Arch to use its default for X forwarding, whatever it is. I had to take the raw Arch config and manually modify its corresponding line to 'XForwarding yes'.)
I hope it helps.
“First principle, Clarice. Simplicity” – Dr. Hannibal Lecter
Offline
Unbelievable! That was it!
I killed my sshd_config file, reinstalled openssh and everything is working fine.
You'd think after this many years of problem solving computers, I'd have learned that you can never say "Well, that can't be the problem so I don't need to try that."
Thanks, Barto. I have spent hours and hours on this. I know more about ssh now than I ever wanted to know. All because I was being bull-headed.
Offline