Ruby on rails Ruby的弹性Beanstalk迁移失败

网站上的错误消息

An unhandled lowlevel error occured. The application logs may have details.

登出时间为

=== puma startup: 2015-05-17 16:26:01 +0000 ===
=== puma startup: 2015-05-17 16:26:01 +0000 ===
[3112] - Worker 0 (pid: 3150) booted, phase: 0
2015-05-17 17:31:54 +0000: Rack app error: #<RuntimeError: Missing `secret_key_base` for 'production' environment, set this value in `config/secrets.yml`>
/opt/rubies/ruby-2.2.2/lib/ruby/gems/2.2.0/gems/railties-4.1.8/lib/rails/application.rb:462:in `validate_secret_key_config!'
/opt/rubies/ruby-2.2.2/lib/ruby/gems/2.2.0/gems/railties-4.1.8/lib/rails/application.rb:195:in `env_config'
/opt/rubies/ruby-2.2.2/lib/ruby/gems/2.2.0/gems/railties-4.1.8/lib/rails/engine.rb:510:in `call'
/opt/rubies/ruby-2.2.2/lib/ruby/gems/2.2.0/gems/railties-4.1.8/lib/rails/application.rb:144:in `call'
/opt/rubies/ruby-2.2.2/lib/ruby/gems/2.2.0/gems/puma-2.11.2/lib/puma/configuration.rb:51:in `call'
/opt/rubies/ruby-2.2.2/lib/ruby/gems/2.2.0/gems/puma-2.11.2/lib/puma/server.rb:507:in `handle_request'
/opt/rubies/ruby-2.2.2/lib/ruby/gems/2.2.0/gems/puma-2.11.2/lib/puma/server.rb:375:in `process_client'
/opt/rubies/ruby-2.2.2/lib/ruby/gems/2.2.0/gems/puma-2.11.2/lib/puma/server.rb:262:in `block in run'
/opt/rubies/ruby-2.2.2/lib/ruby/gems/2.2.0/gems/puma-2.11.2/lib/puma/thread_pool.rb:104:in `call'
/opt/rubies/ruby-2.2.2/lib/ruby/gems/2.2.0/gems/puma-2.11.2/lib/puma/thread_pool.rb:104:in `block in spawn_thread'
2015-05-17 17:31:54 +0000: Rack app error: #<RuntimeError: Missing `secret_key_base` for 'production' environment, set this value in `config/secrets.yml`>
/opt/rubies/ruby-2.2.2/lib/ruby/gems/2.2.0/gems/railties-4.1.8/lib/rails/application.rb:462:in `validate_secret_key_config!'
/opt/rubies/ruby-2.2.2/lib/ruby/gems/2.2.0/gems/railties-4.1.8/lib/rails/application.rb:195:in `env_config'
/opt/rubies/ruby-2.2.2/lib/ruby/gems/2.2.0/gems/railties-4.1.8/lib/rails/engine.rb:510:in `call'
/opt/rubies/ruby-2.2.2/lib/ruby/gems/2.2.0/gems/railties-4.1.8/lib/rails/application.rb:144:in `call'
/opt/rubies/ruby-2.2.2/lib/ruby/gems/2.2.0/gems/puma-2.11.2/lib/puma/configuration.rb:51:in `call'
/opt/rubies/ruby-2.2.2/lib/ruby/gems/2.2.0/gems/puma-2.11.2/lib/puma/server.rb:507:in `handle_request'
/opt/rubies/ruby-2.2.2/lib/ruby/gems/2.2.0/gems/puma-2.11.2/lib/puma/server.rb:375:in `process_client'
/opt/rubies/ruby-2.2.2/lib/ruby/gems/2.2.0/gems/puma-2.11.2/lib/puma/server.rb:262:in `block in run'
/opt/rubies/ruby-2.2.2/lib/ruby/gems/2.2.0/gems/puma-2.11.2/lib/puma/thread_pool.rb:104:in `call'
/opt/rubies/ruby-2.2.2/lib/ruby/gems/2.2.0/gems/puma-2.11.2/lib/puma/thread_pool.rb:104:in `block in spawn_thread'
2015-05-17 17:35:47 +0000: Rack app error: #<RuntimeError: Missing `secret_key_base` for 'production' environment, set this value in `config/secrets.yml`>
/opt/rubies/ruby-2.2.2/lib/ruby/gems/2.2.0/gems/railties-4.1.8/lib/rails/application.rb:462:in `validate_secret_key_config!'
/opt/rubies/ruby-2.2.2/lib/ruby/gems/2.2.0/gems/railties-4.1.8/lib/rails/application.rb:195:in `env_config'
/opt/rubies/ruby-2.2.2/lib/ruby/gems/2.2.0/gems/railties-4.1.8/lib/rails/engine.rb:510:in `call'
/opt/rubies/ruby-2.2.2/lib/ruby/gems/2.2.0/gems/railties-4.1.8/lib/rails/application.rb:144:in `call'
/opt/rubies/ruby-2.2.2/lib/ruby/gems/2.2.0/gems/puma-2.11.2/lib/puma/configuration.rb:51:in `call'
/opt/rubies/ruby-2.2.2/lib/ruby/gems/2.2.0/gems/puma-2.11.2/lib/puma/server.rb:507:in `handle_request'
/opt/rubies/ruby-2.2.2/lib/ruby/gems/2.2.0/gems/puma-2.11.2/lib/puma/server.rb:375:in `process_client'
/opt/rubies/ruby-2.2.2/lib/ruby/gems/2.2.0/gems/puma-2.11.2/lib/puma/server.rb:262:in `block in run'
/opt/rubies/ruby-2.2.2/lib/ruby/gems/2.2.0/gems/puma-2.11.2/lib/puma/thread_pool.rb:104:in `call'
/opt/rubies/ruby-2.2.2/lib/ruby/gems/2.2.0/gems/puma-2.11.2/lib/puma/thread_pool.rb:104:in `block in spawn_thread'
2015-05-17 17:35:47 +0000: Rack app error: #<RuntimeError: Missing `secret_key_base` for 'production' environment, set this value in `config/secrets.yml`>
/opt/rubies/ruby-2.2.2/lib/ruby/gems/2.2.0/gems/railties-4.1.8/lib/rails/application.rb:462:in `validate_secret_key_config!'
/opt/rubies/ruby-2.2.2/lib/ruby/gems/2.2.0/gems/railties-4.1.8/lib/rails/application.rb:195:in `env_config'
/opt/rubies/ruby-2.2.2/lib/ruby/gems/2.2.0/gems/railties-4.1.8/lib/rails/engine.rb:510:in `call'
/opt/rubies/ruby-2.2.2/lib/ruby/gems/2.2.0/gems/railties-4.1.8/lib/rails/application.rb:144:in `call

但是我不相信这个秘密基地不见了。我用实际的生产密钥关闭了ENV[：secret\u key\u base]。如果我转到我的secret.yml文件，它是纯文本的

我让nginx和puma跑步

可能的错误可能是因为生产密钥库与部署的密钥库不同？我部署后做了一个秘密。我将尝试删除该eb实例并重新执行它。也许这会解决问题

我非常感谢您提出的任何其他建议

secrets.yml未上载到服务器。你需要在Elastic Beanstalk控制台中设置你的秘密

转到环境，然后在侧边栏中选择配置，选择软件配置旁边的齿轮图标，然后在列表底部添加您的密钥，可能是密钥库，单击+然后选择应用，您的环境应该会更新

我建议在添加密钥后重新启动。如有必要，重新部署最新版本，它将成功迁移

关于调试器的旁注： 您可以通过SSH连接到服务器来获得rails控制台

从Rails项目目录执行eb ssh。 执行sudo su-以获得根访问权限。 执行cd/var/app/current进入Rails项目目录。 executebundle exec rails console或rails c取决于获得rails控制台的版本。

---

两个问题：这有用吗？您如何设置环境？它在抱怨生产环境。您是否尝试添加几个调试语句来验证您所做的假设？这在本地有效。我可以访问我的本地主机。它在aws实例上从未起作用。在aws上运行调试器时是否可以放置调试器？