Warning: file_get_contents(/data/phpspider/zhask/data//catemap/3/heroku/2.json): failed to open stream: No such file or directory in /data/phpspider/zhask/libs/function.php on line 167

Warning: Invalid argument supplied for foreach() in /data/phpspider/zhask/libs/tag.function.php on line 1116

Notice: Undefined index: in /data/phpspider/zhask/libs/function.php on line 180

Warning: array_chunk() expects parameter 1 to be array, null given in /data/phpspider/zhask/libs/function.php on line 181
Ruby on rails 希罗库例外_Ruby On Rails_Heroku - Fatal编程技术网

Ruby on rails 希罗库例外

Ruby on rails 希罗库例外,ruby-on-rails,heroku,Ruby On Rails,Heroku,Heroku在尝试重新启动服务器时显示此异常。这并不能说明问题的确切位置 2014-11-25T08:27:04.671821+00:00 heroku[web.1]: State changed from up to starting 2014-11-25T08:27:07.668864+00:00 app[web.1]: /app/vendor/ruby-2.0.0/lib/ruby/2.0.0/webrick/server.rb:170:in `block in start' 201

Heroku在尝试重新启动服务器时显示此异常。这并不能说明问题的确切位置

2014-11-25T08:27:04.671821+00:00 heroku[web.1]: State changed from up to starting
2014-11-25T08:27:07.668864+00:00 app[web.1]:    /app/vendor/ruby-2.0.0/lib/ruby/2.0.0/webrick/server.rb:170:in `block in start'
2014-11-25T08:27:07.668866+00:00 app[web.1]:    /app/vendor/ruby-2.0.0/lib/ruby/2.0.0/webrick/server.rb:32:in `start'
2014-11-25T08:27:07.668862+00:00 app[web.1]:    /app/vendor/ruby-2.0.0/lib/ruby/2.0.0/webrick/server.rb:170:in `select'
2014-11-25T08:27:07.668855+00:00 app[web.1]: [2014-11-25 08:27:07] FATAL SignalException: SIGTERM
2014-11-25T08:27:07.668881+00:00 app[web.1]:    bin/rails:8:in `require'
2014-11-25T08:27:07.668883+00:00 app[web.1]:    bin/rails:8:in `<main>'
2014-11-25T08:27:07.668867+00:00 app[web.1]:    /app/vendor/ruby-2.0.0/lib/ruby/2.0.0/webrick/server.rb:160:in `start'
2014-11-25T08:27:07.668890+00:00 app[web.1]: [2014-11-25 08:27:07] INFO  WEBrick::HTTPServer#start done.
2014-11-25T08:27:07.668889+00:00 app[web.1]: [2014-11-25 08:27:07] INFO  going to shutdown ...
2014-11-25T08:27:07.700009+00:00 app[web.1]: => Booting WEBrick
2014-11-25T08:27:07.668875+00:00 app[web.1]:    /app/vendor/bundle/ruby/2.0.0/gems/railties-4.1.8/lib/rails/commands/commands_tasks.rb:76:in `tap'
2014-11-25T08:27:07.668873+00:00 app[web.1]:    /app/vendor/bundle/ruby/2.0.0/gems/railties-4.1.8/lib/rails/commands/commands_tasks.rb:81:in `block in server'
2014-11-25T08:27:07.668876+00:00 app[web.1]:    /app/vendor/bundle/ruby/2.0.0/gems/railties-4.1.8/lib/rails/commands/commands_tasks.rb:76:in `server'
2014-11-25T08:27:07.668878+00:00 app[web.1]:    /app/vendor/bundle/ruby/2.0.0/gems/railties-4.1.8/lib/rails/commands/commands_tasks.rb:40:in `run_command!'
2014-11-25T08:27:07.668869+00:00 app[web.1]:    /app/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/handler/webrick.rb:14:in `run'
2014-11-25T08:27:07.668870+00:00 app[web.1]:    /app/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/server.rb:264:in `start'
2014-11-25T08:27:07.668872+00:00 app[web.1]:    /app/vendor/bundle/ruby/2.0.0/gems/railties-4.1.8/lib/rails/commands/server.rb:69:in `start'
2014-11-25T08:27:07.700019+00:00 app[web.1]: => Notice: server is listening on all interfaces (0.0.0.0). Consider using 127.0.0.1 (--binding option)
2014-11-25T08:27:07.700021+00:00 app[web.1]: => Ctrl-C to shutdown server
2014-11-25T08:27:07.668879+00:00 app[web.1]:    /app/vendor/bundle/ruby/2.0.0/gems/railties-4.1.8/lib/rails/commands.rb:17:in `<top (required)>'
2014-11-25T08:27:07.700016+00:00 app[web.1]: => Rails 4.1.8 application starting in production on http://0.0.0.0:8363
2014-11-25T08:27:07.700018+00:00 app[web.1]: => Run `rails server -h` for more startup options
2014-11-25T08:27:07.700022+00:00 app[web.1]: Exiting
2014-11-25T08:27:07.113073+00:00 heroku[web.1]: Stopping all processes with SIGTERM
2014-11-25T08:27:04.671821+00:00 heroku[web.1]:状态从开始更改为开始
2014-11-25T08:27:07.668864+00:00应用程序[web.1]:/app/vendor/ruby-2.0.0/lib/ruby/2.0.0/webrick/server.rb:170:在“开始时阻塞”中
2014-11-25T08:27:07.668866+00:00应用程序[web.1]:/app/vendor/ruby-2.0.0/lib/ruby/2.0.0/webrick/server.rb:32:in'start'
2014-11-25T08:27:07.668862+00:00应用程序[web.1]:/app/vendor/ruby-2.0.0/lib/ruby/2.0.0/webrick/server.rb:170:在“选择”中
2014-11-25T08:27:07.668855+00:00应用程序[web.1]:[2014-11-25 08:27:07]致命信号异常:SIGTERM
2014-11-25T08:27:07.668881+00:00应用程序[web.1]:bin/rails:8:in'require'
2014-11-25T08:27:07.668883+00:00应用程序[web.1]:bin/rails:8:in`'
2014-11-25T08:27:07.668867+00:00应用程序[web.1]:/app/vendor/ruby-2.0.0/lib/ruby/2.0.0/webrick/server.rb:160:in'start'
2014-11-25T08:27:07.668890+00:00应用程序[web.1]:[2014-11-25 08:27:07]信息WEBrick::HTTPServer#启动完成。
2014-11-25T08:27:07.668889+00:00应用程序[web.1]:[2014-11-25 08:27:07]信息将关闭。。。
2014-11-25T08:27:07.700009+00:00应用程序[web.1]:=>启动WEBrick
2014-11-25T08:27:07.668875+00:00 app[web.1]:/app/vendor/bundle/ruby/2.0.0/gems/railties-4.1.8/lib/rails/commands/commands_tasks.rb:76:in'tap'
2014-11-25T08:27:07.668873+00:00应用程序[web.1]:/app/vendor/bundle/ruby/2.0.0/gems/railties-4.1.8/lib/rails/commands/commands_tasks.rb:81:“服务器中的块”中
2014-11-25T08:27:07.668876+00:00 app[web.1]:/app/vendor/bundle/ruby/2.0.0/gems/railties-4.1.8/lib/rails/commands/commands_tasks.rb:76:in'server'
2014-11-25T08:27:07.668878+00:00应用程序[web.1]:/app/vendor/bundle/ruby/2.0.0/gems/railties-4.1.8/lib/rails/commands/commands_tasks.rb:40:in'run_command!'
2014-11-25T08:27:07.668869+00:00 app[web.1]:/app/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/handler/webrick.rb:14:in'run'
2014-11-25T08:27:07.668870+00:00应用程序[web.1]:/app/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/server.rb:264:在“开始”中
2014-11-25T08:27:07.668872+00:00 app[web.1]:/app/vendor/bundle/ruby/2.0.0/gems/railties-4.1.8/lib/rails/commands/server.rb:69:in'start'
2014-11-25T08:27:07.700019+00:00应用程序[web.1]:=>注意:服务器正在监听所有接口(0.0.0.0)。考虑使用127.0.0.1(-绑定选项)
2014-11-25T08:27:07.700021+00:00应用程序[web.1]:=>Ctrl-C关闭服务器
2014-11-25T08:27:07.668879+00:00 app[web.1]:/app/vendor/bundle/ruby/2.0.0/gems/railties-4.1.8/lib/rails/commands.rb:17:in`'
2014-11-25T08:27:07.700016+00:00应用程序[web.1]:=>Rails 4.1.8应用程序在http://0.0.0.0:8363
2014-11-25T08:27:07.700018+00:00应用程序[web.1]:=>运行“rails服务器-h”以获得更多启动选项
2014-11-25T08:27:07.700022+00:00应用程序[网站1]:退出
2014-11-25T08:27:07.113073+00:00 heroku[web.1]:停止使用SIGTERM的所有进程

看起来您试图重新启动服务器,但出现了致命错误

[2014-11-25 08:27:07] FATAL SignalException: SIGTERM
如果您的服务器以前工作正常,请尝试重新启动服务器或与服务器管理员联系


Heroku使用Postgresql作为数据库服务器,您可以将迁移粘贴到此处吗?

此问题是由于生产中缺少一些配置造成的。rb Heroku应用程序在生产中添加这些配置后启动服务器正常。rb

您正在使用哪个命令重新启动Heroku服务器?是,此错误发生在重新启动时或我尝试部署时。SIGTERM异常发生在dyons关闭时,因此webrick给出了此异常,但我不理解为什么dyons没有显示任何异常细节。如果我恢复到上一次提交,它可以正常工作。我刚刚在new commit中添加了一些迁移,heroku rake db:migrate和这个异常开始出现