[Solved]-Django's migrate command on Amazon Elastic Beanstalk is killed

by

7👍

AWS is not developer friendly when it comes to troubleshooting with the poor logging mechanism.

As an avid AWS user who recently eval’d EBS for a Django project, I totally agree with this for the same reasons. I ended up going with Heroku for this and reasons I won’t go into but I think the following pattern helps either way.

The steps to prepare your prod environment can go in different places; they don’t have to happen on your target web-server environment.

I ended up pulling my make/migrate tasks out of my deployment automation and into tasks that happen just before it. The only things that happen in my target web-server environment are directly related to the code on that server.

In other words: I recommend if you have a CI tool for builds/tests, you pull your make/migrate and any other prep to the environment outside your webserver into your deployment pipeline. Something like:

  • Checkout code
  • Run Tests (including make/migrate on ephemeral database to test it if possible)
  • Put app in maintenance mode (or similar, if required)
  • Snapshot database
  • Make/Migrate on production
  • Deploy
  • If deploy fails, rollback DB, rollback app.

Then you are separating the concerns of automation for your app server and automation for the rest of your prod environment and letting your CI handle that. You could handle them in the same place, but clearly its a bit clunky to do that using EBS’s facilities.

👤alph486

2👍

My migrations were being killed because the memory reserved in the Dockerrun.aws.json file was too low. The example provided in the documentation gave “128” as a sample value, and I had just used that. Increasing the value for “memory” resolved the problem.

e.g. Dockerrun.aws.json excerpt:

  "containerDefinitions": [
    {
      "name": "php-app",
      "image": "php:fpm",
      "essential": true,
      "memory": 512,
      // ... etc. ...
    }
  ]
👤kaapstorm

Leave a comment