1

After having used the VM for several days, I decided to restart the VM so that I can do some performance bench marking with minimal processes running. The VM did come up but I am no longer able to access it through Putty or browser based SSH. The private/public keys are all in place and they are the same ones that were used to get access before.

I get the following error when using the Google provided browser based SSH window..

Connection Failed We are unable to connect to the VM on port 22. Learn more about possible causes of this issue.

My colleagues who used to have access to the same machines are also not able to access it anymore. So my client machine isn't the problem. The VM instances dashboard says the instance is running.

Any thoughts on what could have gone wrong and how to debug this? The log files that I can access from the VM instances dashboard don't indicate any errors.

Thanks

  • I tried the netcat command to test the port accessibility as follows: nc -zv -w 10 x.x.x.x 80 20 22 where x.x.x.x is my external IP address..I got a bunch of connection timeout messages back. Something is wrong at the network level it looks like. – ravi condamoor Nov 21 '17 at 22:55
  • How did you reboot the VM? From inside the VM or from the web console? Have you looked at the serial console for any clues? Could you have broken one of the scripts used during boot? If all else fails you can attach the virtual disk of your failing instance as secondary disk on a working instance to look at the logfiles on disk. – kasperd Nov 21 '17 at 23:12
  • Started the VM from the web console. I may have found the problem...Recently I increased the boot disk size and attached a new file system (sda2) to use the increased space..The serial console shows the following error: 3610.091958] EXT4-fs (sda2): Unrecognized mount option "deafults" or missing value You are in emerg Cannot open access to console, the root account is locked. See sulogin(8) man page for more details. How do I recover from this? – ravi condamoor Nov 21 '17 at 23:23
  • If I can get access to /etc/fstab file, I can fix this error. – ravi condamoor Nov 21 '17 at 23:29
  • 2
    For future reference if you need to access the machine but cannot SSH, you can access via the serial console by following the advice in my answer to this question stackoverflow.com/questions/47123487/… – neilH Nov 22 '17 at 16:39

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.