升级后Rails Web服务器崩溃

时间:2020-10-26 11:53:11

标签: ruby-on-rails ruby heroku rubygems

因此,从ruby 2.4.6升级到ruby 2.7.2,将rails 4.2.8升级到rails 5,我升级了我的应用程序并在本地对其进行了测试,现在我正尝试部署到heroku,一旦完成,Web服务器就会崩溃部署。

Web服务器日志具有以下内容:

2020-10-26T11:37:57.946836+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.7.0/gems/puma-5.0.2/lib/puma/configuration.rb:256:in `app'
2020-10-26T11:37:57.946836+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.7.0/gems/puma-5.0.2/lib/puma/runner.rb:131:in `load_and_bind'
2020-10-26T11:37:57.946836+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.7.0/gems/puma-5.0.2/lib/puma/cluster.rb:501:in `run'
2020-10-26T11:37:57.946837+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.7.0/gems/puma-5.0.2/lib/puma/launcher.rb:171:in `run'
2020-10-26T11:37:57.946837+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.7.0/gems/puma-5.0.2/lib/puma/cli.rb:80:in `run'
2020-10-26T11:37:57.946837+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.7.0/gems/puma-5.0.2/bin/puma:10:in `<top (required)>'
2020-10-26T11:37:57.946837+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.7.0/bin/puma:23:in `load'
2020-10-26T11:37:57.946837+00:00 app[web.1]:   /app/vendor/bundle/ruby/2.7.0/bin/puma:23:in `<top (required)>'
2020-10-26T11:37:58.074574+00:00 heroku[web.1]: Process exited with status 1
2020-10-26T11:37:58.109882+00:00 heroku[web.1]: State changed from starting to crashed

构建日志具有以下内容

-----> Detecting rails configuration
###### WARNING:
       Your app was upgraded to bundler 2.1.4.
       Previously you had a successful deploy with bundler 1.17.3.
       
       If you see problems related to the bundler version please refer to:
       https://devcenter.heroku.com/articles/bundler-version#known-upgrade-issues
       
###### WARNING:
       Detecting rails configuration failed
       set HEROKU_DEBUG_RAILS_RUNNER=1 to debug
-----> Discovering process types
       Procfile declares types     -> release, web, worker
       Default types for buildpack -> console, rake
-----> Compressing...
       Done: 387.5M
-----> Launching...

可能是罪魁祸首?

1 个答案:

答案 0 :(得分:0)

在推送部署后尝试使用heroku logs命令,您将看到更详细的错误消息。