Yep, that's the same issue I was running into on 1.9.1. Opened a support ticket w/ heroku, after a while they finally told me I shouldn't be running beta stacks (1.9.1 is a beta stack, FYI) in production mode, and to downgrade to 1.8.7.
It's an issue with the latest bundler + 1.9.1 -- there's a ticket open about it on the bundler github issues page. On Aug 18, 10:38 pm, jmay <[email protected]> wrote: > I've been running without problems on ruby 1.9.1 for a couple of > months. Has anything else changed in the stack recently that might be > related to worker problems? > > Here's the log you suggested. Definitely blows up. Shouldn't there > be some sort of notification for this? > > $ heroku rake jobs:work > /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:32: > warning: already initialized constant RAKEVERSION > /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake/ > alt_system.rb:32: warning: already initialized constant WINDOWS > WARNING: Possible conflict with Rake extension: String#ext already > exists > WARNING: Possible conflict with Rake extension: String#pathmap already > exists > /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:404: > warning: already initialized constant EMPTY_TASK_ARGS > /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:452: > warning: already initialized constant EMPTY > /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:960: > warning: already initialized constant RUBY_EXT > /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:964: > warning: already initialized constant RUBY > /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:1033: > warning: already initialized constant LN_SUPPORTED > /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:1242: > warning: already initialized constant ARRAY_METHODS > /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:1245: > warning: already initialized constant MUST_DEFINE > /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:1249: > warning: already initialized constant MUST_NOT_DEFINE > /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:1253: > warning: already initialized constant SPECIAL_RETURN > /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:1259: > warning: already initialized constant DELEGATING_METHODS > /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:1569: > warning: already initialized constant DEFAULT_IGNORE_PATTERNS > /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:1575: > warning: already initialized constant DEFAULT_IGNORE_PROCS > /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:1612: > warning: already initialized constant FileList > /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:1638: > warning: already initialized constant EARLY > /usr/ruby1.9.1/lib/ruby/gems/1.9.1/gems/rake-0.8.7/lib/rake.rb:1968: > warning: already initialized constant DEFAULT_RAKEFILES > rake aborted! > stack level too deep > /disk1/home/slugs/235709_37b057a_30d0/mnt/Rakefile:10:in `<top > (required)>' > > On Aug 18, 5:06 pm, chris <[email protected]> wrote: > > > Jobs on our apps all seem to be executed properly by a worker. Try > > running heroku rake jobs:work and see if it blows up w/ a backtrace or > > not. > > > I was running into a pretty serious issue not being able to run any > > rake commands (like "heroku rake routes", for instance) -- ended up > > having to downgrade to ruby 1.8.7 from 1.9.1. > > > On Aug 18, 5:09 pm, jmay <[email protected]> wrote: > > > > Since at least yesterday, Heroku workers are no longer picking up and > > > executing queued jobs. Is anyone else experiencing this? > > > > -Jason > > -- 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.
