I got got by a New Relic Gem / Heroku's New Relic plugin incompatibility today, so I thought I'd share it:
I had specified (via Gemfile) the newrelic gem for local development and profiling of a client's application awhile back. Gemfile.lock was set to 2.13.4. I haven't done a production deploy for the client in about two weeks until today, and when I did, the site wouldn't start: it was the generic "Application Error" you get when a dyno fails to spin up. `heroku logs` said that the plugin injected by Heroku during the production deploy couldn't require the "dependency_loader" file for New Relic. This is a recent requirement, added in 2.13.6 according to the newrelic gem changelog. However, the New Relic gem being loaded for this application was 2.13.4; so the Heroku New Relic plugin, trying to use this very recent (and in this case, unavailable) feature, failed miserably and caused the application to suffer downtime. The solution is to either upgrade Gemfile to specify 2.14.0 (2.13.6 final isn't published on Rubygems; only the beta version. 2.14.0 is the next up) or to remove new relic from the Gemfile and let Heroku handle that part, too, which works equally well. Googling this problem comes up with nothing, unfortunately, so I'm leaving this here for people who will be likewise affected. In the future, though, I'd like to see failing Heroku plugins not cause an entire production deploy to come to a screeching halt. -- 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.
