similar to: cron scheduling problem

Hi, I was trying to schedule a worker to run during the midnight hour like this: :schedules: :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/

I get this error periodically in backgroundrb.log, but only on my production box (the one running ruby 1.8.5) - my dev box doesn''t get this error. As far as I can tell, everything is working ok, despite the error (I don''t really know how to determine if the jobs are getting threaded successfully, but they are running, that I am sure of). Here''s the dump: no

Hi, I am playing around with backgroundrb 1.0.3. I have the following backgroundrb.yml, --- :backgroundrb: :port: 11006 :ip: 0.0.0.0 :schedules: :task_worker: :run: :trigger_args: */10 * * * * * My task worker is just, class TaskWorker < BackgrounDRb:MetaWorker set_worker_name :task_worker def run logger.info "begin" sleep 60 logger.info

I tried to upgrade my existing application to RC2 last night. Like many, I use this mostly for running scheduled tasks. For the moment, I''ve abandoned the effort, but am looking forward to being able to use this. Feedback below: First, the reason I was looking forward to this upgrade was to use the threaded scheduler. I have an application with long-running tasks. I found that

Hi, I am using the latest checkout from backgroundrb release 1.0.1. I have a worker called status_checker that periodically (every minute) checks the status of certain hosts over the network. It works fine at the beginning but after a while the worker will mysteriously disappear and stop working. I have other workers running but they do not disappear like this worker does. These are

Hi, I have a relatively simple Worker: (I added the line numbers to the email, they are not in the worker) ##################################################################################### class ImagetestWorker < BackgrounDRb::MetaWorker set_worker_name :imagetest_worker def create(args = nil) end def save_image(args) @newbook = Book.new @newbook.comment =

Hi, I''m brand new to BackgrounDRb and trying to figure out the setup. I cloned the git repository today as listed on the BackgrounDRb website. Starting out with a very basic worker, but BackgroundDRb is crashing on a NameError. Any help to resolve this issue would be greatly appreciated! Thank you in advance!! I am also attaching a text file with the output below since it might be

Hello, I am unable to get the backgroundrb server to run. Initially I got: /usr/local/lib/ruby/gems/1.8/gems/activesupport-2.0.1/lib/active_support/dependencies.rb:263:in `load_missing_constant'': uninitialized constant BackgrounDRb::MasterProxy (NameError) from /usr/local/lib/ruby/gems/1.8/gems/activesupport-2.0.1/lib/active_support/dependencies.rb:453:in

Hello, I''ve been using backgroundrb successfully for months now, but suddenly I''m getting the error below when trying to start it up. I did some searching and I see that someone posted about it last month: http://rubyforge.org/pipermail/backgroundrb-devel/2008-April/001685.html Anyone have any idea what could have happened? I made no changes to the code or configs, but I did

Trying to use backgroundrb to process and insert a large list of bulk records, but when I try to use it with the batched_sql_fu plugin installed in vendor/plugins, I get the following error: ---SNIP--- /Users/jdonalds/Sites/3dial_ads/config/../vendor/plugins/ batched_sql_fu/lib/batched_sql_fu/active_record.rb:22:in `alias_insert_sql_to_batched_version!'': undefined method

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

Hi all, I''m new to this list (and pretty new to backgroundrb). I''d like to jump in with a question, I hope you don''t mind. I''m trying to get my site working with backgroundrb to sent mail. It''s pretty basic stuff and I got it working pretty fast on my local machine (os x leopard). Unfortunately, when I try to deploy to my production machine I

Hi, I still have the following error while loading backgroundrb : /opt/ruby-enterprise-1.8.6-20081215/lib/ruby/gems/1.8/gems/ packet-0.1.14/lib/packet/packet_master.rb:116:in `exec'': No such file or directory - packet_worker_runner 14:11:maintenance_worker:64:/home/ antz/declix.com/production/lib/workers (Errno::ENOENT) from

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

Hi, I''ve been using bdrb for a while and just recently found the need to use the ask_status/register_status functionality of my worker. This is the error I get whenever the register_status method is encountered: ...lib/workers/session_worker.rb:10:in `create'': undefined method `register_status'' for #<SessionWorker:0xb6e7d52c> (NoMethodError) from

Hi, New BackgrounDrb user struggling for a couple of days to get things up an going. System: Ruby 1.8.6 Packet 0.1.5 chronic 0.2.3 BackgrounDrb 1.0.3 (downloaded 4/02/08 and 4/03/08) I installed the packet and chronic gems as per instructions. I used git to download BDrb as per instructions and ran the rake setup script. When I run script/backgroundrb from my rails app main directory, I get

Hi everyone, I noticed that script/backgroudrb requires config/environment which causes the backgroundrb server as well as the log worker to ''bloat'' to 35MB each. I am kind of sensitive to memory issues, so I patched the code and essentially moved the require of environment from script/backgroundrb to the meta_worker. Everything seems good and now both backgroundrb server and

Hi all, I''ve got the error below in my backgroundrb_debug.log. I''ve tried to reproduce the error in the development environment, but the only way I can get the same thing is by calling ask_work with a bogus worker name. Calling it with the production code causes no error. Here''s an example of what the code calls: MiddleMan.ask_work(:worker => :agronomy_worker,

> Chris T wrote: > > Not sure this is known behaviour but it seems that if want to set > the > > environment to, for example, test, and you want to use Active > Record you > > have to both explicitly set the RAILS_ENV and the BackgrounDRb > environment. > > I ran into essentially the same problem (needing to run BRB in the > test > environment so

I lost my "connection lost" error.. but now I''ve got a "Mysql::Error: MySQL server has gone away" error.. It comes from: /usr/lib/ruby/gems/1.8/gems/activerecord-1.15.6/lib/active_record/connection_adapters/abstract_adapter.rb:128:in ''log''. I''m not sure if Rails / BackgroundRb uses it .. but i''ve got the mysql (2.7) gem