Repost with images.
Begin forwarded message: > From: Simon Dredge <[email protected]> > Date: April 24, 2015 at 10:53:09 AM PDT > To: "[email protected]" <[email protected]> > Subject: FW: Problems encountered when installing Clearwater on AWS EC2 > > > > From: Eleanor Merry > Sent: Friday, April 24, 2015 10:12 AM > To: LIN David DL; [email protected] > Subject: RE: Problems encountered when installing Clearwater on AWS EC2 > > Hi David, > > If you’ve created the instances through chef, but terminated them through > AWS, then this leaves the chef client in a bad state and it can’t create any > new instances. You’ll need to delete the instances in chef as well to be able > to move on. > You can do this by logging onto the chef server web UI as the admin user, and > then deleting any nodes you’ve created from the Nodes tab and the Clients tab. > > You’ll then be able to create a new deployment. If this fails again, can you > please send me the logs? The location of the logs is shown when the instance > is being created, e.g.: > > Waiting for server...INFO: Bootstrapping clearwater-ralf-1, logs can be found > at > /home/ubuntu/chef/plugins/knife/../../logs/clearwater-ralf-1-bootstrap-1429769747.log > > Ellie > > From: LIN David DL [mailto:[email protected]] > Sent: 24 April 2015 01:57 > To: Eleanor Merry; [email protected] > Subject: RE: Problems encountered when installing Clearwater on AWS EC2 > > Hi Ellie, > > Great thanks for the reply! > > I’ve managed to manually install Chef server and Chef client from the > official Chef website, and the “Creating a deployment environment” step is > done. > > Now I’m at the final step “Creating a deployment with Chef”. Below is the > command I used: > knife deployment resize -E clearwater --ralf-count 1 --sprout-count NUM 2 –V > > However it failed. See the output below. From AWS console, the instances were > successfully created, but don’t know why the deployment failed. > > Then I terminated all the created instances, and try the deployment again. It > failed because the security groups (created by the previous try) already > exist. > > Then I tried to delete the security groups, but unfortunately some were > referenced by the already terminated instances. Since the instances were > terminated, I could not change its security group assignment either. So seems > there is nothing I can do now, please advise how to move on. Thanks a lot! > > > Image: ami-d017b2b8 > Region: us-east-1 > Availability Zone: us-east-1a > Security Groups: clearwater-base, clearwater-internal-sip, clearwater-sprout > Tags: {"Name"=>"clearwater-sprout-1"} > SSH Key: linxin1982 > > Waiting for serverInstance ID: i-8b624d77 > Flavor: m1.small > Image: ami-d017b2b8 > Region: us-east-1 > Availability Zone: us-east-1a > Security Groups: clearwater-base, clearwater-homestead > Tags: {"Name"=>"clearwater-homestead-1"} > SSH Key: linxin1982 > > Waiting for server...INFO: Bootstrapping clearwater-ralf-1, logs can be found > at > /home/ubuntu/chef/plugins/knife/../../logs/clearwater-ralf-1-bootstrap-1429769747.log > .....Instance ID: i-73634c8f > Flavor: m1.small > Image: ami-d017b2b8 > Region: us-east-1 > Availability Zone: us-east-1a > Security Groups: clearwater-base, clearwater-ralf > Tags: {"Name"=>"clearwater-ralf-1"} > SSH Key: linxin1982 > > Waiting for serverINFO: Bootstrapping clearwater-ellis-1, logs can be found > at > /home/ubuntu/chef/plugins/knife/../../logs/clearwater-ellis-1-bootstrap-1429769748.log > .....Instance ID: i-8c624d70 > Flavor: m1.small > Image: ami-d017b2b8 > Region: us-east-1 > Availability Zone: us-east-1a > Security Groups: clearwater-base, clearwater-ellis > Tags: {"Name"=>"clearwater-ellis-1"} > SSH Key: linxin1982 > > Waiting for > server......................................................................................................................... > Public DNS Name: ec2-52-6-110-86.compute-1.amazonaws.com > Public IP Address: 52.6.110.86 > Private DNS Name: ip-172-31-27-94.ec2.internal > Private IP Address: 172.31.27.94 > > Waiting for sshd... > Public DNS Name: ec2-52-6-110-85.compute-1.amazonaws.com > Public IP Address: 52.6.110.85 > Private DNS Name: ip-172-31-24-12.ec2.internal > Private IP Address: 172.31.24.12 > > Waiting for sshd... > Public DNS Name: ec2-52-6-110-56.compute-1.amazonaws.com > Public IP Address: 52.6.110.56 > Private DNS Name: ip-172-31-23-75.ec2.internal > Private IP Address: 172.31.23.75 > > Waiting for sshd.. > Public DNS Name: ec2-52-5-21-77.compute-1.amazonaws.com > Public IP Address: 52.5.21.77 > Private DNS Name: ip-172-31-18-18.ec2.internal > Private IP Address: 172.31.18.18 > > Waiting for sshd.. > Public DNS Name: ec2-52-6-109-183.compute-1.amazonaws.com > Public IP Address: 52.6.109.183 > Private DNS Name: ip-172-31-22-153.ec2.internal > Private IP Address: 172.31.22.153 > > Waiting for sshd... > Public DNS Name: ec2-52-6-99-238.compute-1.amazonaws.com > Public IP Address: 52.6.99.238 > Private DNS Name: ip-172-31-27-77.ec2.internal > Private IP Address: 172.31.27.77 > > Waiting for sshd. > Public DNS Name: ec2-52-6-109-111.compute-1.amazonaws.com > Public IP Address: 52.6.109.111 > Private DNS Name: ip-172-31-23-136.ec2.internal > Private IP Address: 172.31.23.136 > > Waiting for sshd...........done > done > done > done > done > done > done > ERROR: Failed to create node: exit > ERROR: Failed to create node for clearwater-bono-1 > INFO: Bootstrapping clearwater-bono-1, logs can be found at > /home/ubuntu/chef/plugins/knife/../../logs/clearwater-bono-1-bootstrap-1429769834.log > ERROR: Failed to create node: exit > ERROR: Failed to create node for clearwater-ralf-1 > INFO: Bootstrapping clearwater-ralf-1, logs can be found at > /home/ubuntu/chef/plugins/knife/../../logs/clearwater-ralf-1-bootstrap-1429769834.log > ERROR: Failed to create node: exit > ERROR: Failed to create node for clearwater-sprout-2 > INFO: Bootstrapping clearwater-sprout-2, logs can be found at > /home/ubuntu/chef/plugins/knife/../../logs/clearwater-sprout-2-bootstrap-1429769834.log > Instance ID: i-09624df5Instance ID: i-4a614eb6 > Flavor: m1.small > Image: ami-d017b2b8 > Region: us-east-1 > > Flavor: m1.smallAvailability Zone: us-east-1a > Security Groups: clearwater-base, clearwater-ralf > Tags: {"Name"=>"clearwater-ralf-1"} > Image: ami-d017b2b8 > Region: us-east-1 > SSH Key: linxin1982 > Availability Zone: us-east-1a > > Waiting for server > Security Groups: clearwater-base, clearwater-internal-sip, clearwater-bono > Tags: {"Name"=>"clearwater-bono-1"} > SSH Key: linxin1982 > > Waiting for server..Instance ID: i-4b614eb7 > Flavor: m1.small > Image: ami-d017b2b8 > Region: us-east-1 > Availability Zone: us-east-1a > Security Groups: clearwater-base, clearwater-internal-sip, clearwater-sprout > Tags: {"Name"=>"clearwater-sprout-2"} > SSH Key: linxin1982 > > Waiting for server................ERROR: Failed to create node: exit > ERROR: Failed to create node for clearwater-ellis-1 > .INFO: Bootstrapping clearwater-ellis-1, logs can be found at > /home/ubuntu/chef/plugins/knife/../../logs/clearwater-ellis-1-bootstrap-1429769841.log > ..Instance ID: i-55624da9 > Flavor: m1.small > Image: ami-d017b2b8 > Region: us-east-1 > Availability Zone: us-east-1a > Security Groups: clearwater-base, clearwater-ellis > Tags: {"Name"=>"clearwater-ellis-1"} > SSH Key: linxin1982 > > Waiting for server............................................... > Public DNS Name: ec2-52-5-237-226.compute-1.amazonaws.com > Public IP Address: 52.5.237.226 > Private DNS Name: ip-172-31-24-87.ec2.internal > Private IP Address: 172.31.24.87 > > Waiting for sshd.. > Public DNS Name: ec2-52-6-33-112.compute-1.amazonaws.com > Public IP Address: 52.6.33.112 > Private DNS Name: ip-172-31-28-205.ec2.internal > Private IP Address: 172.31.28.205 > > Waiting for sshd........ > Public DNS Name: ec2-52-6-100-119.compute-1.amazonaws.com > Public IP Address: 52.6.100.119 > Private DNS Name: ip-172-31-16-101.ec2.internal > Private IP Address: 172.31.16.101 > > Waiting for sshd....ERROR: Failed to create node: exit > ERROR: Failed to create node for clearwater-sprout-1 > ERROR: Failed to create node: exit > ERROR: Failed to create node for clearwater-homestead-1 > .. > Public DNS Name: ec2-52-5-88-113.compute-1.amazonaws.com > Public IP Address: 52.5.88.113 > Private DNS Name: ip-172-31-26-128.ec2.internal > Private IP Address: 172.31.26.128 > > Waiting for sshd.....done > done > .done > done > > ERROR: Failed to create node: exit > ERROR: Failed to create node for clearwater-bono-1 > ERROR: Failed to create node: exit > ERROR: Failed to create node for clearwater-ralf-1 > > > ERROR: Failed to create node: exit > ERROR: Failed to create node for clearwater-sprout-2 > > > ERROR: Failed to create node: exit > ERROR: Failed to create node for clearwater-ellis-1 > > ” > > Thanks, > David > > From: Eleanor Merry [mailto:[email protected]] > Sent: 2015年4月24日 1:19 > To: LIN David DL; [email protected] > Subject: RE: Problems encountered when installing Clearwater on AWS EC2 > > Hi David, > > Thanks for raising this! I agree the documentation is out of date, and I’m > currently investigating what the new install instructions are. > > Ellie > > From: LIN David DL [mailto:[email protected]] > Sent: 22 April 2015 08:34 > To: [email protected] > Subject: Problems encountered when installing Clearwater on AWS EC2 > > Hi, > > I’m installing Clearwarter on AWS EC2, but encountered some problems. Can > anyone help? Thanks a lot! > > > > > I’m following the “Automated Install” instructions listed in the following > link: > http://clearwater.readthedocs.org/en/latest/Automated_Install/index.html > > The first step fails, Seems the steps to install Chef Server and Chef Client > is out of date. > > When I tried to install Chef Server, it shows I need to install dependents > first. I tried to install the dependents but also failed, some packages it > depends do not exist at all. > > sudo apt-get install chef-server -y > > > > > Then I go to Chef website and manually downloaded and installed the latest > version of Chef chef-server-core_12.0.8-1_amd64.deb. > The installation was successful. But the following steps described in the > manual could not be performed: > 1. It does not promote me to input Chef Server URL. > 2. It does not promote me to set password for RabbitMQ server and WebUI. > I think there is no WebUI components in this version of Chef Server. > 3. 4040 and 4000 TCP ports are not opened. Seem this version of Chef > Server use other ports instead of 4040 and 4000. > 4. There is no such file /etc/chef/validation.pem > > I also encountered similar issue when installing Chef Client: > > It depends on chai, which does not exist. > > > > > Can anyone tell me how to install Clearwater on the latest version of Chef, > or does anyone have the package of old version of Chef which I can use? > Thanks a lot! > > Thanks, > David > _______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/listinfo/clearwater
