My group had a web application running using Elastic Beanstalk. For several months, it worked fine, but now the website shows the error
'radiology-ai-env.eba-wgmpba4k.us-west-2.elasticbeanstalk.com is currently unable to handle this request.'
When I try to rebuild the environment, I get two error messages:
1.) LaunchWaitCondition failed. The expected number of EC2 instances were not initialized within the given time. Rebuild the environment. If this persists, contact support.
2.) Stack named 'awseb-e-pw8nbmshem-stack' aborted operation. Current state: 'CREATE_FAILED' Reason: The following resource(s) failed to create: [AWSEBInstanceLaunchWaitCondition].
I am wondering what can be changed to fix this issue, and would appreciate any help. Thank you so much in advance!! I can follow up with more info if it is helpful.
Related
My application is running on Elastic beanstalk AL2 with docker. It is still up and running, this issue is not user facing and only internal to AWS.
I upgraded to AL2 about 7 months ago and there were no problems. Recently I logged into to Elastic Beanstalk console to look into upgrading the platform. When I clicked on "Configuration" I get an error and redirected back to the applications list.
The error says:
Error
A problem occurred while loading your page: Configuration validation exception: Invalid option value: 'awseb-e-XXXXXXXX-stack-AWSEBSecurityGroup-XXXXXXXX’ (Namespace: 'aws:autoscaling:launchconfiguration', OptionName: 'SecurityGroups'): The security group 'awseb-e-XXXXXXXX-stack-AWSEBSecurityGroup-XXXXXXXX' does not exist
The error before this actually referenced a launch template so when I created a version 2 of the launch template but without the errored security group (as indicated by the UI) then this error message changed to the one we see above.
I tried redeploying thinking new setting need to take effect. Didn't work. Error still present.
I tried creating a new unrelated environment from scratch, but it has the same error message when clicking on Configuration.
I tried cloning production environment but am blocked with the same error message.
I also posted this question here: https://repost.aws/questions/QU4VTSJDyCT7OtIIgPCblUPA/elastic-beanstalk-unable-to-access-environments-configuration-error-a-problem-occurred-while-loading-your-page-configuration-validation-exception
I tried the suggestions but neither worked.
Any ideas on how to fix or debug this further?
Thank you
I tried to create a Google Cloud Composer environment but in the page to set it up I get the following errors:
Service Error: Failed to load GKE machine types. Please leave the field
empty to apply default values or retry later.
Service Error: Failed to load regions. Please leave the field empty to
apply default values or retry later.
Service Error: Failed to load zones. Please leave the field empty to apply
default values or retry later.
Service Error: Failed to load service accounts. Please leave the field
empty to apply default values or retry later.
The only parameters GCP lets me change are the region and the number of nodes, but still lets me create the environment. After 30 minutes the environment crashes with the following error:
CREATE operation on this environment failed 1 day ago with the following error message:
Http error status code: 400
Http error message: BAD REQUEST
Errors in: [Web server]; Error messages:
Failed to deploy the Airflow web server. This might be a temporary issue. You can retry the operation later.
If the issue persists, it might be caused by problems with permissions or network configuration. For more information, see https://cloud.google.com/composer/docs/troubleshooting-environment-creation.
An internal error occurred while processing task /app-engine-flex/flex_await_healthy/flex_await_healthy>2021-07-20T14:31:23.047Z7050.xd.0: Your deployment has failed to become healthy in the allotted time and therefore was rolled back. If you believe this was an error, try adjusting the 'app_start_timeout_sec' setting in the 'readiness_check' section.
Got error "Another operation failed." during CP_DEPLOYMENT_CREATING_STANDARD []
Is it a problem with permissions? If so, what permissions do I need? Thank you!
It looks like more of a temporary issue:
the first set of errors is stating you cannot load the metadata :
regions list, zones list ....
you dont have a clear
PERMISSION_DENIED error
the second error: is suggesting also:
This might be a temporary issue.
I get a message when I am trying to deploy my php app on EC2 using Elastic Beanstalk.
Environment named *** is in an invalid state for this operation. Must be Ready.
I am unable to deploy. The server status is running, Environment Health is OK and no warnings.
How can I resolve this?
Not sure if this is the same case for you but I got the same error when I was under the impression my environment was healthy - I figured out my issue by clicking on "Show all" in the Recent events section, at which point the culprit error logs were displayed.
You should open the "Show all", choose warnings or errors.
Try to detect the service that is the root cause and take the appropriate action.
In my case, it was an EC2 instance that somehow hasn't passed the status check. My solution was to restart the instance and it solved the problem.
Go to Actions -> Rebuild Environment. That solved the problem for me. Hope it helps! AWS Elasticbeanstalk Menu: Actions -> Rebuild
I'm trying several times to deploy a new version of a service on my app engine flexible instance using the sdk and the command gcloud app deploy, but all i get is this error
"ERROR: (gcloud.app.deploy) Error Response: [4] Timed out waiting for
the app infrastructure to become healthy."
.
I Couldn't found any answer about it on the issue tracker of gcp.
On this question, he got the same problem, but no one could answered it.
Any guidance will be very helpfull.
According to the gcp team, this particular error was caused because we reached the "In-use IP addresses" quota limit.
They also said that are working on improve the error messages.
"The engineering team has just created a fix for better quota error
details. There is no ETA for when the fix will be released, but I
would guess it would be in the next version of gcloud."
Over half a year later after Loneck's answer I've got the same error. I guessed it could be anything. This is why I've choosen to delete the project, create a new one in a new zone and deployed it there. Then it worked for me. It might have been any other limitation in the zone that I've choosen at the beginning.
I ran into this and solved it by retrying the deploy 3 times.
I tried to deploy MEAN stack using Google Developers Console, no success. I tried several times, the error was always the same (below). Do you have any idea why it keeps failing?
Your MEAN development stack failed to deploy
Sep 16, 2014 11:34:59 AM
meanDevelopmentFirewall: DEPLOYED
meanStackBox: DEPLOYMENT_FAILED
Replica mean-2jmy failed with status PERMANENTLY_FAILING: Replica State changed to PERMANENTLY_FAILING. Replica was unhealthy 2 consecutive times.
What to do next:
Note the error listed above.
Delete the stack.
Correct the error (if you can).
Try again to deploy the stack.
Get help at Stack Overflow
We just rolled out a fix to our MEAN.io stack deployment today. Please try again at your convenience.