similar to: Setting environment

> 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 have been strugging with getting backgroundrb to stay in the correct environment using multiple configuration files and the -c switch when starting backgroundrb. If I start brb like this: ./script/backgroundrb run RAILS_ENV=development -- -c ../config/development_background.yml where development_background.yml specifies "development" for rails_env and environment, the first worker

Hi All, It might be lack of sleep, but I am struggling to accurately limit our pool size. It seems like I can specify it on the server with the -s command line option and also on the client via the YAML pool_size. Is that right? Which one wins? Our problem is that we are getting about 40 threads on each backgroundrb box and it''s flooring our db and each bgrb box. We want around 8.

I''ve found a conflict in the way the configuration file is handled, in particular effecting the setting of the ENV[''RAILS_ENV''] value. When I attempted to run a worker in production, it would run fine the first time - the second time would fail because it was trying to access the development database. I had created a ''backgroundrb_prodcution.yml'' file

I''m running a fresh checkout of release 1.0.1 ... It''s now 11:32 am local time on January 31. I''ve configured a single worker for a test. If I use the following schedule in my background.yaml file: :schedules: :debugger_worker: :ping: :trigger_args: 0 35 11 * * * * Backgroundrb starts up without error. If I make the following

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

Hello, Just upgraded to the the latest backgroundRb.I am getting an error when i run the task "rake test:plugin". Any idea why I am getting this? Here is the error message: /usr/bin/ruby1.8 -Ilib:test "/usr/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake/rake_test_loader.rb" "vendor/plugins/backgroundrb/test/master_worker_test.rb"

Hey all, I''m having some issues moving a project that incorporates Backgroundrb onto a staging server... For some reason (surely of my own doing), my RailsBase workers are insisting on using trying to access my development DB instead of my "production" DB. When I try to load a model object from within a worker, I get the following: 20061120-21:54:28 (26296)

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,

Greetings all, Unit tests are passing, but I''m having mucho problems getting brb to run without exceptions for more than 6 hours. I''m seeing a mixture of the following 2 exceptions: 20070605-11:26:56 (21497) failed to find slave socket - (RuntimeError) 20070605-11:26:56 (21497) /usr/local/lib/ruby/gems/1.8/gems/ slave-1.2.1/lib/slave.rb:435:in `initialize''

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

Hi Guys,You can start backgroundRb in different environments using -e option. ./script/backgroundrb -e production I like to run a rake task from my worker - something like rake RAILS_ENV=proper_environment thinking_sphinx:start I am not sure how to figure out the environment with which the backgroundRb is started from inside a worker task. Any help is appreciated. Thanks for your time. Regards

Hi there, after recently deploying my app, I have noticed that the search results are not being displayed... When I look in my app, I also notice that the apps content (search criterea) is not being indexed, so I dont have an index folder being created. I read on a google post that it may be that the ferret.yml server isn''t started (or perhaps the content of this file are not right) I

Hi everyone, I am going crazy over here! :) I just want to be able to use --clean with my mongrel_rails cluster::start command. I''ve upgraded to mongrel_cluster 1.0.1.1 and mongrel_rails 1.0.1. my config file is in /etc/mongrel_rails/config.yml and contains: --- log_file: log/mongrel.log port: 8000 pid_file: /var/run/mongrel_cluster/mongrel.pid servers: 2 address: 127.0.0.1 environment:

I''m having no luck trying to daemonize mongrel running a camping server. When mongrel daemonizes, I get: /usr/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel.rb:723:in `accept'': closed stream (IOError) from /usr/lib/ruby/gems/1.8/gems/mongrel-1.0.1/lib/mongrel/configurator.rb:293:in `join'' ... (This was after I disabled the unhandled exception catchall in the

I need a way to kill the ferret_server drb process programatically, so I can start/stop it as part of the capistrano deployment process. This should be as simple as adding some sort of stop method to ActsAsFerret::Remote::Server. I was just messing around and was able to do it by modifying method_missing to look for the :stop method and then calling DRb.thread.exit -- this is not good enough for

I''m deploying new rails applications. Everything works well except when it comes to the db migration: * executing "cd /var/rails/benefits_test/releases/20101129190121 && /opt/ruby-enterprise-1.8.7-2010.02/bin/rake RAILS_ENV=production db:util:migrate" servers: ["ps-test-app1"] [ps-test-app1] executing command ** [out :: ps-test-app1] (in

I''m just getting started wtih backgroundrb, and unfortunately hit a snag right away... I''m running the latest releases of rails, backgroundrb, slave and daemons. I created a simple worker class, using the generator, which currently does nothing but print the arguments that are passed to do_work. I''m running backgroundrb using ''./script/backgroundrb

Hi there I''m using the latest release (r300) and ''script/backgroundrb start'' works perfectly when executed on the server, but when put inside a Rake task, it doesn''t launch the worker processes. The Rake task is as follows: task :start_backgroundrb do run "cd #{current_path} && ./script/backgroundrb start" end When I run this task, the

Hello, I''m trying to send emails from a backgroundrb worker and the email doesn''t send. I get no log messages in the sendmail log or the system log, nothing in the backgroundrb logs at all, nothing in the production log. Below is my code for each component worker: class QuizReviewerWorker < BackgrounDRb::MetaWorker set_worker_name :quiz_review_sender def create(args =