Viewing log files written to the filesystem on Heroku - ruby-on-rails

I have a gem (rails-latex) that is not functioning correctly on my app deployed to Heroku but works fine on my local app. I succeeded in installing pdflatex on Heroku so that is not the issue.
To debug this further, I would need to see the log file described in the Heroku logs
2014-03-23T04:32:21.431646+00:00 app[web.1]: This is pdfTeX, Version 3.1415926-2.4-1.40.13 (TeX Live 2012)
2014-03-23T04:32:21.431646+00:00 app[web.1]: \write18 enabled.
2014-03-23T04:32:21.450999+00:00 app[web.1]: entering extended mode
2014-03-23T04:32:21.458053+00:00 app[web.1]: Completed 500 Internal Server Error in 124ms
2014-03-23T04:32:21.458309+00:00 app[web.1]: Completed 500 Internal Server Error in 124ms
2014-03-23T04:32:21.462550+00:00 app[web.1]:
2014-03-23T04:32:21.462550+00:00 app[web.1]: ActionView::Template::Error (pdflatex failed: See /app/tmp/rails-latex/2--2591673647893672512/input.log for details):
2014-03-23T04:32:21.462550+00:00 app[web.1]: 8: \end{document}
2014-03-23T04:32:21.462550+00:00 app[web.1]: 7:
2014-03-23T04:32:21.462550+00:00 app[web.1]: app/views/layouts/menu.pdf.erbtex:9:in `_app_views_layouts_menu_pdf_erbtex___4209895480759438810_30701180'
2014-03-23T04:32:21.462550+00:00 app[web.1]: app/controllers/restaurants_controller.rb:29:in `menu'
2014-03-23T04:32:21.463589+00:00 app[web.1]: 7:
2014-03-23T04:32:21.463589+00:00 app[web.1]: 8: \end{document}
2014-03-23T04:32:21.462550+00:00 app[web.1]: 6: <%= yield %>
2014-03-23T04:32:21.462550+00:00 app[web.1]:
2014-03-23T04:32:21.463589+00:00 app[web.1]: app/views/layouts/menu.pdf.erbtex:9:in `_app_views_layouts_menu_pdf_erbtex___4209895480759438810_30701180'
2014-03-23T04:32:21.463589+00:00 app[web.1]:
2014-03-23T04:32:21.462550+00:00 app[web.1]:
2014-03-23T04:32:21.463589+00:00 app[web.1]: app/controllers/restaurants_controller.rb:29:in `menu'
2014-03-23T04:32:21.463589+00:00 app[web.1]:
2014-03-23T04:32:21.463589+00:00 app[web.1]:
2014-03-23T04:32:21.463589+00:00 app[web.1]: 6: <%= yield %>
2014-03-23T04:32:21.463589+00:00 app[web.1]: ActionView::Template::Error (pdflatex failed: See /app/tmp/rails-latex/2--2591673647893672512/input.log for details):
But since changes to Heroku's filesystem are not saved, I cannot view the input.log file. Is there any way to read this file or redirect it to the heroku logs?

You can look at the filesystem but just know that it would differ across dynos (if you've been writing files) and it will be lost when the dyno is restarted or the application is deployed.
To look at the file system perform:
heroku run bash
and you should be placed at the bash prompt for your application

Related

Heroku LocomotiveCMS site won't run in production - require': cannot load such file -- locomotive/wagon/standalone_server

I'm having a problem with my LocomotiveCMS site crashing whenever I deploy to Heroku. The site is quite old and had been working fine for several years, until I was forced to upgrade to a newer Heroku stack. This required upgrading Ruby and LCMS versions. My site runs fine locally but crashes on start up when deployed to Heroku with the following log messages:
2022-11-01T15:48:54.268743+00:00 heroku[web.1]: Starting process with command bundle exec rackup config.ru -p ${PORT:-5000}
2022-11-01T15:48:55.623656+00:00 app[web.1]: bundler: failed to load command: rackup (/app/vendor/bundle/ruby/2.7.0/bin/rackup)
2022-11-01T15:48:55.623933+00:00 app[web.1]: /app/config.ru:1:in require': cannot load such file -- locomotive/wagon/standalone_server (LoadError) 2022-11-01T15:48:55.623962+00:00 app[web.1]: from /app/config.ru:1:in block in '
2022-11-01T15:48:55.623964+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.7.0/gems/rack-2.2.4/lib/rack/builder.rb:116:in eval' 2022-11-01T15:48:55.623973+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.7.0/gems/rack-2.2.4/lib/rack/builder.rb:116:in new_from_string'
2022-11-01T15:48:55.623976+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.7.0/gems/rack-2.2.4/lib/rack/builder.rb:105:in load_file' 2022-11-01T15:48:55.623985+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.7.0/gems/rack-2.2.4/lib/rack/builder.rb:66:in parse_file'
2022-11-01T15:48:55.623987+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.7.0/gems/rack-2.2.4/lib/rack/server.rb:349:in build_app_and_options_from_config' 2022-11-01T15:48:55.624007+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.7.0/gems/rack-2.2.4/lib/rack/server.rb:249:in app'
2022-11-01T15:48:55.624009+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.7.0/gems/rack-2.2.4/lib/rack/server.rb:422:in wrapped_app' 2022-11-01T15:48:55.624019+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.7.0/gems/rack-2.2.4/lib/rack/server.rb:312:in block in start'
2022-11-01T15:48:55.624021+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.7.0/gems/rack-2.2.4/lib/rack/server.rb:379:in handle_profiling' 2022-11-01T15:48:55.624031+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.7.0/gems/rack-2.2.4/lib/rack/server.rb:311:in start'
2022-11-01T15:48:55.624033+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.7.0/gems/rack-2.2.4/lib/rack/server.rb:168:in start' 2022-11-01T15:48:55.624042+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.7.0/gems/rack-2.2.4/bin/rackup:5:in <top (required)>'
2022-11-01T15:48:55.624044+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.7.0/bin/rackup:23:in load' 2022-11-01T15:48:55.624054+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.7.0/bin/rackup:23:in <top (required)>'
2022-11-01T15:48:55.624056+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.7.0/gems/bundler-2.3.10/lib/bundler/cli/exec.rb:58:in load' 2022-11-01T15:48:55.624065+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.7.0/gems/bundler-2.3.10/lib/bundler/cli/exec.rb:58:in kernel_load'
2022-11-01T15:48:55.624067+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.7.0/gems/bundler-2.3.10/lib/bundler/cli/exec.rb:23:in run' 2022-11-01T15:48:55.624077+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.7.0/gems/bundler-2.3.10/lib/bundler/cli.rb:483:in exec'
2022-11-01T15:48:55.624079+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.7.0/gems/bundler-2.3.10/lib/bundler/vendor/thor/lib/thor/command.rb:27:in run' 2022-11-01T15:48:55.624088+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.7.0/gems/bundler-2.3.10/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in invoke_command'
2022-11-01T15:48:55.624090+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.7.0/gems/bundler-2.3.10/lib/bundler/vendor/thor/lib/thor.rb:392:in dispatch' 2022-11-01T15:48:55.624099+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.7.0/gems/bundler-2.3.10/lib/bundler/cli.rb:31:in dispatch'
2022-11-01T15:48:55.624121+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.7.0/gems/bundler-2.3.10/lib/bundler/vendor/thor/lib/thor/base.rb:485:in start' 2022-11-01T15:48:55.624123+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.7.0/gems/bundler-2.3.10/lib/bundler/cli.rb:25:in start'
2022-11-01T15:48:55.624132+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.7.0/gems/bundler-2.3.10/exe/bundle:48:in block in <top (required)>' 2022-11-01T15:48:55.624134+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.7.0/gems/bundler-2.3.10/lib/bundler/friendly_errors.rb:103:in with_friendly_errors'
2022-11-01T15:48:55.624143+00:00 app[web.1]: from /app/vendor/bundle/ruby/2.7.0/gems/bundler-2.3.10/exe/bundle:36:in <top (required)>' 2022-11-01T15:48:55.624145+00:00 app[web.1]: from /app/vendor/bundle/bin/bundle:113:in load'
2022-11-01T15:48:55.624155+00:00 app[web.1]: from /app/vendor/bundle/bin/bundle:113:in `'
2022-11-01T15:48:55.774101+00:00 heroku[web.1]: Process exited with status 1
2022-11-01T15:48:55.849654+00:00 heroku[web.1]: State changed from starting to crashed
I'm using Heroku-20 stack, Ruby 2.7.6 and gem locomotivecms_wagon 3.1.1
The site runs fine locally (using bundle exec wagon serve)
I've tried the Heroku-18 stack with the same result. I haven't been able to get the latest Heroku stack (22) to work as there is a Ruby version clash with LocomotiveCMS.
I tried using a Procfile (which I never needed before) - I used the standard puma Procfile as shown in the Heroku doc but couldn't get that to work either.
I've also tried deleting Gemfile.lock, running bundle install and bundle update, but no change.

Failed to Load Command Puma: NameError: Wrong Constant Name 'Model-Names' Copy

Just deployed to Heroku and successfullly migrated db. But site crashed with error saying there is 'NameError: Wrong Constant Name Companies Copy' where i have a Company model.
Using Rails 6.0.0.rc1
Ruby version 2.6.3
Checked through the entire code and confirmed that i did not initialize anything with the plural "Companies" name.
have checked through blogs and stackoverflow... there is no specific way to identify this issues.
2019-07-15T03:39:08.124899+00:00 heroku[web.1]: Starting process with command `bundle exec puma -p 28862`
2019-07-15T03:39:10.206749+00:00 app[web.1]: Puma starting in single mode...
2019-07-15T03:39:10.206793+00:00 app[web.1]: * Version 3.12.1 (ruby 2.6.3-p62), codename: Llamas in Pajamas
2019-07-15T03:39:10.206795+00:00 app[web.1]: * Min threads: 5, max threads: 5
2019-07-15T03:39:10.206797+00:00 app[web.1]: * Environment: production
2019-07-15T03:39:14.734930+00:00 app[web.1]: ! Unable to load application: NameError: wrong constant name Companies copy
2019-07-15T03:39:14.735052+00:00 app[web.1]: bundler: failed to load command: puma (/app/vendor/bundle/ruby/2.6.0/bin/puma)
2019-07-15T03:39:14.735115+00:00 app[web.1]: NameError: wrong constant name Companies copy
2019-07-15T03:39:14.735118+00:00 app[web.1]: /app/vendor/bundle/ruby/2.6.0/gems/zeitwerk-2.1.8/lib/zeitwerk/loader.rb:679:in `const_defined?'
2019-07-15T03:39:14.735120+00:00 app[web.1]: /app/vendor/bundle/ruby/2.6.0/gems/zeitwerk-2.1.8/lib/zeitwerk/loader.rb:679:in `cdef?'
2019-07-15T03:39:14.735122+00:00 app[web.1]: /app/vendor/bundle/ruby/2.6.0/gems/zeitwerk-2.1.8/lib/zeitwerk/loader.rb:597:in `strict_autoload_path' 2019-07-15T03:39:14.735124+00:00 app[web.1]: /app/vendor/bundle/ruby/2.6.0/gems/zeitwerk-2.1.8/lib/zeitwerk/loader.rb:574:in `autoload_for?'
2019-07-15T03:39:14.735126+00:00 app[web.1]: /app/vendor/bundle/ruby/2.6.0/gems/zeitwerk-2.1.8/lib/zeitwerk/loader.rb:488:in `autoload_subdir'
2019-07-15T03:39:14.735128+00:00 app[web.1]: /app/vendor/bundle/ruby/2.6.0/gems/zeitwerk-2.1.8/lib/zeitwerk/loader.rb:477:in `block in set_autoloads_in_dir'
2019-07-15T03:39:14.735130+00:00 app[web.1]: /app/vendor/bundle/ruby/2.6.0/gems/zeitwerk-2.1.8/lib/zeitwerk/loader.rb:649:in `block in ls'
2019-07-15T03:39:14.735132+00:00 app[web.1]: /app/vendor/bundle/ruby/2.6.0/gems/zeitwerk-2.1.8/lib/zeitwerk/loader.rb:646:in `foreach'
2019-07-15T03:39:14.735134+00:00 app[web.1]: /app/vendor/bundle/ruby/2.6.0/gems/zeitwerk-2.1.8/lib/zeitwerk/loader.rb:646:in `ls'
2019-07-15T03:39:14.735136+00:00 app[web.1]: /app/vendor/bundle/ruby/2.6.0/gems/zeitwerk-2.1.8/lib/zeitwerk/loader.rb:463:in `set_autoloads_in_dir'
2019-07-15T03:39:14.735138+00:00 app[web.1]: /app/vendor/bundle/ruby/2.6.0/gems/zeitwerk-2.1.8/lib/zeitwerk/loader/callbacks.rb:65:in `block in on_namespace_loaded'
2019-07-15T03:39:14.735139+00:00 app[web.1]: /app/vendor/bundle/ruby/2.6.0/gems/zeitwerk-2.1.8/lib/zeitwerk/loader/callbacks.rb:64:in `each'
2019-07-15T03:39:14.735141+00:00 app[web.1]: /app/vendor/bundle/ruby/2.6.0/gems/zeitwerk-2.1.8/lib/zeitwerk/loader/callbacks.rb:64:in `on_namespace_loaded'
2019-07-15T03:39:14.735142+00:00 app[web.1]: /app/vendor/bundle/ruby/2.6.0/gems/zeitwerk-2.1.8/lib/zeitwerk/loader/callbacks.rb:50:in `block in on_dir_autoloaded'
2019-07-15T03:39:14.735144+00:00 app[web.1]: /app/vendor/bundle/ruby/2.6.0/gems/zeitwerk-2.1.8/lib/zeitwerk/loader/callbacks.rb:37:in `synchronize'
2019-07-15T03:39:14.735145+00:00 app[web.1]: /app/vendor/bundle/ruby/2.6.0/gems/zeitwerk-2.1.8/lib/zeitwerk/loader/callbacks.
Hope anyone with similar experience can at least point me to where to look to solve or dissect this issue further.
Many thanks.
UPDATE:
Found a quick fix. The reason the error was raise was due to autoloading with with zeitwerk which is the default autoloader for rails 6.
I have not found the reason as to why I had the NameError. So, in the application.rb file, I reverted the autoloading back to the classic version which was used for rails before version 6. After that everything went well.
config.load_defaults "6.x"
config.autoloader = :classic

Heroku rails installation stopped working after month

I set up this super simple rails app about 5 month ago and it worked until lately.
But today i noticed im getting this error: "We're sorry, but something went wrong. If you are the application owner check the logs for more information."
I checked the heroku logs but i dont see any errors appart from what i assume is the daily restart:
2017-02-11T01:37:52.624288+00:00 heroku[router]: at=info method=GET path="/favicon.ico" host=url.herokuapp.com request_id=918be0b7-bf45-4111-97b8-d95450dd3507 fwd="126.7.114.122" dyno=web.1 connect=0ms service=4ms status=200 bytes=228
2017-02-11T01:38:45.926088+00:00 heroku[web.1]: Restarting
2017-02-11T01:38:45.927276+00:00 heroku[web.1]: State changed from up to starting
2017-02-11T01:38:46.437082+00:00 app[web.1]: [2017-02-11 01:38:46] FATAL SignalException: SIGTERM
2017-02-11T01:38:46.437099+00:00 app[web.1]: /app/vendor/ruby-2.2.4/lib/ruby/2.2.0/webrick/server.rb:174:in `select'
2017-02-11T01:38:46.437100+00:00 app[web.1]: /app/vendor/ruby-2.2.4/lib/ruby/2.2.0/webrick/server.rb:174:in `block in start'
2017-02-11T01:38:46.437101+00:00 app[web.1]: /app/vendor/ruby-2.2.4/lib/ruby/2.2.0/webrick/server.rb:32:in `start'
2017-02-11T01:38:46.437102+00:00 app[web.1]: /app/vendor/ruby-2.2.4/lib/ruby/2.2.0/webrick/server.rb:162:in `start'
2017-02-11T01:38:46.437103+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/rack-1.6.4/lib/rack/handler/webrick.rb:34:in `run'
2017-02-11T01:38:46.437103+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/rack-1.6.4/lib/rack/server.rb:286:in `start'
2017-02-11T01:38:46.437104+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/railties-4.2.6/lib/rails/commands/server.rb:80:in `start'
2017-02-11T01:38:46.437105+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/railties-4.2.6/lib/rails/commands/commands_tasks.rb:80:in `block in server'
2017-02-11T01:38:46.437105+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/railties-4.2.6/lib/rails/commands/commands_tasks.rb:75:in `tap'
2017-02-11T01:38:46.437106+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/railties-4.2.6/lib/rails/commands/commands_tasks.rb:75:in `server'
2017-02-11T01:38:46.437106+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/railties-4.2.6/lib/rails/commands/commands_tasks.rb:39:in `run_command!'
2017-02-11T01:38:46.437107+00:00 app[web.1]: /app/vendor/bundle/ruby/2.2.0/gems/railties-4.2.6/lib/rails/commands.rb:17:in `<top (required)>'
2017-02-11T01:38:46.437108+00:00 app[web.1]: bin/rails:9:in `require'
2017-02-11T01:38:46.437109+00:00 app[web.1]: bin/rails:9:in `<main>'
2017-02-11T01:38:46.437176+00:00 app[web.1]: [2017-02-11 01:38:46] INFO going to shutdown ...
2017-02-11T01:38:46.437226+00:00 app[web.1]: [2017-02-11 01:38:46] INFO WEBrick::HTTPServer#start done.
I also took a look at my production.log file but it's weirdly empty.
I'm at a loss regarding how to trouble shoot this. any suggestion?
So, it turned out it wasnt actually related to the environment.
I ran the site on my machine with the prod env and was able to find an access_token was expired which error wasnt caught correctly causing the 500 error.
I fixed it and redeployed the site. it works now.

heroku looking for a staging.log file?

Our heroku staging app is crashing on start up due to not being able to find a staging.log . This seems pretty odd since it should just be outputting everything to development.log, so I am not exactly sure what is going on.
Any help would be greatly appreciated! Thanks!
Here is the stack trace:
2012-04-18T19:20:36+00:00 heroku[web.1]: State changed from crashed to created
2012-04-18T19:20:36+00:00 heroku[web.1]: State changed from created to starting
2012-04-18T19:20:37+00:00 heroku[slugc]: Slug compilation finished
2012-04-18T19:20:40+00:00 heroku[web.1]: Starting process with command `bundle exec rails server -p 49887`
2012-04-18T19:20:46+00:00 app[web.1]: => Booting WEBrick
2012-04-18T19:20:46+00:00 app[web.1]: => Rails 3.0.3 application starting in staging on http://0.0.0.0:49887
2012-04-18T19:20:46+00:00 app[web.1]: => Call with -d to detach
2012-04-18T19:20:46+00:00 app[web.1]: => Ctrl-C to shutdown server
2012-04-18T19:20:46+00:00 app[web.1]: Exiting
2012-04-18T19:20:46+00:00 app[web.1]: /app/vendor/bundle/ruby/1.9.1/gems/railties-3.0.3/lib/rails/rack/log_tailer.rb:8:in `size': No such file or directory - log/staging.log (Errno::ENOENT)
2012-04-18T19:20:46+00:00 app[web.1]: from /app/vendor/bundle/ruby/1.9.1/gems/railties-3.0.3/lib/rails/rack/log_tailer.rb:8:in `initialize'
2012-04-18T19:20:46+00:00 app[web.1]: from /app/vendor/bundle/ruby/1.9.1/gems/rack-1.2.5/lib/rack/server.rb:247:in `new'
2012-04-18T19:20:46+00:00 app[web.1]: from /app/vendor/bundle/ruby/1.9.1/gems/rack-1.2.5/lib/rack/server.rb:247:in `block in build_app'
2012-04-18T19:20:46+00:00 app[web.1]: from /app/vendor/bundle/ruby/1.9.1/gems/rack-1.2.5/lib/rack/server.rb:243:in `reverse_each'
2012-04-18T19:20:46+00:00 app[web.1]: from /app/vendor/bundle/ruby/1.9.1/gems/rack-1.2.5/lib/rack/server.rb:243:in `build_app'
2012-04-18T19:20:46+00:00 app[web.1]: from /app/vendor/bundle/ruby/1.9.1/gems/rack-1.2.5/lib/rack/server.rb:253:in `wrapped_app'
2012-04-18T19:20:46+00:00 app[web.1]: from /app/vendor/bundle/ruby/1.9.1/gems/rack-1.2.5/lib/rack/server.rb:204:in `start'
2012-04-18T19:20:46+00:00 app[web.1]: from /app/vendor/bundle/ruby/1.9.1/gems/railties-3.0.3/lib/rails/commands/server.rb:65:in `start'
2012-04-18T19:20:46+00:00 app[web.1]: from /app/vendor/bundle/ruby/1.9.1/gems/railties-3.0.3/lib/rails/commands.rb:30:in `block in <top (required)>'
2012-04-18T19:20:46+00:00 app[web.1]: from /app/vendor/bundle/ruby/1.9.1/gems/railties-3.0.3/lib/rails/commands.rb:27:in `tap'
2012-04-18T19:20:46+00:00 app[web.1]: from /app/vendor/bundle/ruby/1.9.1/gems/railties-3.0.3/lib/rails/commands.rb:27:in `<top (required)>'
2012-04-18T19:20:46+00:00 app[web.1]: from script/rails:6:in `require'
2012-04-18T19:20:46+00:00 app[web.1]: from script/rails:6:in `<main>'
2012-04-18T19:20:47+00:00 heroku[web.1]: Process exited with status 1
2012-04-18T19:20:47+00:00 heroku[web.1]: State changed from starting to crashed
Your app should be outputting its logs to STDOUT, not to a file on the server. See the logging article on the Dev Center for details: https://devcenter.heroku.com/articles/logging
Heroku automatically injects the rails_log_stdout to your app on deploy which fixes Rails default logging, so I'm not sure why that isn't happening here. Do you see the following lines output when you deploy to Heroku?
-----> Rails plugin injection
Injecting rails_log_stdout
Injecting rails3_serve_static_assets
If you have a config/environments/staging.rb file ensure that you've set both your RACK_ENV and RAILS_ENV to 'staging'.
heroku config:add RACK_ENV=staging --app myapp-staging
heroku config:add RAILS_ENV=staging --app myapp-staging
Do you have a Procfile that specifies which environement you want to run? I don't believe this is required by Heroku, but it allows you to specify the enviornment, among other things.

Pages not rendering properly on Heroku

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.
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.
I am add a part of the logfile. I wish I could show snapshots but unfortunately I don't have rights to do so.
I would appreciate any help and tips on debugging this problem.
====logfile===========================================
2012-03-19T18:22:42+00:00 heroku[web.1]: State changed from starting to up
2012-03-19T18:22:43+00:00 app[web.1]: => Booting WEBrick
2012-03-19T18:22:43+00:00 app[web.1]: => Rails 3.2.0 application starting in production on http://0.0.0.0:36524
2012-03-19T18:22:43+00:00 app[web.1]: => Call with -d to detach
2012-03-19T18:22:43+00:00 app[web.1]: => Ctrl-C to shutdown server
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
2012-03-19T18:22:44+00:00 app[web.1]: Processing by StaticPagesController#home as HTML
2012-03-19T18:22:44+00:00 app[web.1]: Rendered static_pages/home.html.erb within layouts/application (11.2ms)
2012-03-19T18:22:44+00:00 app[web.1]: Rendered layouts/_shim.html.erb (0.2ms)
2012-03-19T18:22:44+00:00 app[web.1]: Rendered layouts/_header.html.erb (1.9ms)
2012-03-19T18:22:44+00:00 app[web.1]: Rendered layouts/_footer.html.erb (1.5ms)
2012-03-19T18:22:44+00:00 app[web.1]: Completed 200 OK in 76ms (Views: 75.7ms | ActiveRecord: 0.0ms)
2012-03-19T18:22:44+00:00 app[web.1]: cache: [GET /] miss
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
2012-03-19T18:22:47+00:00 heroku[web.1]: State changed from up to bouncing
2012-03-19T18:22:47+00:00 heroku[web.1]: State changed from bouncing to created
2012-03-19T18:22:47+00:00 heroku[web.1]: State changed from created to starting
2012-03-19T18:22:51+00:00 heroku[web.1]: Stopping process with SIGTERM
2012-03-19T18:22:51+00:00 app[web.1]: [2012-03-19 18:22:51] ERROR SignalException: SIGTERM
2012-03-19T18:22:51+00:00 app[web.1]: /usr/local/lib/ruby/1.9.1/webrick/server.rb:90:in `select'
2012-03-19T18:22:55+00:00 heroku[web.1]: Starting process with command bundle exec rails server -p 4160
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)
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)
2012-03-19T18:23:01+00:00 heroku[web.1]: Stopping process with SIGKILL
2012-03-19T18:23:01+00:00 heroku[web.1]: Error R12 (Exit timeout) -> Process failed to exit within 10 seconds of SIGTERM
2012-03-19T18:23:02+00:00 heroku[web.1]: Process exited with status 137
2012-03-19T18:23:04+00:00 app[web.1]: [2012-03-19 18:23:04] INFO WEBrick 1.3.1
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]
2012-03-19T18:23:04+00:00 app[web.1]: [2012-03-19 18:23:04] INFO WEBrick::HTTPServer#start: pid=1 port=4160
2012-03-19T18:23:05+
I hope you don't mind but I took the liberty of going to your site myself to see what the problem is. The issue is that you're configuring to use the asset pipeline but none of your assets are compiled. You can verify this is the case by visiting your main CSS file -- you'll notice there's nothing at all there.
This is likely because you forgot to include compilation directives at the top of your application.css. See the asset pipeline guide for full details, but I bet you're missing a line like this at the top of your application.css:
*= require_self
*= require_tree .
I had this problem before too, and I think it had something to do with precompiling your css file. Try going into config/environments/production.rb and add this config.assets.precompile += [ "blueprint/*.css" ]. I am assuming you're using the blueprint css file.

Resources