similar to: Start script not working when run via Rake

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

Hi, I''ve been having some issues integrating bdrb on a cruisecontrolrb server It''s related to the way we stop the bdrb server. The thing is, right now when we stop the process we are killing the parent of the group of the process. This is ok if you''re running script/backgroundrb stop directly from the console, but if I''m running this from another process,

I override some Rails'' configuration options in my project, like: config.database_configuration_file = "#{RAILS_ROOT}/local/config/ database.yml" But they aren''t picked up in BackgroundRB because Rails ActiveRecord is just initialized directly in MasterWorker#load_rails_env: db_config_file = YAML.load(ERB.new(IO.read("#{RAILS_HOME}/

Hi there I have recently upgraded to v1.0.1 and I''ve noticed an issue which I don''t believe was present in the 0.2 release. In my worker class I am logging errors as follows: logger.error "the error message" However, this now causes an exception to be thrown in the new version: undefined method `error'' for

I''m using backgroundrb in a rails project, with packet and chronic unpacked in the vendor folder, to make backgroundrb I''ve added the following line to scribts/backgroundrb $LOAD_PATH << File.join(RAILS_HOME, "vendor") Do you believe it''s a good idea? I don''t like depend on the installed gems ciao ciao paolo -------------- next part

Hi - I have a fresh install of OSX, Rails, Ruby, Ferret, AAF etc ... Everything is working fine, I can start mongrel, I can start backgroundrb, but Ferret Drb ... doesn''t want to work. RAILS_ENV=development script/ferret_start Gives me: env: script/runner: Permission denied Is there a way I can debug this to figure out what is going on - or is there another way to start Ferret Drb?

Hi. I am using BackgrounDRb to process thumbnails and upload to S3 - things are hunky-dory in development (thumbs are generated, these are uploaded to S3, the metadata is saved to trhe DB, and I get a nice status page updated by periodic calls via ask_status), but when I tried to deploy to our staging server and stop/start BackgrounDRb via Capistrano, things blew up - well, not exactly,

When I call ask_status on a worker that has not been started I get and exception of type BackgrounDRb::BdrbConnError, which is fine. I can deal with that, but I also find that the backgroundrb process dies as well. The scenario is simple: Call ask_status on a worker that is not auto loaded. I used a job_key, in case that makes a difference. -------------- next part -------------- An

I''m trying to run a single worker that could perform a periodic task for a given user. >From a controller, I imagine something like: def start_job MiddleMan.ask_work(:worker => :foo_worker, :worker_method => :perform_task, :data => { :user_id = current_user.id }) end def check_job @status = MiddleMan.ask_status(:worker => :foo_worker)[current_user.id] end

Hello ~ I am using the Capistrano recipe outlined in this post to restart my backgroundrb server: http://rubyforge.org/pipermail/backgroundrb-devel/2007-February/000718.html My Version: ~~~~~~~~~~~~ task :before_restart, :roles => :app do restart_backgroundrb end task :start_backgroundrb, :roles => :app do sudo "nohup

Short update: It seems that the workers go into some state in which they do not have a correct Rails environment (or db connection). When they enter this state it goes wrong all the time :( Joost Hietbrink (YelloYello) wrote: > Hi all, > > We''re experiencing some problems with Backgroundrb. > > Why is "# master_reactor_instance.result_hash = {}" commented in

I''ve created a couple of tasks in my deploy.rb file for starting and stopping backgroundrb on the remote server. The stop task runs fine and kills the process. And the start task *seems* to run successfully, but backgroundrb is never started on the remote host. Has anyone had success with this? Here are my deploy tasks: desc ''Start backgroundrb server (default

I have noticed that occasionally (about 50% of the time) when i deploy (using capistrano) my app to a production server, i have to ssh into the box and manually stop and start backgroundrb to get it to load my workers. this is my basic setup i have 2 workers: lib/workers/mp3_worker.rb => takes a hash of params to downsample an mp3 lib/workers/flv_worker.rb => takes a has of

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,

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, I get this error when starting bgdrb using "rake backgroundrb:start" (on a Mac using bgdrb 0.2.0): /Users/gl/Projects/xxxxx/xxxxx/vendor/plugins/backgroundrb/server/lib/ backgroundrb_server.rb:33:in `format_message'': undefined method `strftime'' for "2006-11-22T12:34:18.524572 ":String (NoMethodError) from /usr/lib/ruby/1.8/logger.rb:320:in

Hi there, We''ve been using previous version of bdrb (drb based one) for a while and it was running relatively OK. We recently attempted to upgrade to the new version to keep up / use supported version but we ended up reverting to the older version. Here are the things that moved us to revert : 1) With the workers we never manage to pass this error: '''' You have a nil

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''ve been having a terrible time with the backgroundrb scheduler. The issues I''m having is that the scheduled actions aren''t ran at all and if they do, the process stays around forever. I''m using the backgroundrb as a nightly cron to run some accounting operations. questions: 1. How can I have the process destroyed after the worker completes? 2. Any idea on

Hi , If you are following commits, I have pushed following changes: 1. Now, you can specify :environment option in config file to load production environment and stuff. 2. Exeptions that were exposed to the user has been changed to BdrbConnError if rails is not able to connect to bdrb server. 3. loading mechanism has been changed, so remove backgroundrb script from your backgroundrb directory