Differences

This shows you the differences between two versions of the page.

--- bloglike:2020-12 [2020/12/30 14:28] – fix formatting stybla
+++ bloglike:2020-12 [2020/12/31 14:36] (current) – add EBT deploy stybla
@@ Line 55: / Line 55: @@
  --- //[[stybla@turnovfree.net|Zdenek Styblik]] 2020/12/30 20:12//
+===== When AWS Elastic Beanstalk deploy fails for no reason =====
+I've heard couple rumors that AWS Elastic Beanstalk(EBT) can end up belly up for no reason. It almost seemed like this can happen at random. Ok, seriously - this is one of pain points and drawbacks of EBT and deploys. I waived it off since no details were provided and when something like that happens, I'm going to deal with it. What else?
+It did happen to us. Simple change like any other. Test at ''localhost'' was a OK and so were unit tests/CI. The same cannot be said about deploy. It failed, crashed, burned and left no return address. Deploy crashed in one of ''.ebextension''/''.platform'' hooks. Unfortunately, this was some time ago and I didn't keep the logs. This part was working before and was not touched by MR. However, that was the only lead(error) I could find in AWS CloudWatch logs. As usual this was misleading. Also, container was being killed so fast, one couldn't catch any logs. Enough of blabbering, database migration was to blame, because data couldn't be migrated for one reason or another, and there is ''/var/log/eb-docker/containers/eb-current-app/unexpected-quit.log'' you should check in case something like that happens. Note that there is a 50:50 chance rollback to previous version will be successful and happen(don't be surprised if it does not). It's probably somewhere in documentation, although I cannot find it right now. Anyway, nothing new since EBT is quite old platform and everybody knows this one.
+ --- //[[stybla@turnovfree.net|Zdenek Styblik]] 2020/12/31 19:40//