Heroku Rails應用程序立即終止（SIGTERM）

Question

我試圖簡單地得到基本的Rails應用程序，只是初始化一個空的/默認的項目，並把它放在Heroku上。

但是，無論我嘗試什麼，我似乎都無法在Heroku上獲得默認的「Welcome Aboard」頁面。 儘管一切工作。

似乎應用程序被推到Heroku後立即終止。我看到一些SIGTERM和'進程退出狀態143'。

這裏的Heroku的日誌：

2014-05-07T19:09:26.423194+00:00 heroku[router]: at=info method=GET path=/ host=young-caverns-5100.herokuapp.com request_id=b0b3030f-8292-4f5e-ad40-8763f6503d1e fwd="24.5.234.171" dyno=web.1 connect=1ms service=13ms status=404 bytes=1829 
2014-05-07T19:09:26.703179+00:00 heroku[router]: at=info method=GET path=/ host=young-caverns-5100.herokuapp.com request_id=80608d62-5b9c-4c20-9450-3909c42a4042 fwd="24.5.234.171" dyno=web.1 connect=51ms service=55ms status=404 bytes=1829 
2014-05-07T19:09:26.791689+00:00 heroku[router]: at=info method=GET path=/ host=young-caverns-5100.herokuapp.com request_id=d4c54ded-b7fa-4535-ad66-47ca49dbd8c4 fwd="24.5.234.171" dyno=web.1 connect=2ms service=14ms status=404 bytes=1829 
2014-05-07T19:10:08.421266+00:00 heroku[router]: at=info method=GET path=/ host=young-caverns-5100.herokuapp.com request_id=e21b204e-8d22-4f47-83a8-01ea4b00163e fwd="24.5.234.171" dyno=web.1 connect=2ms service=8ms status=404 bytes=1829 
2014-05-07T19:11:45.398253+00:00 heroku[router]: at=info method=GET path=/ host=young-caverns-5100.herokuapp.com request_id=c9c8c2e3-86f2-492d-b738-d7ed4427abd5 fwd="24.5.234.171" dyno=web.1 connect=1ms service=10ms status=404 bytes=1829 
2014-05-07T19:11:45.664341+00:00 heroku[router]: at=info method=GET path=/favicon.ico host=young-caverns-5100.herokuapp.com request_id=061df699-108d-4776-b6c0-9a32db8efd22 fwd="24.5.234.171" dyno=web.1 connect=1ms service=83ms status=404 bytes=1829 
2014-05-07T19:11:48.467737+00:00 heroku[router]: at=info method=GET path=/home host=young-caverns-5100.herokuapp.com request_id=f884c580-3648-4bc5-913e-1a80d9563024 fwd="24.5.234.171" dyno=web.1 connect=7ms service=10ms status=404 bytes=1829 
2014-05-07T19:11:52.832857+00:00 heroku[router]: at=info method=GET path=/leads host=young-caverns-5100.herokuapp.com request_id=43807ebc-4e3e-48f6-b014-9198b8dba0b2 fwd="24.5.234.171" dyno=web.1 connect=5ms service=13ms status=404 bytes=1829 
2014-05-07T19:18:02.160375+00:00 heroku[web.1]: State changed from up to starting 
2014-05-07T19:18:05.171369+00:00 heroku[web.1]: Stopping all processes with SIGTERM 
2014-05-07T19:18:05.870522+00:00 app[web.1]: [2014-05-07 19:18:05] FATAL SignalException: SIGTERM 
2014-05-07T19:18:05.870530+00:00 app[web.1]: /app/vendor/ruby-2.0.0/lib/ruby/2.0.0/webrick/server.rb:170:in `select' 
2014-05-07T19:18:05.870533+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-05-07T19:18:05.870534+00:00 app[web.1]: /app/vendor/ruby-2.0.0/lib/ruby/2.0.0/webrick/server.rb:32:in `start' 
2014-05-07T19:18:05.870535+00:00 app[web.1]: /app/vendor/ruby-2.0.0/lib/ruby/2.0.0/webrick/server.rb:160:in `start' 
2014-05-07T19:18:05.870537+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-05-07T19:18:05.870539+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-05-07T19:18:05.870540+00:00 app[web.1]: /app/vendor/bundle/ruby/2.0.0/gems/railties-4.1.1/lib/rails/commands/server.rb:69:in `start' 
2014-05-07T19:18:05.870542+00:00 app[web.1]: /app/vendor/bundle/ruby/2.0.0/gems/railties-4.1.1/lib/rails/commands/commands_tasks.rb:81:in `block in server' 
2014-05-07T19:18:05.870544+00:00 app[web.1]: /app/vendor/bundle/ruby/2.0.0/gems/railties-4.1.1/lib/rails/commands/commands_tasks.rb:76:in `tap' 
2014-05-07T19:18:05.870551+00:00 app[web.1]: /app/vendor/bundle/ruby/2.0.0/gems/railties-4.1.1/lib/rails/commands/commands_tasks.rb:76:in `server' 
2014-05-07T19:18:05.870553+00:00 app[web.1]: /app/vendor/bundle/ruby/2.0.0/gems/railties-4.1.1/lib/rails/commands/commands_tasks.rb:40:in `run_command!' 
2014-05-07T19:18:05.870556+00:00 app[web.1]: bin/rails:8:in `require' 
2014-05-07T19:18:05.870555+00:00 app[web.1]: /app/vendor/bundle/ruby/2.0.0/gems/railties-4.1.1/lib/rails/commands.rb:17:in `<top (required)>' 
2014-05-07T19:18:05.870558+00:00 app[web.1]: bin/rails:8:in `<main>' 
2014-05-07T19:18:05.870625+00:00 app[web.1]: [2014-05-07 19:18:05] INFO going to shutdown ... 
2014-05-07T19:18:05.870698+00:00 app[web.1]: [2014-05-07 19:18:05] INFO WEBrick::HTTPServer#start done. 
2014-05-07T19:18:05.984386+00:00 app[web.1]: => Booting WEBrick 
2014-05-07T19:18:05.984394+00:00 app[web.1]: => Rails 4.1.1 application starting in production on http://0.0.0.0:6427 
2014-05-07T19:18:05.984396+00:00 app[web.1]: => Run `rails server -h` for more startup options 
2014-05-07T19:18:05.984398+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-05-07T19:18:05.984400+00:00 app[web.1]: => Ctrl-C to shutdown server 
2014-05-07T19:18:05.984402+00:00 app[web.1]: Exiting 
2014-05-07T19:18:08.381243+00:00 app[web.1]: [2014-05-07 19:18:08] INFO ruby 2.0.0 (2014-02-24) [x86_64-linux] 
2014-05-07T19:18:08.381212+00:00 app[web.1]: [2014-05-07 19:18:08] INFO WEBrick 1.3.1 
2014-05-07T19:18:08.381705+00:00 app[web.1]: [2014-05-07 19:18:08] INFO WEBrick::HTTPServer#start: pid=2 port=53268 
2014-05-07T19:18:08.432919+00:00 heroku[web.1]: State changed from starting to up 
2014-05-07T19:18:05.271399+00:00 heroku[web.1]: Starting process with command `bin/rails server -p 53268 -e production` 
2014-05-07T19:18:07.843876+00:00 heroku[web.1]: Process exited with status 143 

我已經看了許多其他SO帖子，嘗試修復，但我沒有得到任何地方。其他人的問題似乎也不涉及「地位143」。

我試圖改變到PostgreSQL在生產中，從「假」到「真」改變預編譯資產，運行分貝：遷移等等等等

我不知道這有什麼用該問題，但我昨天下載了this教程下載了Ruby/Rails /等。一年前我使用VirtualBox使用Ubuntu，並很容易地在Heroku上爲之前的類創建了默認應用程序。我不明白它不適用於我目前的設置。

Answer 1

似乎有些事情是不同的使用Rails 4.X與Heroku，我不知道。在Heroku的網站上關注this。工作得很好。

Answer 2

試試您的控制檯上的命令希望將工作

heroku restart worker.1 

它似乎在控制檯上像這樣

80:~/Desktop/hospitality$ heroku restart worker.1 

Restarting worker.1 dyno... done