HTTP 500将Elixir / Phoenix部署到AWS Elastic Beanstalk

我在configurationAWS / Elastic Beanstalk所需的elixir / phoenixconfiguration时遇到了问题。 （遵循在这里find的指南： https ://robots.thoughtbot.com/deploying-elixir-to-aws-elastic-beanstalk-with-docker – 我的Dockerfile除了更新的库看起来相似）。

我可以在eb local run ，但是在推进生产时遇到了麻烦。

但是，当我尝试部署到EB，我得到以下警告，并崩溃：

 Environment health has transitioned from Degraded to Severe. 100.0 % of the requests are failing with HTTP 5xx. Command failed on all instances. Incorrect application version found on all instances. Expected version "app-8412-171116_115503" (deployment 5). ELB processes are not healthy on all instances. 100.0 % of the requests to the ELB are erroring with HTTP 4xx. Insufficient request rate (0.5 requests/min) to determine application health (5 minutes ago). ELB health is failing or not available for all instances. 

我想知道如果有人可以让我知道，如果我的configuration看起来是正确的。

• 无法使用Nginx + Unicorn访问Rails应用程序
• Nginx没有提供Django映像
• 404在Nginx上没有find错误
• AWS Spring引导应用程序上的502错误请求
• Node.JS代理与Nginx和Docker

我一直在尝试一些东西，但是我觉得我感到困惑，因为我只是在猜测这一点。

config.exs

 use Mix.Config config :newsly, ecto_repos: [Newsly.Repo] config :logger, :console, format: "$time $metadata[$level] $message\n", metadata: [:request_id] import_config "#{Mix.env}.exs" 

prod.exs

 use Mix.Config config :logger, :console, format: "[$level] $message\n" config :phoenix, :stacktrace_depth, 5 import_config "prod.secret.exs" 

prod.secret.exs

 use Mix.Config config :ex_aws, access_key_id: System.get_env("AWS_ACCESS_KEY_ID"), secret_access_key: System.get_env("AWS_SECRET_ACCESS_KEY"), bucket_name: System.get_env("BUCKET_NAME"), s3: [ scheme: "https://", host: System.get_env("BUCKET_NAME"), region: "us-west-2" ] config :newsly, Newsly.Repo, adapter: Ecto.Adapters.Postgres, username: System.get_env("USERNAME"), password: System.get_env("PASSWORD"), database: System.get_env("DATABASE"), hostname: System.get_env("DBHOST"), # sometimes hostname is db (like in the docker-compose method - play with this one) pool_size: 10 config :newsly, Newsly.Endpoint, http: [port: 4000], debug_errors: true, code_reloader: false, url: [scheme: "http", host: System.get_env("HOST"), port: 4000], secret_key_base: System.get_env("SECRET_KEY_BASE"), pubsub: [adapter: Phoenix.PubSub.PG2, pool_size: 5, name: Newsly.PubSub], check_origin: false, watchers: [node: ["node_modules/brunch/bin/brunch", "watch", "--stdin", cd: Path.expand("../", __DIR__)]] 

在我的Dockerfile中，我设置了如下的环境variables：

 ENV AWS_ACCESS_KEY_ID=nottelling ENV AWS_SECRET_ACCESS_KEY=nottelling ENV BUCKET_NAME=s3 storage bucket (not eb related) ENV SECRET_KEY_BASE=nottelling ENV HOST=host name of my eb instance im uploading to ENV DBHOST=AWS rds host that holds postgres ENV USERNAME=nottelling ENV PASSWORD=nottelling 

关于实例的我的健康报告未能显示以下警告：

 Environment health has transitioned from Warning to Severe. 100.0 % of the requests are failing with HTTP 5xx. ELB processes are not healthy on all instances. ELB health is failing or not available for all instances. 

NGINX似乎在窒息

 2017/11/16 17:59:46 [error] 28815#0: *99 connect() failed (113: No route to host) while connecting to upstream, client: 172.31.20.108, server: , request: "GET / HTTP/1.1", upstream: "http://172.17.0.2:4000/", host: "172.31.38.244" 

在nginx日志中。

如果我看看我有的eb活动日志

 duplicate MIME type "text/html" in /etc/nginx/sites-enabled/elasticbeanstalk-nginx-docker-proxy.conf:11 

这似乎是杀nginx

 [2017-11-16T18:02:33.927Z] INFO [29355] - [Application update app-8412-171116_115503@5/AppDeployStage1/AppDeployEnactHook/01flip.sh] : Completed activity. Result: nginx: [warn] duplicate MIME type "text/html" in /etc/nginx/sites-enabled/elasticbeanstalk-nginx-docker-proxy.conf:11 Stopping nginx: [ OK ] Starting nginx: nginx: [warn] duplicate MIME type "text/html" in /etc/nginx/sites-enabled/elasticbeanstalk-nginx-docker-proxy.conf:11 [ OK ] iptables: Saving firewall rules to /etc/sysconfig/iptables: [ OK ] Stopping current app container: e0161742ee69... Error response from daemon: No such image: aws_beanstalk/current-app:latest Making STAGING app container current... Untagged: aws_beanstalk/staging-app:latest eb-docker start/running, process 1398 Docker container e25f2b562f4f is running aws_beanstalk/current-app. 

有没有人有任何想法？

编辑：

挖掘我find的nginx的日志

 map $http_upgrade $connection_upgrade { default "upgrade"; "" ""; } server { listen 80; gzip on; gzip_comp_level 4; gzip_types text/html text/plain text/css application/json application/x-javascript text/xml application/xml application/xml+rss text/javascript; if ($time_iso8601 ~ "^(\d{4})-(\d{2})-(\d{2})T(\d{2})") { set $year $1; set $month $2; set $day $3; set $hour $4; } access_log /var/log/nginx/healthd/application.log.$year-$month-$day-$hour healthd; access_log /var/log/nginx/access.log; location / { proxy_pass http://docker; proxy_http_version 1.1; proxy_set_header Connection $connection_upgrade; proxy_set_header Upgrade $http_upgrade; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; } } 

所以，

 duplicate MIME type "text/html" in /etc/nginx/sites-enabled/elasticbeanstalk-nginx-docker-proxy.conf:11 

似乎是指这一行：

 gzip_types text/html text/plain text/css application/json application/x-javascript text/xml application/xml application/xml+rss text/javascript; 

但在这一点上，我会发现，如果nginx只是因为它定义了text/html两次而窒息，才会感到惊讶。 所以现在我不确定….

编辑编辑：我应该提到，我的nginx / error.logs看起来像下面（最后一行重复ad-infinum）：

 2017/11/16 17:19:22 [warn] 18445#0: duplicate MIME type "text/html" in /etc/nginx/sites-enabled/elasticbeanstalk-nginx-docker-proxy.conf:11 2017/11/16 17:19:22 [warn] 18460#0: duplicate MIME type "text/html" in /etc/nginx/sites-enabled/elasticbeanstalk-nginx-docker-proxy.conf:11 2017/11/16 17:20:06 [error] 18467#0: *11 connect() failed (113: No route to host) while connecting to upstream, client: 172.31.32.139, server: , request: "GET / HTTP/1.1", upstream: "http://172.17.0.2:4000/", host: "172.31.38.244" 2017/11/16 17:20:15 [error] 18467#0: *13 connect() failed (113: No route to host) while connecting to upstream, client: 172.31.20.108, server: , request: "GET / HTTP/1.1", upstream: "http://172.17.0.2:4000/", host: "172.31.38.244" 2017/11/16 17:20:21 [error] 18467#0: *15 connect() failed (113: No route to host) while connecting to upstream, client: 172.31.32.139, server: , request: "GET / HTTP/1.1", upstream: "http://172.17.0.2:4000/", host: "172.31.38.244" 2017/11/16 17:20:30 [error] 18467#0: *17 connect() failed (113: No route to host) while connecting to upstream, client: 172.31.20.108, server: , request: "GET / HTTP/1.1", upstream: 

这是问题的核心

NGINX从根本上不能将入口点连接到应用程序，我不知道为什么！

更新：

使用凯文·约翰逊的build议，我成功地把我的Docker文件推到AWS ECR，并且当我用一个好的Dockerrun.aws.json eb deploy '我的应用程序'时，编译正确。 这实际上是一个首选的方法来做到这一点。 不过 ，我仍然得到同样的错误！ 我不知道发生了什么，但我想我可以放心地说，我的Dockerfile成功编译。

我认为在AWS中有些东西被破坏，我不知道是什么。

UPDATE

问题与NGINX路由问题有关。 在一个干净的问题中的更多信息： 如何修改Elastic Beanstalk AWS上的NGINX路由？