similar to: scheduled only called once

I am sure..again I am missing something, but I am trying to start a worker, when backgroundrb starts and it doesn''t seem to work. Here is my config/backgroundrb_schedules.yml file: feed_worker: class: feed_worker job_key: feed_worker_key worker_method: do_work trigger_args: repeat_interval: 20.minutes I even tried this from Rails controller: # def start_feed_worker #

I''m running the latest backgroundrb mainly for scheduled tasks support. As per the documentation I created the backgroundrb_schedules.yml with the following: simple_label: :class: :document_sorter_worker :worker_method: :do_work :job: :bleh :trigger_args: :start: <%= Time.now + 5.seconds %> :end: <%= Time.now + 10.minutes :repeat_interval: 1.minute Under

Hi there, Backgroundrb is working pretty well for me but I have a job that launches two of the same job, apparently a minute(?) apart from each other. Should this be happening if I have repeat interval enabled with a job_key? It seems like it should wait until the job is finished before launching a new instance. --Backgroundrb_schedules.yml-- city_updater: :class: :city_updater_worker

Hi gang, Thanks to other help I''ve gotten on this list, I''ve got backgroundrb up and running using postgres alongside my rails app. I''ve designed the system to have several eternally-running workers that periodically poll the database to see if there''s any work for them to do, and set things up in the config file to make them restart quickly if any of them

I had a worker scheduled to run every minute with backgroundrb_schedules.yml: ebay_runner: :class: :ebay_auction_worker :job_key: :ebay_auction_runner :trigger_type: :cron_trigger :trigger_args: 0 * * * * * * This worker posts an auction to eBay from a queue of auctions every minute. I was having a problem where the worker would run ok the first time, but never any subsequent minutes

I''ve got some workers that I want to have running all the time. Right now I''m just launching them manually, by requesting a special page in my rails app that includes lines like: MiddleMan.new_worker(:class=> :receiver, :job_key=>:r, :args=>{:sleep_time=>10}) This strikes me as a really weak way to fire up my workers. I basically want to automate things so

Hi , How do i schedule a job that can send emails at intervals of time using backgroundrb and rails For testing When i hit the controller i''m able send the emails. but that is not i intend to do ..... I want to use backgroundrb and rails in which i''ll schedule a job for every 5 minutes/ 1 minute or so..... to send an email But when i write

Hi all, I just read Ezra''s article on BackgroundRb and decided to use it one of my projects. I installed the plugin into my rails project using script/plugin and then ran rake backgroundrb:setup to copy the yml scripts. Now my backgroundrb.yml looks like ======= --- port: "22222" timer_sleep: 60 load_rails: true environment: development host: localhost database_yml:

Quick question: If I want to schedule different worker methods defined in the same worker to trigger at different times, is this possible? Would the following scheduler yaml work? :schedules: :foo_worker: :worker_method: method1 :trigger_args: 0 */10 * * * * * :job_key: some_key_1 :foo_worker: :worker_method: method2 :trigger_args: 0 */15 * * * * * :job_key:

Hi Ezra/skaar, Wow man, the exercise was worth it. The connection closed problem with socket as i mentioned in my earlier mails...completely disappeared, and now i can connect only once to the socket and keep reading..till end of its days. Literally impossible with older release of backgroundrb. This could also potentially solve the issues people were having with ActiveRecord. As i said

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

Hi I have previously used railscron for server-side manipulation of the database but had a heap of trouble working with it. BackgrounDRB was suggested to me by a friend. I upload some files via acts_as_attachment and these go lie in a dir structure that i desire. What I want from the background process is to periodically (not user initiated) do some file-structure manipulation i.e. I want to

I have been facing this damn ugly issue since quite sometime. So this worker reads RSS feed from Yahoo news and stores it in a DB. The worker is scheduled to run at every 40 minutes and my background_schedules.yml looks like this: feed_worker: :class: :feed_worker :job_key: :feed_worker_key :worker_method: :do_work :trigger_args: :start: <%= Time.now + 5 %>

Hi I thought this should suspend the task by 1 minute, but it starts immediately: MiddleMan.ask_work( :worker => :bar_worker, :worker_method => :test_method, :trigger_args => { :start => (Time.now + 1.minute)}) Is the start argument not allowed in the new backgroundrb (mine is at rev HEAD (=314))? What can I do about this? I really need to suspend starting the task as I want

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, i''m trying desperately to schedule some worker methods within rails 2.0.2. The problem is, both methods don''t even get called by BackgrounDRb. my background.yml: > --- > :backgroundrb: > :port: 11006 > :ip: 0.0.0.0 > --- > :schedules: > :server_worker: > :update: > :trigger_args: 1 *

Hi! I''m using the latest&greatest backgroundrb with rails 2.0.2 on ubuntu dapper. I''ve made an app that lets you run a query on several servers at once, which are selected at runtime. Therefore, for each server that is selected, I spawn a new worker and assign its work. After everything is completed, the workers are deleted. I often get this error:

I have installed backgroundrb. I can start it. I have read everything I can get my hands on, and have read the list for a few months. I have written a worker, and am ready to start. This worker reads a queue, and processes it (sends queued emails). Sends 10, sleeps for a minute, sends 10 until done - very straightforward. My question is, what would be the best way to run this? I have

I have a scheduled worker that runs every minute, checking for new eBay auctions to post. If it finds an auction, then it posts it. If there are no auctions in the database that are queued up, it simply does nothing. I got the worker to finally run as a scheduled worker, every minute. However, after about 30-45 scheduled runs, it simply stops running. My backgroundrb_schedules.yml file: ------

Hi, pardon if this is a duplicate mail, I forgot to click the subscription link the first time around. I''ve been using backgroundrb for a while now (older version) and I''ve had so many headaches because of it that I began looking for a replacement technology. And then I saw the new and shiny backgroundrb website, looking good! Initially I used the version maintained by

Hi, I have backgroundrb running to decouple the execution of massive business logic from an ActionWebservice request. The service is designed to take some configuration parameters and fire a lot of background workers to do the requested work. Due to performance reasons I want to limit the number of workers to a maximum number of 30. But when I start a configuration that requires for example