rg87
August 19, 2020, 3:31pm
1
I am doing a brand new elastic beanstalk deployment following the instructions and using v0.36.4 . The build process fails and in the eb-engine.log file I am seeing the following error:
2020/08/19 14:31:52.646697 [INFO] Writing nginx upstream config...
2020/08/19 14:31:52.646738 [ERROR] compile template elasticbeanstalk-nginx-docker-upstream.template failed with error:open/create output file failed:
open /var/proxy/staging/nginx/conf.d/elasticbeanstalk-nginx-docker-upstream.conf: no such file or directory
2020/08/19 14:31:52.646748 [ERROR] An error occurred during execution of command [app-deploy] - [Run Docker Container]. Stop running the command. Error: generate nginx upstream conf failed with error open/create output file failed:
open /var/proxy/staging/nginx/conf.d/elasticbeanstalk-nginx-docker-upstream.conf: no such file or directory
Hi @rg87 https://www.metabase.com/docs/latest/operations-guide/running-metabase-on-elastic-beanstalk.html
rg87
August 19, 2020, 3:51pm
3
Yes that is the instructions I followed. Sorry not build process but environment start process. If you need more logs or if there’s something I can send to you let me know.
Edit, here are other errors I see in the log:
2020/08/19 14:31:04.799816 [INFO] Start cfn-hup
2020/08/19 14:31:04.799842 [INFO] Running command /bin/sh -c systemctl is-active cfn-hup.service
2020/08/19 14:31:04.803714 [INFO] Running command /bin/sh -c systemctl is-active cfn-hup.service
2020/08/19 14:31:04.812376 [INFO] Running command /bin/sh -c systemctl show -p PartOf cfn-hup.service
2020/08/19 14:31:04.846273 [INFO] Running command /bin/sh -c systemctl daemon-reload
2020/08/19 14:31:04.976098 [INFO] Running command /bin/sh -c systemctl reset-failed
2020/08/19 14:31:04.980535 [INFO] Running command /bin/sh -c systemctl is-enabled aws-eb.target
2020/08/19 14:31:04.992923 [INFO] Running command /bin/sh -c systemctl enable aws-eb.target
2020/08/19 14:31:05.121718 [INFO] Running command /bin/sh -c systemctl start aws-eb.target
2020/08/19 14:31:05.126465 [INFO] Running command /bin/sh -c systemctl enable cfn-hup.service
2020/08/19 14:31:05.281108 [INFO] Running command /bin/sh -c systemctl show -p PartOf cfn-hup.service
2020/08/19 14:31:05.286336 [INFO] Running command /bin/sh -c systemctl is-active cfn-hup.service
2020/08/19 14:31:05.297567 [INFO] Running command /bin/sh -c systemctl start cfn-hup.service
2020/08/19 14:31:05.375410 [INFO] Instance has NOT been bootstrapped
2020/08/19 14:31:05.375424 [INFO] Executing instruction: SetupPublishLogCronjob
2020/08/19 14:31:05.375429 [INFO] Setup publish logs cron job...
2020/08/19 14:31:05.375434 [INFO] Copying file /opt/elasticbeanstalk/config/private/logtasks/cron/publishlogs to /etc/cron.d/publishlogs
2020/08/19 14:31:05.376888 [INFO] Executing instruction: Start Docker
2020/08/19 14:31:05.376896 [INFO] Starting Docker...
2020/08/19 14:31:05.376931 [INFO] Copying file /opt/elasticbeanstalk/config/private/docker-log.conf to /etc/systemd/system/docker.service.d/docker-log.conf
2020/08/19 14:31:05.378173 [INFO] Copying file /opt/elasticbeanstalk/config/private/docker-rsyslog.conf to /etc/rsyslog.d/docker-log.conf
2020/08/19 14:31:05.386698 [INFO] Running command /bin/sh -c systemctl restart rsyslog.service
2020/08/19 14:31:05.426174 [INFO] Running command /bin/sh -c systemctl show -p PartOf docker.service
2020/08/19 14:31:05.446336 [INFO] Running command /bin/sh -c systemctl daemon-reload
2020/08/19 14:31:05.588596 [INFO] Running command /bin/sh -c systemctl reset-failed
2020/08/19 14:31:05.608044 [INFO] Running command /bin/sh -c systemctl show -p PartOf docker.service
2020/08/19 14:31:05.628933 [INFO] Running command /bin/sh -c systemctl is-active docker.service
2020/08/19 14:31:05.636065 [INFO] Running command /bin/sh -c systemctl start docker.service
2020/08/19 14:31:08.687595 [INFO] Instance has NOT been bootstrapped
2020/08/19 14:31:08.687610 [INFO] Executing instruction: Setup Docker Options
2020/08/19 14:31:08.687614 [INFO] Setting up configurations for docker platform
2020/08/19 14:31:08.691400 [INFO] Register process eb-docker
2020/08/19 14:31:08.691426 [INFO] Running command /bin/sh -c systemctl show -p PartOf eb-docker.service
2020/08/19 14:31:08.701097 [INFO] Running command /bin/sh -c systemctl daemon-reload
2020/08/19 14:31:08.775706 [INFO] Running command /bin/sh -c systemctl reset-failed
2020/08/19 14:31:08.780940 [INFO] Running command /bin/sh -c systemctl enable eb-docker.service
2020/08/19 14:31:08.857976 [INFO] Register process eb-docker-events
2020/08/19 14:31:08.858003 [INFO] Running command /bin/sh -c systemctl show -p PartOf eb-docker-events.service
2020/08/19 14:31:08.864795 [INFO] Running command /bin/sh -c systemctl daemon-reload
2020/08/19 14:31:08.939885 [INFO] Running command /bin/sh -c systemctl reset-failed
2020/08/19 14:31:08.945251 [INFO] Running command /bin/sh -c systemctl enable eb-docker-events.service
2020/08/19 14:31:09.022582 [INFO] Register process eb-docker-log
2020/08/19 14:31:09.022610 [INFO] Running command /bin/sh -c systemctl show -p PartOf eb-docker-log.service
2020/08/19 14:31:09.029822 [INFO] Running command /bin/sh -c systemctl daemon-reload
2020/08/19 14:31:09.103637 [INFO] Running command /bin/sh -c systemctl reset-failed
2020/08/19 14:31:09.108830 [INFO] Running command /bin/sh -c systemctl enable eb-docker-log.service
2020/08/19 14:31:09.183586 [INFO] Running command /bin/sh -c systemctl show -p PartOf eb-docker-events.service
2020/08/19 14:31:09.189939 [INFO] Running command /bin/sh -c systemctl is-active eb-docker-events.service
2020/08/19 14:31:09.193528 [INFO] Running command /bin/sh -c systemctl start eb-docker-events.service
2020/08/19 14:31:09.234647 [INFO] Instance has NOT been bootstrapped
rg87
August 19, 2020, 4:19pm
4
@flamber The only thing I modified in the setup was that I couldn’t find the health check path under the location mentioned. I had to go to Load balancers configuration to find the input for the path.
@rg87 We think that AWS has changed something, so the guide cannot be followed exactly. Still figuring out what the problem could be.
timy
September 1, 2020, 8:03pm
7
I also think something has changed. I am unable to deploy the exact artifact that previously deployed in what should have been the same environment.