My Amazon EC2 instance's openssh server fails on boot ever since I scaled my instance.

I have tried following these instructions here: https://stackoverflow.com/questions/14026148/running-ec2-instance-suddenly-refuses-ssh-connection

I have detached my EBS volume and attached it to a new instance of the same OS in the same region. I can see that there are two volumes attached to it before I start it up.

Once it starts, it experiences the exact same problem my other instance is experiencing where I cannot SSH into it.

I then detach the "bad" volume and reboot the instance and it works as expected.

What am I doing incorrectly that is causing the instance OS to run openssh off of the "bad" volume instead of the new volume associated with it as the root volume?

  • What do the ssh logs say? – EEAA Apr 11 '15 at 19:27
  • I can't see them because I can't access the server through SSH to read them. I get "connection refused" when attempting to connect. I looked at the AWS system log and it shows openssh trying to start about 8 times and then failing. – AJStacy Apr 11 '15 at 19:33
  • Well there's really nothing any of us can do to help you other than suggesting that you either 1) Re-build a new server from the ground up, mount your current EBS volume to the new server, and restore your data or 2) Mount the current EBS vol to a new server and fix up whatever's broken. – EEAA Apr 11 '15 at 19:35
  • Since you "scaled" your instance? What specifically did you change? – Michael - sqlbot Apr 12 '15 at 0:52

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.