similar to: disable trigger logging in production

Greetings all; I''ve just moved my app into production and BackgrounDRb is writing to development.log. The backgroundrb.yml file specifies production, as does environment.rb. A little background (no pun intended ;-0 ) I''m using the ''old'' version of backgroundrb for session management. In the app, whenever a visitor changes pages I record the time in a db

I have a big report to produce from a Rails app that takes several minutes to put together. I hoped backgroundrb would be able to pull together all the ActiveRecord stuff in the background then throw it back to Rails for rendering. It seems, however, that I can''t pass an array of ActiveRecord objects from the worker back to Rails. Do I have that right? Another possibility was to do

Hi list, I''m having some issues getting backgroundrb to play nice with more than one mongrel. When I run my app on a single mongrel instance it works fine. I have two different problems show up in my backgrounrb_server.log. The top of the backtrace is shown here: 20070130-12:03:03 (92473) failed to find slave socket - (RuntimeError) 20070130-12:03:03 (92473)

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''m trying to make a worker that will render a large page to a file, very similar to what rails'' builtin cacheing does except with the rendering done outside of rails. The only advice I''ve found is to use ActionController::Integration::Session.new but this doesn''t seem to allow setting session variables the way the functional tests do. Is there a way to

Hi, I''m having a problem where connections started through BackgrounDRb::MiddleManDRbObject.init are not stopped, resulting in an ever growing established connections between my Mongrels and remote backgroundrbs I added DRb.stop_service to my code executed after requests that init MiddleManDRbObjects but that does not help. Any ideas? Thanks, Robert Bjarnason

Hi all, BackgrounDrb was exactly what I needed for a project I''m working on at work. Everyone''s really impressed, and now it''s time to put the system into production. My question is, how do I avoid having to manually run the startup and shutdown scripts (or the rake tasks) for backgroundrb? I tried putting a system "rake backgroundrb:start" in my

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

In response to my Rails Weenie post today[1], someone mentioned that I try BackgrounDRb to help take the strain off my application. 1: http://rails.techno-weenie.net/question/2006/7/13/nested-loops- best-way-to-send-messages-to-blog-subscribers I''ve just tried to install and use BackgrounDRb with my app, but I''m afraid that I''m not too versed in running processes

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

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

All the active record....read and writes....from backgroundrb gets logged into development.log files..created by rails...is there any way to avoid this? Its driving me nuts....because once bulk read/write from backgroundrb starts i am not able to trace my normal rails logs. -------------- next part -------------- An HTML attachment was scrubbed... URL:

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 have a job that I am starting from a Rails controller in production mode using MiddleMan: MiddleMan.new_worker(:class => :import_ccg_category_worker, :args => { :category_id => @category.id, :remote_category_id => params[:remote_category_id], :description => "Importing CCG products for #{@ category.name}" }) Both of the category ID variables are just basic integers. I

Hey again, After playing with BackgrounDRb a bit longer, I have two more issues I''d like to bring up with it. 1. Logging... it seems like even when the environment is set to production in both Mongrel and the backgroundrb.yml file, all ActiveRecord SQL statements are written to the development log. If you''re doing a lot of ActiveRecord stuff in your workers, then the

Sorry for perhaps asking a Newbie-Question, but couldn''t find any answer elsewhere (and even not in the archieves...). Trying to import files in my rails app using backgroundrb and trying to examine the backgroundrb.log file. But it isn''t updated. The pid-file is updated to the correct value every time I start drb. I''m working on an windows-machine (XP Prof). Tried to

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''m trying to silence the information that backgroundrb is putting in to my test runs. I''m seeing several hundred lines of this during the test runs (both unit and functional): {:type=>:all_worker_info} {:type=>:do_work, :worker=>:xmlrpc_xmpp_worker, :worker_method=>:register_user,

Thanks so much for backgroundrb, it''s nice to be able to keep the moving parts to a minimum. I''m noting some odd behavior on ruby 1.8.5, rails 1.2.5, backroundrb trunk on a macbook. When scheduling a task everything works perfectly, but triggers are not calling the methods, only blocking the background drb instance. Logs show no errors. Even more interesting is the fact that