I had this issue this week and Heroku support suggested I disable New Relic add-on since their updated gem didn't play nice with Delayed Job. I did, and it immediately started working again.
Heroku guys, any idea when we'll be able to re-enable New Relic? On Fri, Feb 19, 2010 at 6:38 PM, Higgaion <[email protected]>wrote: > My jobs don't seem to be running automatically, so I tried to start a > worker with heroku rake: > > heroku rake --trace jobs:work > (in /disk1/home/slugs/125600_b30055f_55f0/mnt) > ** Invoke jobs:work (first_time) > ** Invoke merb_env (first_time) > ** Execute merb_env > ** Invoke environment (first_time) > ** Execute environment > ** Execute jobs:work > rake aborted! > undefined method `info' for nil:NilClass > /disk1/home/slugs/125600_b30055f_55f0/mnt/vendor/plugins/rpm/lib/ > new_relic/delayed_job_injection.rb:18:in `initialize' > : > : > > Two general categories of questions come to mind: > > 1) What is that new_relic thing trying to do? where is the source code > for that? what info? where am I? > > 2) How to I fix it? > > -- > 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]<heroku%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en. > > -- 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.
