elasticbeanstalk

Elastic Beanstalk is causing my Rails 6 app precompiled assets to break when adding/removing ENV variables

ⅰ亾dé卋堺 提交于 2021-01-27 22:41:43
问题 I can make code deployments no problem, everything works just fine. The problem is when I use either the Elastic Beanstalk web configuration form or the EB CLI to add/remove/modify ENV variables. Elastic Beanstalk reports back that the change was made successfully however when I visit the web application in the browser I standard Rails error "Sorry, something went wrong". SSH'ing into the server looking at the log files shows errors related to missing assets. Looking in the "public" folder of

Logs not working on Elastic Beanstalk Tomcat environment

雨燕双飞 提交于 2020-12-30 04:11:14
问题 We've been using Elastic Beanstalk to run our Java (8) applications on Tomcat in our company without any issues. Now we have decided to move on to Java 11. We set up our environments with CloudFormation as we did before for the Java 8 applications but now we are using this solution stack: '64bit Amazon Linux 2 v4.1.1 running Tomcat 8.5 Corretto 11' (also tried v4.1.2). Everything works fine but it looks like the request logs feature isn't working anymore in elastic beanstalk (Last 100 lines

Logs not working on Elastic Beanstalk Tomcat environment

眉间皱痕 提交于 2020-12-30 04:06:37
问题 We've been using Elastic Beanstalk to run our Java (8) applications on Tomcat in our company without any issues. Now we have decided to move on to Java 11. We set up our environments with CloudFormation as we did before for the Java 8 applications but now we are using this solution stack: '64bit Amazon Linux 2 v4.1.1 running Tomcat 8.5 Corretto 11' (also tried v4.1.2). Everything works fine but it looks like the request logs feature isn't working anymore in elastic beanstalk (Last 100 lines

Logs not working on Elastic Beanstalk Tomcat environment

放肆的年华 提交于 2020-12-30 04:05:50
问题 We've been using Elastic Beanstalk to run our Java (8) applications on Tomcat in our company without any issues. Now we have decided to move on to Java 11. We set up our environments with CloudFormation as we did before for the Java 8 applications but now we are using this solution stack: '64bit Amazon Linux 2 v4.1.1 running Tomcat 8.5 Corretto 11' (also tried v4.1.2). Everything works fine but it looks like the request logs feature isn't working anymore in elastic beanstalk (Last 100 lines

Logs not working on Elastic Beanstalk Tomcat environment

元气小坏坏 提交于 2020-12-30 04:05:32
问题 We've been using Elastic Beanstalk to run our Java (8) applications on Tomcat in our company without any issues. Now we have decided to move on to Java 11. We set up our environments with CloudFormation as we did before for the Java 8 applications but now we are using this solution stack: '64bit Amazon Linux 2 v4.1.1 running Tomcat 8.5 Corretto 11' (also tried v4.1.2). Everything works fine but it looks like the request logs feature isn't working anymore in elastic beanstalk (Last 100 lines

Container Command Fails in Django on Elastic Beanstalk Python 3.7

半城伤御伤魂 提交于 2020-12-12 12:23:04
问题 I am using Django Python 3.7 on Elastic Beanstalk (Amazon Linux 2) and the following command fails: container_commands: 01_migrate: command: "pipenv run python ./manage.py migrate" leader_only: true 2020-07-17 09:31:57,017 [ERROR] Command 01_migrate (pipenv run python ./manage.py migrate) failed 2020-07-17 09:31:57,017 [ERROR] Error encountered during build of postbuild_0_sarahandanatol: Command 01_migrate failed Traceback (most recent call last): File "/usr/lib/python2.7/site-packages

Container Command Fails in Django on Elastic Beanstalk Python 3.7

↘锁芯ラ 提交于 2020-12-12 12:20:43
问题 I am using Django Python 3.7 on Elastic Beanstalk (Amazon Linux 2) and the following command fails: container_commands: 01_migrate: command: "pipenv run python ./manage.py migrate" leader_only: true 2020-07-17 09:31:57,017 [ERROR] Command 01_migrate (pipenv run python ./manage.py migrate) failed 2020-07-17 09:31:57,017 [ERROR] Error encountered during build of postbuild_0_sarahandanatol: Command 01_migrate failed Traceback (most recent call last): File "/usr/lib/python2.7/site-packages