Menu
I'm hosting an application with AWS, using elasticbeanstalk. I'm using the toolbelt to push my application from my local machine. Up until a couple weeks ago, everything was working fine, but recently my changes aren't taking effect. I can see in the aws management console that my application is being pushed and deployed, but changes aren't coming through.
I checked the environment event log to see if anything was new from a typical deployment and the error I'm seeing is
ERROR Update environment operation is complete, but with command timeouts. Try increasing the timeout period. For more information, see troubleshooting documentation.
ERROR During an aborted deployment, some instances may have deployed the new application version. To ensure all instances are running the same version, re-deploy the appropriate application version.
ERROR Failed to deploy application.
ERROR Unsuccessful command execution on instance id(s) 'i-8d88a587'. Aborting the operation.
What is the problem exactly, and what can I do to fix this?
541
Elastic Beanstalk applies an application's lifecycle policy each time you create a new application version, and deletes up to 100 versions each time the lifecycle policy is applied.
Elastic Beanstalk isn't great if you need a lot of environment variables. The simple reason is that Elastic Beanstalk has a hard limit of 4KB to store all key-value pairs. The environment had accumulated 74 environment variables — a few of them had exceedingly verbose names.
There could be several causes of this.
The next troubleshooting step is to download the most recent Elastic Beanstalk logs (either from the web console or with the eb logs command line tool.)
Open /var/log/eb-activity.log and look at the last few lines to determine the exact command that failed.
Examples could be
.ebextensions/ has a bug
112
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
