No, it shouldn't be. But I don't know what is actually happening during 'waiting for sshd,' so on the off chance there's some additional communication there I thought I'd suggest it.--Michael F. Weinberg | Director of Operationshttp://heavywaterops.com | @heavywateropsOn Fri, Mar 6, 2015 at 2:29 PM, Michael Lindsay < " target="_blank"> > wrote:Hi again Michael :-) I'm new to VPC, but I feel like I've poured over all the settings there. Would the behavior be different with knife than ssh on the same workstation in this regard?On Fri, Mar 6, 2015 at 2:19 PM, Michael Weinberg < " target="_blank"> > wrote:Hi Michael,I generally use Cloudformation for all my VPC instances, so have not attempted a direct bootstrap. Have you confirmed that the inbound and outbound security group and ACL rules allow traffic both directions on 22, 80, 443, and the ephemeral ports?--Michael F. Weinberg | Director of Operationshttp://heavywaterops.com | @heavywateropsOn Fri, Mar 6, 2015 at 2:16 PM, Michael Lindsay < " target="_blank"> > wrote:Hello everyone…
I’m attempting my first knife ec2 create commands for building instances inside a VPC.
The problem I'm facing is that "Waiting for sshd access to become available...." Never completes. What's weird (and flies in the face of what I thought was going on) is that while I'm watching little dots appear, in another terminal window on the same workstation, using the same identity file, user, and I think hostname (EIP) that the knife command is using, I CAN ssh into the instance.
Any ideas what might cause this?- Michael
Archive powered by MHonArc 2.6.16.