search for: cron_trigger

...s: :collector: :process_something: :trigger_args: 30 * 0 * * 2,3,4,5,6 When I try to start backgroundrb, the "collector" worker failed to start up and I find this in backgroundrb_server.log: /home/mengkuan/apps/testrailsapp/current/vendor/plugins/backgroundrb/ server/cron_trigger.rb:160:in `local'': argument out o f range (ArgumentError) from /home/mengkuan/apps/testrailsapp/current/vendor/plugins/ backgroundrb/server/cron_trigger.rb:160:in `fire_time _after'' from /home/mengkuan/apps/testrailsapp/current/vendor/plugins/ backgroundrb/serv...

...ground.yaml file: :schedules: :debugger_worker: :ping: :trigger_args: 0 35 11 * * * * Backgroundrb starts up without error. If I make the following change: :trigger_args: 0 30 11 * * * * Backgroundrb complains: brb-test/vendor/plugins/backgroundrb/server/cron_trigger.rb:161:in `local'': argument out of range (ArgumentError) from brb-test/vendor/plugins/backgroundrb/server/cron_trigger.rb:161:in `fire_time_after'' from brb-test/vendor/plugins/backgroundrb/server/meta_worker.rb:266:in `new_load_schedule'' from br...

...orker_name :task_worker def run logger.info "begin" sleep 60 logger.info "end" end end After seeing a few begin''s and end''s in the log, I get the following exception: /Users/pkmiec/src/propertyadmin/trunk/vendor/plugins/backgroundrb/server/lib/cron_trigger.rb:119:in `parse'': wrong number of arguments (2 for 1) (ArgumentError) from /Users/pkmiec/src/propertyadmin/trunk/vendor/plugins/backgroundrb/server/lib/cron_trigger.rb:119:in `fire_after_time'' from /Users/pkmiec/src/propertyadmin/trunk/vendor/plugins/backgroundrb/server/lib/cro...

A quick fix for anyone running into this problem: load_schedule was crashing cron_trigger.rb#160, and I found that for triggers like "0 20 5 * * * *" it was putting in 32 for the date (even though its Mon Mar 31 04:16:21 BST 2008). Something to do with switching to day light savings I think, which concludes after 2am. I patched it by adding day = 31 if day == 32 on the line...

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 after that. The way I fixed it was adding a call to self.delete at the end of every do_wo...

Hey guys, I was playing with the cron trigger, and I noticed that wday is not honored. Looking at the code confirms this. Has anyone else seen this? Thanks Adam -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20071217/44d3a8a6/attachment.html

I''m using a plugin which adds a method to ActiveRecord::Base http://similetimelinerailshelper.googlecode.com/svn/trunk/simile_timeline/ This adds an "acts_as" type declaration to the Models, via the file in vendor/plugins/simile_timeline/lib/simile_timeline.rb Rails is working with these declarations, and they are being used successfully in ''regular

...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. attr_accessor :progress, :description def do_work(args) # This method is called in it''s own new thread when you...