Ruby的Elastic Beanstalk遷移失敗

Question

網站上的錯誤消息

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

但是我不相信secret_key_base丟失了。 我用實際的生產密鑰關閉了ENV [：secret_key_base]。 如果轉到我的secret.yml文件，它將以純文本格式存在。

我正在運行nginx和puma。

可能的錯誤可能是因為生產secret_key_base是什么得到了部署不同？ 我eb部署后，我做了一個秘密的秘密。 我將嘗試刪除eb實例並重做它。 也許那將解決問題。

我感謝其他建議

Answer 1

secrets.yml沒有上傳到服務器。 您需要在Elastic Beanstalk控制台中設置機密。

轉到環境，然后在側欄中選擇“ Configuration ”，選擇“ Software Configuration旁邊的齒輪圖標，然后添加密鑰（大概是secret_key_base在列表的底部，單擊+ ，然后選擇“ Apply ，您的環境將更新。

添加密鑰后，建議您重新啟動。 如有必要，請重新部署最新版本，它應該可以成功遷移。

旁注（關於調試器）：您可以通過SSH進入服務器來獲得Rails控制台。

1. 從Rails項目目錄中執行eb ssh 。
2. 執行sudo su -以獲得root用戶訪問權限。
3. 執行cd /var/app/current進入Rails項目目錄。
4. 執行bundle exec rails console或rails c （取決於版本）以獲取Rails控制台。