Note that there are some explanatory texts on larger screens.

plurals
  1. POPages not rendering properly on Heroku
    primarykey
    data
    text
    <p>Hi I am in the midst of Ruby on Rails tutorial. MY pages are rendering perfectly on the localserver but NOT on Heroku. I have run the command "heroku run rake db:migrate". I also have gone through the Heroku logs. I am just not sure how to read them.</p> <p>I am wondering if it has to do with my stylesheets but I replicated whatever was on my local server to github and heroku so not sure why it can't read it.</p> <p>I am add a part of the logfile. I wish I could show snapshots but unfortunately I don't have rights to do so.</p> <p>I would appreciate any help and tips on debugging this problem.</p> <p>====logfile===========================================</p> <p>2012-03-19T18:22:42+00:00 heroku[web.1]: State changed from starting to up </p> <p>2012-03-19T18:22:43+00:00 app[web.1]: => Booting WEBrick</p> <p>2012-03-19T18:22:43+00:00 app[web.1]: => Rails 3.2.0 application starting in production on <a href="http://0.0.0.0:36524" rel="nofollow">http://0.0.0.0:36524</a></p> <p>2012-03-19T18:22:43+00:00 app[web.1]: => Call with -d to detach</p> <p>2012-03-19T18:22:43+00:00 app[web.1]: => Ctrl-C to shutdown server</p> <p>2012-03-19T18:22:43+00:00 app[web.1]: 2012-03-19T18:22:43+00:00 app[web.1]: 2012-03-19T18:22:43+00:00 app[web.1]: Started GET "/" for 68.81.36.121 at 2012-03-19 18:22:43 +0000</p> <p>2012-03-19T18:22:44+00:00 app[web.1]: Processing by StaticPagesController#home as HTML</p> <p>2012-03-19T18:22:44+00:00 app[web.1]: Rendered static_pages/home.html.erb within layouts/application (11.2ms)</p> <p>2012-03-19T18:22:44+00:00 app[web.1]: Rendered layouts/_shim.html.erb (0.2ms)</p> <p>2012-03-19T18:22:44+00:00 app[web.1]: Rendered layouts/_header.html.erb (1.9ms)</p> <p>2012-03-19T18:22:44+00:00 app[web.1]: Rendered layouts/_footer.html.erb (1.5ms)</p> <p>2012-03-19T18:22:44+00:00 app[web.1]: Completed 200 OK in 76ms (Views: 75.7ms | ActiveRecord: 0.0ms)</p> <p>2012-03-19T18:22:44+00:00 app[web.1]: cache: [GET /] miss</p> <p>2012-03-19T18:22:44+00:00 heroku[router]: GET stormy-mist-1232.herokuapp.com/ dyno=web.1 queue=0 wait=0ms service=850ms status=304 bytes=0</p> <p>2012-03-19T18:22:47+00:00 heroku[web.1]: State changed from up to bouncing</p> <p>2012-03-19T18:22:47+00:00 heroku[web.1]: State changed from bouncing to created</p> <p>2012-03-19T18:22:47+00:00 heroku[web.1]: State changed from created to starting</p> <p>2012-03-19T18:22:51+00:00 heroku[web.1]: Stopping process with SIGTERM</p> <p>2012-03-19T18:22:51+00:00 app[web.1]: [2012-03-19 18:22:51] ERROR SignalException: SIGTERM</p> <p>2012-03-19T18:22:51+00:00 app[web.1]: /usr/local/lib/ruby/1.9.1/webrick/server.rb:90:in `select'</p> <p>2012-03-19T18:22:55+00:00 heroku[web.1]: Starting process with command <code>bundle exec rails server -p 4160</code></p> <p>2012-03-19T18:22:59+00:00 app[web.1]: DEPRECATION WARNING: You have Rails 2.3-style plugins in vendor/plugins! Support for these plugins will be removed in Rails 4.0. Move them out and bundle them in your Gemfile, or fold them in to your app as lib/myplugin/* and config/initializers/myplugin.rb. See the release notes for more on this: "http://weblog.rubyonrails.org/2012/01/04/rails-3-2-0-rc2-has-been-released." (called from at /app/config/environment.rb:5)</p> <p>2012-03-19T18:22:59+00:00 app[web.1]: DEPRECATION WARNING: You have Rails 2.3-style plugins in vendor/plugins! Support for these plugins will be removed in Rails 4.0. Move them out and bundle them in your Gemfile, or fold them in to your app as lib/myplugin/* and config/initializers/myplugin.rb. See the release notes for more on this: "http://weblog.rubyonrails.org/2012/01/04/rails-3-2-0-rc2-has-been-released". (called from at /app/config/environment.rb:5)</p> <p>2012-03-19T18:23:01+00:00 heroku[web.1]: Stopping process with SIGKILL</p> <p>2012-03-19T18:23:01+00:00 heroku[web.1]: Error R12 (Exit timeout) -> Process failed to exit within 10 seconds of SIGTERM</p> <p>2012-03-19T18:23:02+00:00 heroku[web.1]: Process exited with status 137</p> <p>2012-03-19T18:23:04+00:00 app[web.1]: [2012-03-19 18:23:04] INFO WEBrick 1.3.1</p> <p>2012-03-19T18:23:04+00:00 app[web.1]: [2012-03-19 18:23:04] INFO ruby 1.9.2 (2011-07-09) [x86_64-linux]</p> <p>2012-03-19T18:23:04+00:00 app[web.1]: [2012-03-19 18:23:04] INFO WEBrick::HTTPServer#start: pid=1 port=4160</p> <h1>2012-03-19T18:23:05+</h1>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload