CODEWITHSUNDEEP
ruby-on-railsamazon-ec2deploymentamazon-elastic-beanstalk
Israel Barba
Israel Barba

Reputation: 1494

Why Amazon Elastic Beanstalk takes a long time to update my deploy?

I have Amazon EB. with (Puma, Nginx) 64bit Amazon Linux 2014.09 v1.0.9 running Ruby 2.1 (Puma).

Suddenly when I deployed my project send the next error in my terminal: ERROR: Timed out while waiting for command to Complete

Note: Before didn't happen.

I see the event in the console and this is the log: Update environment operation is complete, but with command timeouts. Try increasing the timeout period. For more information, see troubleshooting documentation.

I'v already incrementing the time without success.

option_settings:
  - namespace: aws:elasticbeanstalk:command
    option_name: Timeout
    value: 1800

The Health takes a long time to put it in green (aprox, 20 min), and then it takes other long time for updating the instance with the new changes (aprox, other 20 min), (I have only one instance).

How can I see other logs?

Upvotes: 10

Views: 9098

Answers (2)

Israel Barba
Israel Barba

Reputation: 1494

The problem was the RAM in the instance, so I had to change that instance by other bigger.

Upvotes: 2

biobirdman
biobirdman

Reputation: 4120

This seems like rather common problem with elasticbeanstalk. In short your EC2 instance is going haywired. What you can do is to terminate the EC2 instance on the EC2 dashboard and the loader balancer will start new instance and that may save your problem. To minimise any down time you may start the new instance first and then terminate your older instance. Just be wary that you will lose any ephemeral data and you may have to reinstall certain dependencies (if they are not in your ebextensions 0

Let me know if you need any more help. Do check out the aws ebs forum

Cheers, biobirdman

Upvotes: 2

Related Questions