That didn't work, thanks for the idea though. Here's the code: https://github.com/jeffayle/TV-Tracker (please excuse the incredibly embarrassing commit messages)
On Feb 13, 11:11 am, Jesse House <[email protected]> wrote: > I have a rails app that referenced aws-s3. last time I uploaded my > code the gems were re-imported and I ended up with builder 3.0.0 (aws- > s3 depends on builder); this caused a lot of other code to start > failing. > > I had to specify builder -v 2.1.2, I am only bringing this up since I > see errors in builder in your stacktrace, in my case it was a local > gem not part of the heroku stack > > try to specify builder -v 2.1.2 in .gem or bundler? > > On Feb 12, 11:38 am, Jeffrey Aylesworth <[email protected]> wrote: > > > I have a Sinatra app working on my local computer, but when I send it > > to heroku, it crashes. The error log says: > > > 2011-02-12T11:36:50-08:00 app[web.1]: from /home/heroku_rack/ > > heroku.ru:18 > > 2011-02-12T11:36:50-08:00 app[web.1]: from /usr/ruby1.8.7/lib/ruby/ > > gems/1.8/gems/rack-1.0.1/lib/rack/builder.rb:29:in `instance_eval' > > 2011-02-12T11:36:50-08:00 app[web.1]: from /usr/ruby1.8.7/lib/ruby/ > > gems/1.8/gems/rack-1.0.1/lib/rack/builder.rb:29:in `initialize' > > 2011-02-12T11:36:50-08:00 app[web.1]: from /home/heroku_rack/ > > heroku.ru:11:in `new' > > 2011-02-12T11:36:50-08:00 app[web.1]: from /home/heroku_rack/ > > heroku.ru:11 > > 2011-02-12T11:36:50-08:00 app[web.1]: from /usr/ruby1.8.7/lib/ruby/ > > gems/1.8/gems/rack-1.0.1/lib/rack/builder.rb:29:in `instance_eval' > > 2011-02-12T11:36:50-08:00 app[web.1]: from /usr/ruby1.8.7/lib/ruby/ > > gems/1.8/gems/rack-1.0.1/lib/rack/builder.rb:29:in `initialize' > > 2011-02-12T11:36:50-08:00 app[web.1]: from /home/heroku_rack/ > > heroku.ru:1:in `new' > > 2011-02-12T11:36:50-08:00 app[web.1]: from /home/heroku_rack/ > > heroku.ru:1 > > 2011-02-12T11:36:50-08:00 heroku[web.1]: State changed from starting > > to crashed > > 2011-02-12T11:36:55-08:00 heroku[router]: Error H10 (App crashed) -> > > GET deep-ice-593.heroku.com/ dyno=none queue=0 wait=0ms service=0ms > > bytes=0 > > 2011-02-12T11:36:55-08:00 heroku[router]: Error H10 (App crashed) -> > > GET deep-ice-593.heroku.com/favicon.ico dyno=none queue=0 wait=0ms > > service=0ms bytes=0 > > 2011-02-12T11:36:55-08:00 heroku[nginx]: GET /favicon.ico HTTP/1.1 | > > 24.57.83.182 | 3310 | http | 500 > > 2011-02-12T11:36:55-08:00 heroku[nginx]: GET / HTTP/1.1 | 24.57.83.182 > > | 3310 | http | 500 > > 2011-02-12T11:36:55-08:00 heroku[router]: Error H10 (App crashed) -> > > GET deep-ice-593.heroku.com/favicon.ico dyno=none queue=0 wait=0ms > > service=0ms bytes=0 > > 2011-02-12T11:36:55-08:00 heroku[nginx]: GET /favicon.ico HTTP/1.1 | > > 24.57.83.182 | 3310 | http | 500 > > 2011-02-12T11:36:58-08:00 heroku[router]: Error H10 (App crashed) -> > > GET deep-ice-593.heroku.com/ dyno=none queue=0 wait=0ms service=0ms > > bytes=0 > > 2011-02-12T11:36:58-08:00 heroku[nginx]: GET / HTTP/1.1 | 24.57.83.182 > > | 3310 | http | 500 > > 2011-02-12T11:36:58-08:00 heroku[router]: Error H10 (App crashed) -> > > GET deep-ice-593.heroku.com/favicon.ico dyno=none queue=0 wait=0ms > > service=0ms bytes=0 > > 2011-02-12T11:36:58-08:00 heroku[nginx]: GET /favicon.ico HTTP/1.1 | > > 24.57.83.182 | 3310 | http | 500 > > > Which means nothing to me because it does not mention any of my own > > files, as far as I can see. > > > Has anyone had this before, and know what might be causing the > > problem? > > > Thanks. -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
