StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POIssue launching app on Heroku: requires different GEMS?
text
Body
copied!<p>I'm trying to push an app to Heroku ... and everything goes well, except that I see an error page when I try to actually view it on Heroku.</p> <p>On my machine, it works fine though. I followed the basic steps to get a Hello World example going on Heroku and that worked fine on my machine as well as on Heroku ... but my app seems to be having some weird issues.</p> <p>The push works fine, everything seems to setup correctly, but this is what the logs say:</p> <blockquote> <p>2011-07-09T03:32:01+00:00 app[web.1]: /usr/ruby1.9.2/lib/ruby/gems/1.9.1/gems/bundler-1.0.7/lib/bundler/runtime.rb:27:in `block in setup': You have already activated daemons 1.1.0, but your Gemfile requires daemons 1.0.10. Consider using bundle exec. (Gem::LoadError)</p> <p>...</p> <p>2011-07-09T03:32:35+00:00 heroku[router]: Error H10 (App crashed) -> GET high-sunrise-670.heroku.com/ dyno= queue= wait= service= status=503 bytes= 2011-07-09T03:32:36+00:00 heroku[router]: Error H10 (App crashed) -> GET high-sunrise-670.heroku.com/favicon.ico dyno= queue= wait= service= status=503 bytes= 2011-07-09T03:32:36+00:00 heroku[router]: Error H10 (App crashed) -> GET high-sunrise-670.heroku.com/favicon.ico dyno= queue= wait= service= status=503 bytes= 2011-07-09T03:40:25+00:00 heroku[router]: Error H10 (App crashed) -> GET high-sunrise-670.heroku.com/ dyno= queue= wait= service= status=503 bytes=</p> </blockquote> <p>I'm very new to this stuff, so I'm sorry if this is a silly question. I don't get why it requires an older daemons version. I checked my Gemfile and nothing required that specifically. I then checked my Gemfile.lock and it says GEM requires it. No idea what that means though (or why Heroku has issues with it ...). Can I change that somehow?</p> <p>Thanks a lot!</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

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