similar to: Dynamic start/stop test environment backgroundrb during test execution?

I found this stack trace in my logs. My worker name is MiscWorker, and Qualifier is a Rails model. uninitialized constant MiscWorker::Qualifier: /Users/bryan/ Workspace/sandbox/scraper-trunk/config/../vendor/rails/activerecord/ lib/../../activesupport/lib/active_support/dependencies.rb:476:in `const_missing'' /Users/bryan/Workspace/sandbox/scraper-trunk/lib/workers/

It seems that regardless of what environment I specify in my backgroundrb.yml file, it always uses development mode unless I pass "-e production" to the "script/backgroundrb start" command. >From looking at bdrb_config.rb, it looks like immediately after loading the config file it assigns whatever was passed on the command line (which defaults to development if nothing is

Hello all, I''m using BackgroundRb 0.2.0 (standalone) and in the do_work method of my worker, I''m working with objects from my Rails application. So in my config/backgroundrb.yml file, I added this line: :load_rails: true I think my worker isn''t doing what I want him to do. So I opened the console and read these error lines: # ruby script/backgroundrb console

I started emailing monit mailing list because I started getting this problem where I couldn''t start backgroundrb with monit anymore, thinking it was a monit problem. However, I back tracked a bit since I had added code to my project, and monit was able to start backgroundrb again. I seem to have zeroed in on the problem. I''m not sure where the problem lies - maybe monit or

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, it probably is a noob question but I''m confused by this error message: active_support/dependencies.rb:478:in `const_missing'': uninitialized constant Invoice::ApplicationController Situation: I have an InvoicesController with a create method that in turn calls upon a MiddleMan.worker(:billing_worker), which in turn finds an Invoice and calls upon @invoice.print_invoice

I have two scheduled tasks in my rails app: background_schedules.yml mail_sender_1: :class: :mail_sender_worker :job_key: :job_key_mail_sender_1 :worker_method: :do_work :trigger_args: :start: <%= Time.now + 5.seconds %> :end: <%= 1.years.from_now %> :repeat_interval: <%= 60.minutes %> cleanup_1: :class: :cleanup_worker :job_key: :job_key_cleanup_1

I''m trying to use BackgrounDRb to do image processing on large uploaded zip files of images, but $script/plugin install svn://rubyforge.org//var/svn/backgroundrb gives me this: /usr/lib/ruby/1.8/open-uri.rb:88:in `initialize'': No such file or directory - svn://rubyforge.org//var/svn/backgroundrb (Errno::ENOENT) I can install the old version with $script/plugin install

I just installed backgroundrb on our server. When tryin to start via script/backgroundrb i get a no method error. ./script/backgroundrb start /home/tom/ralf_dev/vendor/plugins/backgroundrb/server/lib/backgroundrb_server.rb:34:in `format_message'': undefined method `strftime'' for "2006-12-04T15:53: 23.419225 ":String (NoMethodError) from

i ran rake backgroundrb:setup and modified the default config/backgroundrb.yml file as: --- port: "22223" timer_sleep: 60 load_rails: true environment: production host: localhost database_yml: config/database.yml acl: deny: all allow: localhost 127.0.0.1 order: deny,allow and my database.yml production: adapter: mysql database: chip2_production username: xxxxx password:

Hi, I have my rails sites tricked out with capistrano, and backgroundrb, so I can easily use the ant tasks, but I would like to be able to start and stop backgroundrb from within rails. I have a few reasons for this: 1. Using fastcgi, backgroundrb would start under the apache user and the same mod_security context as apache, instead of my developer account which has many more privileges. 2.

Hi Guys,Looks like I have to do this in backgroundrb.yml :backgroundrb: :ip: 0.0.0.0 :production: :backgroundrb: :port: 11008 # use port 11008 :environment: production That is, have an entry for "environment: production" under :production:, This seems to have fixed the issue. Regards Sarat On 5/29/08, Sarat Kongara <saratkongara at gmail.com> wrote: > >

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

Howdy, I''m trying to use monit with backgroundrb, but it seems that backgroundrb.ppid isn''t holding the id of the backgroundrb task. jodi at soup/var/www/the-soup/current $ cat log/backgroundrb.ppid 23182 jodi at soup/var/www/the-soup/current $ ps -efl 1 S deploy 23184 1 0 75 0 - 27056 stext 11:27 ? 00:00:04 backgroundrb 1 S deploy 23186 23184 0 76

Hi, I am using eclipse and instant rails. I am trying to start the backgroundrb server by the folowing script ruby script/backgroundrb start On doing a stack trace, it shows me an error in backgroundrb_tasks.rb on the line if File.exists?(scripts_src) `#{scripts_src}/start -d` Can anyone tell me what could be the possible reason? I tried removing -d, but no use. Thanks, Harini

Hi, If I start backgroundrb with rails_env = production, and then run my test suite, is it true that my background tasks will run against the production database? Can I prevent this from happening when I mistakenly end up with a combination like this? Thanks Joerg -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because

Seems this mail did not make it to the list for some reason. It contains my solution for the problem with login_engine without having to load the whole Rails environment. Begin forwarded message: > From: G?nter Ladwig <gladwig at gmx.de> > Date: 22. Juni 2006 23:51:18 MESZ > To: backgroundrb-devel at rubyforge.org > Subject: Re: [Backgroundrb-devel] Models and Backgroundrb

Hi Folks, I am glad to announce a 1.0.1 release of BackgrounDRb library. It has numerous fixes and some nice feature updates, so please upgrade. Code: http://svn.devjavu.com/backgroundrb/tags/release-1.0.1/ Updates and Fixes: * Fixed issue with Mysql Lost connections * Message debugging can be disabled now with ''debug_log'' option in configuration file( :debug_log: false)

I just had an interesting issue on a production system that has been running nicely for about a year. There were approximately 10,000 backgroundrb temp files in the /tmp directory. It looks like backgroundrb wasn''t cleaning them up. I noticed it with the following error: DRb::DRbConnError: drbunix:///tmp/backgroundrb.20015/ backgroundrb_logger_0_0.101544829808665 -

It''s that time again friends. skaar has been at it again and has greatly improved the stability of the new system. And Ara Howard has helped a ton by working with us on the slave library to iron out the wrinkles./ The results is a lot nicer backgroundrb for everyone. I have to say another huge thanks to skaar. He has singlehandedly wrote almost all of this new version and many