similar to: Time based configuration in God

I am facing problem in resque process. I have following implementation: /config/resque_schedule.yml add_jobs_to_queue: cron: "15 * * * *" class: FooJob description: "Find results from class Bar and put on queue" /app/jobs/foo_job.rb class FooJob @queue = :normal def self.perform Bar.add_jobs end end app/models/bar.rb class Bar def self.add_jobs

Hi, I have implemented resque scheduler in my application by looking at example here https://github.com/bvandenbos/resque-scheduler. I have configured resque_schedule.yml file, and in that I can pass arguments to the resque job. My requirement is to pass more than one arguments to the queueing resque job. If we consider the example given, clear_leaderboards_contributors: cron: "30 6 * *

I run Resque with x ''general'' queues. With ''general'' I mean a queue that may run every type of Worker. Or in the Rake command: COUNT=x QUEUE=* rake resque:work When a worker runs a job of a specific class, it may not run another job of the same class simultaniously. This job has to wait until the previous job has finished before it may start. BTW The reason

Hi, guys! Background: I''ve resque workers in my application. These workers do several jobs that associated with DB. In development environment, I''ve no need to provide some additional configuration for db, they are use development database. But then I switching to production env, I set ActiveRecord::Base.establish_connection with my production DB parameters. Problem: When

Hi, I''ve just got a quick question. How come ActiveRecord::ConnectionAdapters::ConnectionHandler#verify_active_connections! is marked with :nodoc: ? I understand that this is used internally (depending upon an application''s configuration?) on every request (?) to clear out old, stale database connections. All this to prevent the old, classic "MySQL server has gone

I was having a problem with cap deploys where you get: Couldn''t find any pid file in ... matching ''dispatch.[0-9]*.pid'' based on the suggestion of another post I implemented the following in deploy.rb which does successful terminate all the Ruby process but this includes God. desc "restart override" task :restart, :roles => :app do run "killall -9

Hi, I''m trying to use god to monitor my mongrels. When they are running everything looks OK but when a mongrel process dies and god tries to restart it I get the following error: command exited with non-zero code = 1 The weird thing is that if I try use the exact same command as god is using but on the command line then the mongrel starts back up. I''ve seen this error

I was able to run god earlier in the day, but now I get this error: # god load config/mms-service.god The server is not available (or you do not have permissions to access it) Anybody know what this error means? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this

Hello, Although it is off topic, but I wanted to share my idea with the group of shorewall There were greek,Egyptian,.... gods they have gods for everything I think it is our turn to make a god for the internet it is a virtual thing, but I think it is a nice idea and he/she should be the protector and so on as the internet is like the Sky /water, and fire If no one likes the idea , do not

Hey All, I just wanted to get other peoples take on problems when running merb in production? Just as Rails used to do, the mongrels tend to get heavy/unresponsive over time so need a good kicking by a watcher daemon like god or monit. However, I have had serious problems getting God to restart the process, as the "merb -k <port>" command doesnt appear to work reliably

This means we no longer waste an extra file descriptor per worker process in the master. Now there''s no need to set a higher file descriptor limit for systems running >= 1024 workers. --- I just pushed this out to git://bogomips.org/unicorn.git and it''ll be in Unicorn 4.x. The subset of raindrops used by Unicorn should work on all machines with mmap(2) +

When I run rake db:migrate or rake -T I get these lines at the end: Finished in 0.000276 seconds. 0 tests, 0 assertions, 0 failures, 0 errors My Gemfile is: source ''http://rubygems.org'' gem ''rack'' gem ''rails'', ''3.0.9'' gem "acl9", ''0.12.0'' gem "fastercsv"#, :version =>

I have two workers (ie two files in my RAILS_ROOT/lib/workers directory) on my Rails app. When I run a top on my box, I see *three* processes called packer_worker_r. Shouldn''t I just be having two? What is the third process for? Here is an extract of the output from my top command. The PIDs are 7084, 7085 and 7083. ============================================ PID USER PR NI VIRT

Howdy, I''m trying to debug a situation where a Rails app running on Mongrel +Apache stops listening to requests. Restarting Mongrel and Apache brings it back to life. First off, here''s some info on versions, etc...: Red Hat Enterprise Linux ES release 3 (Taroon Update 8) ruby 1.8.5 (2006-12-04 patchlevel 2) [x86_64-linux] Mongrel 1.0.1 Rails 1.2.1 fastthread (0.6.2)

Hi folks, I''ve got some BackgroundRB workers to handle a long running task (triggered by a user) that work very well on my staging server, and I just wanted to check to see if anyone had any advice before I put it into production. When I start the worker (which performs an import), I write a record to my database for each import. The record gets updated by the worker to

Hey there bdrb''ers! I have been so very busy with http://engineyard.com that I have not had time to complete the new release of backgroundrb. But I have done substantial work towards it. It is basically an entirely new beast with a complete rethinking of how it works. I have put up a zip file of the new code base in the hopes that some folks will be able to start playing with

> > > Dear All, I just posted an interview with Karim Chine of http://www.biocep.net/ who has successfully built a latform for on demand data mining enabled by the cloud through R. Here is an except BIOCEP is built on top of R and Scilab and anything that you can do within those environments is accessible through BIOCEP. Here is what you have uniquely with this new R/Scilab-based

While i run rake db:migrate i got below error ,let me know any one . Please it is urgent to me. D:\raj\tweasier>rake db:migrate --trace (in D:/raj/tweasier) DEPRECATION WARNING: Rake tasks in vendor/plugins/open_flash_chart_2/tasks, vend or/plugins/resque/tasks, and vendor/plugins/resque/tasks are deprecated. Use lib /tasks instead. (called from

Hey Greg- Yes I am sorry, the new architecture uses fork and named pipes and a bunch of unix stuff to do its magick. Now you may be able to port it to qwork on windows, but I don''t think it is possible :( I''m really sorry about this but I need this thing to be as robust and solid as it can be and in the end windows isn''t compatible. Now you may be able to

We have a fairly expensive task that we''d rather not schedule too many instances of in parallel. Couldn''t get pool_size to limit the amount of workers, and I figure that''s hardly optimal anyway, so would like to have the work queued up for a single named worker instead, running as soon as possible. Using MiddleMan.schedule_worker() with :job_key does start off a