![Rails 应用程序 502,带有运行 Puma 和 Nginx 的 AWS Elastic Beanstalk](https://linux22.com/image/633040/Rails%20%E5%BA%94%E7%94%A8%E7%A8%8B%E5%BA%8F%20502%EF%BC%8C%E5%B8%A6%E6%9C%89%E8%BF%90%E8%A1%8C%20Puma%20%E5%92%8C%20Nginx%20%E7%9A%84%20AWS%20Elastic%20Beanstalk.png)
我已经能够成功地使用 Passenger 在 Beanstalk 上运行我的应用程序,但是使用 Puma 时却没有成功。每当我将其部署到 Puma 堆栈时,我都会收到 502 错误,我的日志文件表明它找不到 sock 文件:
2014/05/15 21:00:15 [crit] 1684#0: *4 connect() to unix:///var/run/puma/my_app.sock failed (2: No such file or directory) while connecting to upstream, client: 10.184.156.117, server: _, request: "GET / HTTP/1.1", upstream: "http://unix:///var/run/puma/my_app.sock:/", host: "app-env-89spnxpcai.elasticbeanstalk.com"
我的应用程序是使用 Ruby ruby 2.0.0p451 和 Rails 4.1.1 构建的
我的 .ebextensions 配置如下
packages:
yum:
git: []
commands:
add_bundle_exec:
test: test ! -f /opt/elasticbeanstalk/support/.post-provisioning-complete
cwd: /opt/elasticbeanstalk/hooks/appdeploy/pre
command: perl -pi -e 's/(rake)/bundle exec $1/' 11_asset_compilation.sh 12_db_migration.sh
add_deployment_flag:
test: test ! -f /opt/elasticbeanstalk/support/.post-provisioning-complete
cwd: /opt/elasticbeanstalk/hooks/appdeploy/pre
command: perl -pi -e 's/(bundle install)/$1 --deployment/' 10_bundle_install.sh
make_vendor_bundle_dir:
test: test ! -f /opt/elasticbeanstalk/support/.post-provisioning-complete
command: mkdir /var/app/support/vendor_bundle
set_vendor_bundle_var:
test: test ! -f /opt/elasticbeanstalk/support/.post-provisioning-complete
cwd: /opt/elasticbeanstalk/support
command: sed -i '12iexport EB_CONFIG_APP_VENDOR_BUNDLE=$EB_CONFIG_APP_SUPPORT/vendor_bundle' envvars
symlink_vendor_bundle:
test: test ! -f /opt/elasticbeanstalk/support/.post-provisioning-complete
cwd: /opt/elasticbeanstalk/hooks/appdeploy/pre
command: sed -i 's/\(^cd $EB_CONFIG_APP_ONDECK\)/\1\nln -s $EB_CONFIG_APP_VENDOR_BUNDLE .\/vendor\/bundle/' 10_bundle_install.sh
z_write_post_provisioning_complete_file:
cwd: /opt/elasticbeanstalk/support
command: touch .post-provisioning-complete
我做错了什么,我需要一些特殊的东西才能让它与 Puma 一起工作吗?
答案1
最新版本(运行 Ruby 2.0(Puma)的 64 位 Amazon Linux 2014.03 v1.0.5)不存在此问题
答案2
更改config.force_ssl = true
为false
解决了我的问题