I tried to setup EB for worker tier by using the following command
eb create -t worker
But I receive the following error
2015-11-04 16:44:01 UTC+0800 ERROR Stack named 'awseb-e-wh4epksrzi-stack' aborted operation. Current state: 'CREATE_FAILED' Reason: The following resource(s) failed to create: [AWSEBWorkerCronLeaderRegistry, AWSEBSecurityGroup].
2015-11-04 16:43:58 UTC+0800 ERROR Creating security group named: sg-7ba1f41e failed Reason: Resource creation cancelled
Is there something specific to run the command line ?
I found the eb command line buggy. try to use the web console. much more reliable.
Related
I am creating ASG using the CloudFormation template, the instances created by the autoscaling group are failing to send the success signal to the CloudFormation stack.
This is happening after the system boots up successfully.
There is no problem when am creating Ec2 instances manually but facing the issue from ASG created instances
Here is the error: [Boot Script received the following error:
Cfn-Signal failed to execute]
Thanks in advance for helping me
I am trying to create an application load balancer controller on my EKS cluster by following
this link
When I run these steps (after making the necessary changes to the downloaded yaml file)
curl -o v2_1_2_full.yaml https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.1.2/docs/install/v2_1_2_full.yaml
kubectl apply -f v2_1_2_full.yaml
I get this output
customresourcedefinition.apiextensions.k8s.io/targetgroupbindings.elbv2.k8s.aws configured
mutatingwebhookconfiguration.admissionregistration.k8s.io/aws-load-balancer-webhook configured
role.rbac.authorization.k8s.io/aws-load-balancer-controller-leader-election-role unchanged
clusterrole.rbac.authorization.k8s.io/aws-load-balancer-controller-role configured
rolebinding.rbac.authorization.k8s.io/aws-load-balancer-controller-leader-election-rolebinding unchanged
clusterrolebinding.rbac.authorization.k8s.io/aws-load-balancer-controller-rolebinding unchanged
service/aws-load-balancer-webhook-service unchanged
deployment.apps/aws-load-balancer-controller unchanged
validatingwebhookconfiguration.admissionregistration.k8s.io/aws-load-balancer-webhook configured
Error from server (InternalError): error when creating "v2_1_2_full.yaml": Internal error occurred: failed calling webhook "webhook.cert-manager.io": Post https://cert-manager-webhook.cert-manager.svc:443/mutate?timeout=10s: no endpoints available for service "cert-manager-webhook"
Error from server (InternalError): error when creating "v2_1_2_full.yaml": Internal error occurred: failed calling webhook "webhook.cert-manager.io": Post https://cert-manager-webhook.cert-manager.svc:443/mutate?timeout=10s: no endpoints available for service "cert-manager-webhook"
The load balancer controller doesnt appear to start up because of this and never gets to the ready state
Has anyone any suggestions on how to resolve this issue?
Turns out the taints on my nodegroup prevented the cert-manager pods from starting on any node.
These commands helped debug and led me to a fix for this issue:
kubectl get po -n cert-manager
kubectl describe po <pod id> -n cert-manager
My solution was to create another nodeGroup with no taints specified. This allowed the cert-manager to run.
I want to see logs of my elastic beanstalk environment in the command line, for which I'm doing the following:
eb logs --cloudwatch-logs enable --cloudwatch-log-source instance Humboialpha2021-env
However, I'm seeing the following error:
Enabling instance log streaming to CloudWatch for your environment
After the environment is updated you can view your logs by following the link:
https://console.aws.amazon.com/cloudwatch/home?region=us-east-1#logs:prefix=/aws/elasticbeanstalk/Humboialpha2021-env/
Printing Status:
2021-03-27 16:19:05 INFO Environment update is starting.
2021-03-27 16:19:16 INFO Updating environment Humboialpha2021-env's configuration settings.
2021-03-27 16:19:54 INFO Instance deployment successfully detected a JAR file in your source bundle.
2021-03-27 16:19:57 INFO Instance deployment successfully generated a 'Procfile'.
2021-03-27 16:19:58 ERROR Instance deployment failed. For details, see 'eb-engine.log'.
2021-03-27 16:20:02 ERROR [Instance: i-04fb7a3d67a219ca7] Command failed on instance. Return code: 1 Output: Engine execution has encountered an error..
2021-03-27 16:20:02 INFO Command execution completed on all instances. Summary: [Successful: 0, Failed: 1].
2021-03-27 16:20:02 ERROR Unsuccessful command execution on instance id(s) 'i-04fb7a3d67a219ca7'. Aborting the operation.
2021-03-27 16:20:03 ERROR Failed to deploy configuration.
ERROR: ServiceError - Failed to deploy configuration.
How to fix this?
Trying to deploy an IIS application to AWS Elastic Beanstalk via Visual Studio 2015. Every time we try to deploy it we get the following errors:
Error occurred during build: Command hooks failed
[Instance: i-XXXXXXXX ConfigSet: Infra-WriteRuntimeConfig, Infra-WriteApplication1,
Infra-WriteApplication2, Infra-EmbeddedPreBuild, Hook-PreAppDeploy,
Infra-EmbeddedPostBuild, Hook-EnactAppDeploy, Hook-PostAppDeploy]
Command failed on instance. Return code: 1 Output: null.
Unsuccessful command execution on instance id(s) 'i-XXXXXXXX'. Aborting the operation.
We've tried restarting the Application. We've tried deleting and recreating the Environment and Application. All to no success. Always the same error. I cannot find anything online anywhere that tells how to fix this. Has anyone else run into this problem and found a solution?
The Beanstalk deployment errors are usually quite generic.
To get the root cause, the troubleshooting steps are the ones in AWS Elastic Beanstalk Troubleshooting doc:
Retrieve and investigate EB Logs.
If retrieved logs are not helpful, then SSH to the EC2 instance can be used to get more details or check that the instance config is really what is expected for example.
Before deploying login to the ec2 instance via SSH and do a realtime log fetching
tail -f /var/log/eb-engine.log
and you will get proper error log why the hooks get failed.
I'm trying to create cluster structure using Cloud Formation script. I'm using Bitnami drupal AMI.
Bu the script produces below eror:
WaitCondition received failed message: 'Failed to run cfn-init' for uniqueId: i-4d121a16
Then I connected to instance and checked cfn-init.log:
bitnami#ip-10-58-51-235:/var/log$ cat cfn-init.log
2013-01-01 19:18:23,128 [INFO] Starting new HTTP connection (1): 169.254.169.254
2013-01-01 22:52:17,607 [INFO] Starting new HTTP connection (1): 169.254.169.254
2013-01-01 22:52:17,621 [INFO] Starting new HTTPS connection (1): cloudformation-waitcondition- eu-west-1.s3.amazonaws.com
My AWS Console events like below:
Logical ID PhysicalID Status Reason
mycluster arn:aws:cloudformation:eu-west-1:318730... CREATE_FAILED The following resource(s) failed to create: [WaitCondition]
WaitCondition vgdrobe-WaitCondition-UWEKNUJ8TMT6 CREATE_FAILED WaitCondition received failed message: 'Failed to run cfn-init' for uniqueId: i-59272f1c
WaitCondition vgdrb-WaitCondition-MML6Y6E47WTB CREATE_IN_PROGRESS
WebServerGroup vgdrb-WebServerGroup-1OBJYOSQX8093 CREATE_COMPLETE
I couln't find the problem. Could you help me please?
Kind regards...
Is it possible that the cfn-init scripts are not part of the image?
According to the docs, they're installed as part of the Amazon Linux image, but may not be included by default in other images.
Expanding on what Chris suggested, I had to add the following to get cfn-init working on my CloudFormation script:
"apt-get -y install python-setuptools\n",
"easy_install https://s3.amazonaws.com/cloudformation-examples/aws-cfn-bootstrap-1.0.tar.gz\n",
I found some really useful info about this here: http://smart421.wordpress.com/2012/12/14/aws-cloudformation-and-chef-on-centos/
I also found errors in my UserData caused cfn-init to fail. I got around this by using VS2012 to validate the script before uploading it (as suggested here: How can I quickly and effectively debug CloudFormation templates?).
Hope that helps.