After starting an Ubuntu 14.04 EC2 instance with expanded HD volumes, ssh-ing into it fails with
The EBS expansion process
One of my Ubuntu 14.04 EC2 machines was running low on HD size. In order to solve the problem, I followed AWS's own manual on HD expansion:
- Stopped the machine
- Detached both volumes
- Took a snapshot of both volumes
- Created a larger volumes from the snapshot
- Attached the new volumes and started the machine
In addition to that, I took the opportunity to add an Elastic IP to the machine, if that matters.
After starting the machine, I constantly get a
Connection refused error when ssh-ing to it. I tried ssh from within the VPC to the private IP and from outside. I've used both the
XX.X.XXX.XX IP and the
ec2-XX-X-XXX-XX.compute-1.amazonaws.com DNS name, and both the original
.pem key I've downloaded from AWS upon creation, and the ssh key I've placed in the
.ssh/authorized_keys of the machine.
I get the same response:
ssh: connect to host ec2-XX-X-XXX-XX.compute-1.amazonaws.com port 22: Connection refused
Notes / What have I tried
- I have connected the volumes to another instance and checked them. The files are there.
- I tried removing from the
- I have tried connecting to the machine using the Java client in the EC2 console.
- I have tried connecting the original volumes to the machine (before expansion). I still get
- The root EBS volume is connected at
Update: Issue solved. Thanks a bunch to everybody here!