Silly me, it was a Security Group issue; I was doing the manual ssh test
from my desktop but the workstation creating the server is on a different
subnet. When I updated the security group everything progressed normally.
Thanks very much for all the suggestions, though!
On Thu, Feb 9, 2012 at 8:53 AM, Kevin Harvey email@example.com wrote:
How long are you waiting for sshd to come up there? It can take a minute
On Thu, Feb 9, 2012 at 8:50 AM, mark bradley firstname.lastname@example.org wrote:
I’m trying to bootstrap nodes in EC2 using knife as follows:
knife ec2 server create --flavor m1.large -I ami-1b814f72 -G DevOps -S
DevOps -N foobar -x ec2-user -i /tmp/DevOps.pem -V -V
but it hangs with the following output:
DEBUG: Using configuration from /root/.chef/knife.rb
Instance ID: i-638eea06
Availability Zone: us-east-1b
Security Groups: DevOps
SSH Key: DevOps
Waiting for server…
Public DNS Name: ec2-50-19-18-3.compute-1.amazonaws.com
Public IP Address: 184.108.40.206
Private DNS Name: ip-10-87-1-167.ec2.internal
Private IP Address: 10.87.1.167
Waiting for sshd.
If, however, I manually log in to the instance everything seems available:
$ ssh -i DevOps.pem email@example.com
The authenticity of host ‘ec2-50-19-18-3.compute-1.amazonaws.com(220.127.116.11)’ can’t be established.
RSA key fingerprint is 0e:da:5e:4b:8d:80:7f:ba:63:89:25:ad:dd:b4:ba:a0.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added ‘ec2-50-19-18-3.compute-1.amazonaws.com,18.104.22.168’
(RSA) to the list of known hosts.
__| __|_ ) _| ( / Amazon Linux AMI ___|\___|___|
See /usr/share/doc/system-release/ for latest release notes.
There are 23 security update(s) out of 32 total update(s) available
Is there any way to get more debugging information from knife? Does
anyone know what could be going wrong?