In resque’s sources (Job class) there’s such method, guess it’s what you need 🙂 # Removes a job from a queue. Expects a string queue name, a # string class name, and, optionally, args. # # Returns the number of jobs destroyed. # # If no args are provided, it will remove all jobs of … Read more
It’s probably trying to open the default browser and failing to do so. Try using: $ resque-web -L To avoid starting a browser.
Have you verified redis-server is running? Please don’t ask me to dissect the following command, but in a terminal you can type: ps aux | grep redis You should then see something like: redis 13319 0.0 0.0 2884 1056 ? Ss 10:54 0:00 /usr/bin/redis-server /etc/redis/redis.conf If it’s not running, I recommend issuing the following command: … Read more
I’m a little late to the party, but thought I’d post what worked for me. Essentially, I have god setup to monitor redis and resque. If they aren’t running anymore, god starts them back up. Then, I have a rake task that gets run after a capistrano deploy that quits my resque workers. Once the … Read more
Playing off of the above answers, if you need to clear all of your queues, you could use the following: Resque.queues.each{|q| Resque.redis.del “queue:#{q}” }
For my projects I will feel very comfortbale with collectiveidea/delayed_job in rails2 and 3. I don’t know beanstalkd, but i will try it soon :-). I have followed the suggestions in the resque documentation. I will report it. Resque vs DelayedJob How does Resque compare to DelayedJob, and why would you choose one over the … Read more
yes it’s quite easy, given you’re using the Resque gem: require ‘resque’ Resque.info will return a hash e.g/ => { :pending => 54338, :processed => 12772, :queues => 2, :workers => 0, :working => 0, :failed => 8761, :servers => [ [0] “redis://192.168.1.10:6379/0” ], :environment => “development” } So to get the failed job count, … Read more
Resque: Pros: does not require thread safety (works with pretty much any gem out there); has no interpreter preference (you can use any ruby); Resque currently supports MRI 2.3.0 or later loads of plugins. Cons runs a process per worker (uses more memory); does not retry jobs (out of the box, anyway). Sidekiq: Pros runs … Read more
None of these solutions worked for me, I would still see this in redis-web: 0 out of 10 Workers Working Finally, this worked for me to clear all the workers: Resque.workers.each {|w| w.unregister_worker}