Heroku app crashing
My guess is that you forgot to set up the production database. Perhaps...
$ heroku rake db:setup
or $ heroku rake db:push
...is needed?
Update: Aha! Going by your error message in the comment, you have an unresolved merge conflict in application_helper.rb.
That's what those <<<<<<
lines are, something inserted by git (or perhaps some local SCCS you are using) that usually point out conflicts between a branch and local changes.
Start with "git status" and also just look at application_helper.rb
in your editor.
Justin Meltzer
Updated on November 20, 2022Comments
-
Justin Meltzer over 1 year
I've just deployed my RoR app to Heroku, and the app works on my local port, but when I visit the Heroku address I get:
App crashed This application is temporarily offline. If you're the administrator of this app, please check your heroku logs for the backtrace.
This may be the error that I found in the logs:
2011-02-25T17:08:25-08:00 heroku[router]: Error H10 (App crashed) -> GET afternoon-warrior-452.heroku.com/ dyno=none queue=0 wait=0ms service=0ms bytes=0 2011-02-25T17:08:25-08:00 heroku[router]: Error H10 (App crashed) -> GET afternoon-warrior-452.heroku.com/favicon.ico dyno=none queue=0 wait=0ms service=0ms bytes=0
How do I fix this?
-
Justin Meltzer about 13 yearsI found this from the logs. Could this be the error?
2011-02-25T17:08:25-08:00 heroku[router]: Error H10 (App crashed) -> GET afternoon-warrior-452.heroku.com/ dyno=none queue=0 wait=0ms service=0ms bytes=0 2011-02-25T17:08:25-08:00 heroku[router]: Error H10 (App crashed) -> GET afternoon-warrior-452.heroku.com/favicon.ico dyno=none queue=0 wait=0ms service=0ms bytes=0
-
afraziz about 13 yearsThat only tells us that there was an error, not really what happened. Trying running
heroku restart
and thenheroku logs
right away to see if anything interesting shows up. -
Justin Meltzer about 13 yearsHere's some strange stuff:
2011-02-25T17:09:08-08:00 app[web.1]: /app/8d489c6f-7838-45ee-bc56-f2e2e72a0a94/home/.bundle/gems/ruby/1.8/gems/activesupport-3.0.4/lib/active_support/dependencies.rb:239:in require': /app/8d489c6f-7838-45ee-bc56-f2e2e72a0a94/home/app/helpers/application_helper.rb:2: syntax error, unexpected tLSHFT, expecting kEND (SyntaxError) 2011-02-25T17:09:08-08:00 app[web.1]: ^
-
Justin Meltzer about 13 years
2011-02-25T17:09:08-08:00 app[web.1]: /app/8d489c6f-7838-45ee-bc56-f2e2e72a0a94/home/app/helpers/application_helper.rb:15: syntax error, unexpected tLSHFT, expecting kEND 2011-02-25T17:09:08-08:00 app[web.1]: <<<<<<< HEAD 2011-02-25T17:09:08-08:00 app[web.1]: ^ 2011-02-25T17:09:08-08:00 app[web.1]: /app/8d489c6f-7838-45ee-bc56-f2e2e72a0a94/home/app/helpers/application_helper.rb:17: syntax error, unexpected tEQQ, expecting $end 2011-02-25T17:09:08-08:00 app[web.1]: ^ 2011-02-25T17:09:08-08:00 app[web.1]: =======
-
Justin Meltzer about 13 yearsNo I don't think this is it. Check out some of the logs I've reproduced below jdl's answer. The error may be in there.
-
afraziz about 13 yearsLooks like a code bug. Post your
application_helper.rb
file in your original question and let's see. How well is this app unit tested, because something like that should be blowing up on any functional test case. -
Justin Meltzer about 13 yearsahh yes, i think this is it. But I thought I had fixed the merge conflict manually...
-
Justin Meltzer about 13 years
# modified: app/helpers/application_helper.rb
# modified: app/views/layouts/application.html.erb
This is what I get referring toapplication_helper.rb
when I rungit status
I originally cleaned up those<<<<<<
in my text editor but I'm guessing that wasn't enough. Not sure what to do now though. -
Justin Meltzer about 13 yearsahhh ok! Just figured it out. Thanks digitalross!