Chef infra 厨师和刀子-在ec2上启动一个实例时,刀子挂在一个上面,有三个刀子作业

Chef infra 厨师和刀子-在ec2上启动一个实例时,刀子挂在一个上面,有三个刀子作业,chef-infra,Chef Infra,随机的,刀似乎挂着。我使用下面的命令启动了三个ami warning: commands will be executed using /bin/sh job 106 at Thu Apr 5 20:35:00 2012 knife ec2 server create -r "role[redis_server]" -N redis_singapore_development_1_1_1333629300 -E development --region ap-southeast-1 -Z ap

随机的,刀似乎挂着。我使用下面的命令启动了三个ami

warning: commands will be executed using /bin/sh
job 106 at Thu Apr  5 20:35:00 2012
knife ec2 server create -r "role[redis_server]" -N redis_singapore_development_1_1_1333629300 -E development --region ap-southeast-1 -Z ap-southeast-1a -I ami-c4622596 --flavor t1.micro -G redis -x ubuntu -S sg_development -i /home/ubuntu/.ec2/sg_development.pem > /tmp/redis_singapore_development_1_1_1333629300
warning: commands will be executed using /bin/sh
job 107 at Thu Apr  5 20:36:00 2012
knife ec2 server create -r "role[redis_server]" -N redis_singapore_development_1_2_1333629300 -E development --region ap-southeast-1 -Z ap-southeast-1a -I ami-c4622596 --flavor t1.micro -G redis -x ubuntu -S sg_development -i /home/ubuntu/.ec2/sg_development.pem > /tmp/redis_singapore_development_1_2_1333629300
warning: commands will be executed using /bin/sh
knife ec2 server create -r "role[nginx_server]" -N bidder_singapore_development_1_1_1333629300 -E development --region ap-southeast-1 -Z ap-southeast-1a -I ami-c4622596 --flavor t1.micro -G nginx -x ubuntu -S sg_development -i /home/ubuntu/.ec2/sg_development.pem > /tmp/bidder_singapore_development_1_1_1333629300job 108 at Thu Apr  5 20:37:00 2012
两个会完成,一个会卡住。下面是挂刀作业的输出。所有这三只靴子在大约20%的时间里都能工作。刀有问题吗?我甚至试着在执行命令之间等待60秒,但都无济于事

Waiting for server............
Public DNS Name: ec2-122-248-207-247.ap-southeast-1.compute.amazonaws.com
Public IP Address: 122.248.207.247
Private DNS Name: ip-10-131-22-222.ap-southeast-1.compute.internal
Private IP Address: 10.131.22.222

Waiting for sshd.done
Bootstrapping Chef on ec2-122-248-207-247.ap-southeast-1.compute.amazonaws.com

由于某些原因,ssh demon的启动没有完成,或者刀子实例无法ssh到box。我经历过这两种情况对我的影响。你需要做一些工作来弄清楚这里发生了什么

第一步是确定ssh是否已启动并在机箱上运行。作为第一步,我将查看您的AWS控制台,并查看它为所讨论的实例显示了什么


我也会增加刀的冗长程度。我总是使用“-VV”选项来获得尽可能多的细节。

在我的情况下,这是由于ssh端口(22)在我的网络上被阻塞。也许下次再检查一下你是否在防火墙后面