search for: backgroundrb_schedul

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 # begin # MiddleMan.schedule_worker(:class => :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 lib/workers I have the following class: cl...

...drb 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 :job_key: :city_updater :worker_method: :do_work :worker_method_args: scheduled workers require some args, so here you go... :trigger_args: :start: <%= Time.now + 5.seconds %> :repeat_interval: <%= 1.minutes %> I...

...: class EmailProcessorWorker < BackgrounDRb::Worker::RailsBase def do_work(args) queue = EmailQueue.new queue.process_queue end end EmailProcessorWorker.register I do all the work in a Rails Model, since I can unit test it outside of backgroundrb. Does anyone have a backgroundrb_schedules.yml file I could use as an example, and should this run something like every 15 minutes, etc., or should it start once, and loop endlessly inside do_work? Any thoughts or experience? Thanks for your input ? Jim Scott -- No virus found in this outgoing message. Checked by AVG Free E...

...ass. Sometimes it just blocks infinitely when I try to access it. I don''t know whether it is in AR itself or in the SQL driver. It just stops doing anything, logging nothing, no exceptions are raised. I don''t know if it matters that I call the worker''s methods via backgroundrb_schedule.yml. Has anyone experienced a problem alike? Or can you give me a clue what could be wrong? PS: I''m not passing ANY AR objects via DRb ----------------------------- Siebert Michael info at siebert-wd.de --- ACHTUNG potenzieller Amokl?ufer: spiele Killerspiele (Scarface, GTA, UT)...

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 ne...

...here is a line in the backgroundrb codebase: sleep 0.1 # TODO this is dangerous; could skip over some jobs Could this explain why my scheduler stops triggering? It only seems to work for about 12 - 24 hours before schedules are being skipped... Once I changed the times to using cron trigger in backgroundrb_schedules.yml and set the times to every 37th and 59th minute of the hour, instead of the previous repeat_interval of 60.minutes it seemed to improve but it still stops being triggered within a day and doesn''t seem to start again unless I stop and start background rb... Sometimes this is both my...

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

when working with the scheduler i found that using :trigger_args: 0 * * * * * * in config/backgroundrb_schedules.yml the worker gets only called once. :trigger_args: "0 * * * * * *" works as expected. Maybe this should be changed in the README ? regards tom -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/backgroundrb-devel/attac...

...er 20070313-15:45:21 (5595) MbReceiver mr started. 20070313-15:45:21 (5595) Sender s started 20070313-15:45:22 (5595) MbSender ms1 started 20070313-15:45:22 (5595) MbSender ms2 started 20070313-15:45:22 (5595) Receiver r started 20070313-15:45:30 (5595) MbReceiver mr started. The relevant chunk of backgroundrb_schedules.yml looks like this: mb_receiver: :class: :mb_receiver :job_key: :mr :worker_method: :do_work :args: :sleep_time: 5 :trigger_args: 0,10,20,30,40,50 * * * * * * The other workers have identical trigger_args, but don''t exhibit this behavior. The do_work metho...

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

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

...takes three arguments: > > | :start => time, :end => time, :interval => seconds > > If the end argument is omitted, the event will trigger at the interval as > long as the server is running. > Shouldn''t it be :repeat_interval? Everything below it in both the backgroundrb_schedules.yml and the MiddleMan section seems to indicate this. If so, how can I go about changing it? download the trunk and submit a patch? I wouldn''t mind helping out with documentation, especially parts I found confusing when I first started using backgroundrb. Thanks. Wil -- http://www....

...undrb 0.2.1 support autostart? I''ve tried to set up autostart by adding something like the following in backgroundrb.yml: autostart: 1: class: bar_worker args: '''' However, that does not seem to work. I also tried the scheduling mechanism like this in backgroundrb_schedules.yml: bar: :class: :bar_worker :job_key: :bar1 :trigger_args: 0 * * * * * * This works, but after around 30 to 40 mins, the scheduler will fail and I get errors like this in the logs: 20070404-11:37:00 (23325) failed to find slave socket - (RuntimeError) 20070404-11:37:00 (23325) /...

...automatically start a worker and have it repeat every xx minutes. This was easy in the previous version because you would simply do : ''repeat.every 20.minutes'' or similar in the worker. I''m sure it''s easy, but I''m not sure how to place something in backgroundrb_schedules.yml to get it to autostart. Any easy tips? Thanks, Brian -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20070215/cc3438be/attachment.html

...automatically start a worker and have it repeat every xx minutes. This was easy in the previous version because you would simply do : ''repeat.every 20.minutes'' or similar in the worker. I''m sure it''s easy, but I''m not sure how to place something in backgroundrb_schedules.yml to get it to autostart. Any easy tips? Thanks, Brian -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20070215/9ae5f2fc/attachment.html

...entry, which is never deleted... maybe this is a problem - new sockets are created, but never deleted and system runs out of resources? Currently my configuration is (backgroundrb.yml): :port: 2000 :rails_env: development :host: localhost :protocol: druby :pool_size: 5 :worker_dir: lib/workers (backgroundrb_schedules.yml) sql_scheduler: :class: :s_e_work :job_key: :sql_exe :trigger_args: 5 * * * * * * Worker code is: class SEWork < BackgrounDRb::Worker::RailsBase def do_work(args) # This method is called in it''s own new thread begin script = SqlScript.find(:first, :conditio...

...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: ------ ebay_runner: :class: :ebay_auction_worker :job_key: :ebay_auction_runner :trigger_type: :cron_trigger :trigger_args: 0 * * * * * * ------ My ebay_auction_worker.rb file: ------ class EbayAuctionWorker < BackgrounDRb::Rails # Set this worker to run every minute. at...

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