diaspora/diaspora — Issue #2169: resque crashes
Author: amckinstry
Created: 2011-10-12 08:26:28+00:00
State: open

Updated as of 11 October, (I update my production pod diaspora.sceal.ie approx . weekly), it appears that resque has been crashing since early September.

Running resque independent of ./script/server gives:

(See full trace by running task with --trace)
root@ailm:/srv/diaspora# QUEUE=* bundle exec rake resque:work --trace
** Invoke resque:work (first_time)
** Invoke resque:setup (first_time)
** Execute resque:setup
** Execute resque:work
rake aborted!
uninitialized constant Job
/var/lib/gems/1.8/gems/rake-0.9.2/lib/rake/ext/module.rb:36:in `const_missing'
/var/lib/gems/1.8/gems/resque-1.10.0/lib/resque/helpers.rb:58:in `const_get'
/var/lib/gems/1.8/gems/resque-1.10.0/lib/resque/helpers.rb:58:in `constantize'
/var/lib/gems/1.8/gems/resque-1.10.0/lib/resque/helpers.rb:57:in `each'
/var/lib/gems/1.8/gems/resque-1.10.0/lib/resque/helpers.rb:57:in `constantize'
/var/lib/gems/1.8/gems/resque-1.10.0/lib/resque/job.rb:174:in `payload_class'
/var/lib/gems/1.8/gems/resque-timeout-1.0.0/lib/resque/plugins/timeout.rb:37
/var/lib/gems/1.8/gems/resque-1.10.0/lib/resque/worker.rb:336:in `call'
/var/lib/gems/1.8/gems/resque-1.10.0/lib/resque/worker.rb:336:in `run_hook'
/var/lib/gems/1.8/gems/resque-1.10.0/lib/resque/worker.rb:115:in `work'
/var/lib/gems/1.8/gems/resque-1.10.0/lib/resque/worker.rb:110:in `loop'
/var/lib/gems/1.8/gems/resque-1.10.0/lib/resque/worker.rb:110:in `work'
/var/lib/gems/1.8/gems/resque-1.10.0/lib/resque/tasks.rb:24
/var/lib/gems/1.8/gems/rake-0.9.2/lib/rake/task.rb:205:in `call'
/var/lib/gems/1.8/gems/rake-0.9.2/lib/rake/task.rb:205:in `execute'
/var/lib/gems/1.8/gems/rake-0.9.2/lib/rake/task.rb:200:in `each'
/var/lib/gems/1.8/gems/rake-0.9.2/lib/rake/task.rb:200:in `execute'
/var/lib/gems/1.8/gems/rake-0.9.2/lib/rake/task.rb:158:in `invoke_with_call_chain'
/usr/lib/ruby/1.8/monitor.rb:242:in `synchronize'
/var/lib/gems/1.8/gems/rake-0.9.2/lib/rake/task.rb:151:in `invoke_with_call_chain'
/var/lib/gems/1.8/gems/rake-0.9.2/lib/rake/task.rb:144:in `invoke'
/var/lib/gems/1.8/gems/rake-0.9.2/lib/rake/application.rb:112:in `invoke_task'
/var/lib/gems/1.8/gems/rake-0.9.2/lib/rake/application.rb:90:in `top_level'
/var/lib/gems/1.8/gems/rake-0.9.2/lib/rake/application.rb:90:in `each'
/var/lib/gems/1.8/gems/rake-0.9.2/lib/rake/application.rb:90:in `top_level'
/var/lib/gems/1.8/gems/rake-0.9.2/lib/rake/application.rb:129:in `standard_exception_handling'
/var/lib/gems/1.8/gems/rake-0.9.2/lib/rake/application.rb:84:in `top_level'
/var/lib/gems/1.8/gems/rake-0.9.2/lib/rake/application.rb:62:in `run'
/var/lib/gems/1.8/gems/rake-0.9.2/lib/rake/application.rb:129:in `standard_exception_handling'
/var/lib/gems/1.8/gems/rake-0.9.2/lib/rake/application.rb:59:in `run'
/var/lib/gems/1.8/gems/rake-0.9.2/bin/rake:32
/var/lib/gems/1.8/bin/rake:19:in `load'
/var/lib/gems/1.8/bin/rake:19
Tasks: TOP => resque:work

with the result that while while the pod works for local users, no content from other pods is retrieved; only stuff from before September.

When I change to single process mode, content from remote users slowly starts to arrive.