Unknown ssh login error, hangs for unknown reason

1

I'm trying to log into a VM instance using, but for some reason it's hanging at:

$ mforde@igsb:~$ ssh -vvv -l ubuntu -i ~/.ssh/mf-half.pem 172.16.215.255
OpenSSH_6.6.1, OpenSSL 1.0.1f 6 Jan 2014
debug1: Reading configuration data /etc/ssh/ssh_config 
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to 172.16.215.255 [172.16.215.255] port 22.
debug1: Connection established.
debug3: Incorrect RSA1 identifier
debug3: Could not load "/home/mforde/.ssh/mf-half.pem" as a RSA1 public key
debug1: identity file /home/mforde/.ssh/mf-half.pem type -1
debug1: identity file /home/mforde/.ssh/mf-half.pem-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.6

The key worked fine until this weekend, and works fine with other VMs. Also the VM successfully responds to pings.

Any suggestions?

Martin James

Posted 2016-07-11T14:54:06.220

Reputation: 35

Not sure I'm seeing any problems with the log you've provided. Seems to be just a normal key based authentication for ssh v2 and not v1. Do you have any more log? And can you access the machine at 172.16.215.255 to check it's sshd_config? – jehad – 2016-07-11T15:29:07.000

Yea, key is fine too. No more log. That's where it hangs, and it's a VM so there's no physical access. – Martin James – 2016-07-11T15:32:04.650

It's really weird. – Martin James – 2016-07-11T15:32:27.267

Yeah. It's like the remote machine is there, but not running an ssh server. I expect the next line of the log to tell you what is the "remote" ssh version and software, but if the log ends at the local information, it's like there is no ssh service on the VM... sorry, but I have to say "have you tried turning it off and on again?" :-) That will certainly restart the ssh service. – jehad – 2016-07-11T15:43:14.703

yea, that's the next step. however i have a scratch space mounted to the VM so I'm afraid of losing data. well it's not like i can get to the data anyway, so it's a wash. maybe i can make a copy of the volume. – Martin James – 2016-07-11T15:47:19.343

Unless you have some other way to get into the VM (telnet or your VM console; e.g. "show" in virtualbox), I'm afraid you might be out of luck and you'll just have to sacrifice the data. – jehad – 2016-07-11T16:01:11.580

Answers

0

Your VM IP address seems a little strange because it ending with 255 like a broadcast address. Are you using a /16 netmask? Can you ping it? Do you have any local console on that VM by the way?

Can you try to delete this VM RSA key from your trusted keys list on the local machine? Maybe it was changed and it's the reason why you can't login again.

Tim Connor

Posted 2016-07-11T14:54:06.220

Reputation: 25

If that was the problem, then the OP would not be able to connect at all. Note that for the past two decades, with CIDR, netmasks can be of any length. RFC 1918 reserves 172.16.0.0/12, but that space can be divided in any way desired. – a CVn – 2016-07-13T15:27:32.463

Asked: 2016-07-11T14:54:06.220

Viewed: 72 times

Active: 2016-07-13T14:43:46.993