similar to: How to: Reduce nbr of processes (Ruby, Apache, BackgroundRB)

Hi all, I''ve been having trouble for a long time with backgroundrb processes that suddenly vanish without a trace. What happens is that at some point I discover that all the backgroundrb processes are suddenly gone. Nothing special is seen in any of the log files. This has happened intermittently for a long time, and I was hoping that upgrading to 1.0.4 would somehow help me out, but

Hi Folks, I have been working to fix BackgrounDRb memory usage as such. Ruby1.8 GC isn''t fork friendly and it seems to use a lot of memory because when you fork, it sets a bit in all the objects in global scope which causes OS to all pages in child process. A classic solution is to use fork and exec, rather than just fork. Its working and pretty stable, but you loose ability to pass

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

What might be causing this error? I see it once in 2-3 days and it goes away when I restart backgroundrb. Quoted below is my backgroundrb_server_11007.log file. Can I do anything to avoid this? Thanks, Raghu ================================================================================== /usr/lib/ruby/1.8/monitor.rb:224:in `mon_exit'': stack level too deep (SystemStackError) from

Hi All, I''ve been developing a rails app using the Bitnami RailsStack ( http://bitnami.org/stack/rubystack) and it has always worked as advertised. That is until I have tried to get BackgrounDRB up and running. I have followed the steps given on the plugin''s project page, each seems to work. I the plugin install works, I can generate workers etc, but when I start the backgrounDRB

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

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! I''ve just a created a really simple rails scheduled worker for backgroundrb to start playing with : class SessionCleanerWorker < BackgrounDRb::Worker::RailsBase def do_work(args) logger.info "SessionCleaner> started" CGI::Session::ActiveRecordStore::Session.destroy_all( [''updated_at <?'', 120.minutes.ago] )

Hi all My problem is that: With reference to http://backgroundrb.rubyforge.org/ 1---I have download backgroundrb from http://opensvn.csie.org/ezra/rails/backgroundrb to my vendor/plugin in my application folder. 2-- after that I used the command to run :-rake backgroundrb:setup -- trace From my application

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"

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.

I''m working on an application that does extensive database searching. These searches can take a long time, so we have been working on moving the searches to a backgroundrb worker task so we can provide a sexy AJAX progress bar, and populate the search results as they are available. All of this seems to work fine until the size of the search results gets sufficiently large, when we start

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:

BackgrounDRbers: We pass a data batch to a background task for processing. When it finishes, our GUI updates correctly (using the results hash). But the data records don''t appear in the Rails connection to the database. Our stack is the HEAD BackgrounDRb, Rails 1.1.6, MySQL, and Apache/mongrel. As soon as I whack the background process with script/backgroundrb stop, the data records

Hi! As you might remember I''m having a problem of backgroundrb stopping calling my workers after some period of time. I tried adding logging to backgroundrb source code but it didn''t help. So, after digging through internet I''ve found several gdb tools and here''s what I''ve discovered: After attaching to a backgroundrb ruby process it turns out that it

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

Hey Folks- I have just pushed a new release of BackgrounDRb to rubyforge. It has some nice new features to allow for usage of your ActiveRecord Models within your worker classes. I also added a config file for setting hosts and ports and if you want to load rails or not. Please have a look and let me know if anyone runs into any issues. If you already have an older version installed then you

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)

Hello - I would like to figure out a way to have backgroundrb start/stop with the same UID that dispatch.fcgi uses, at the same point in time that apache is started/stopped. I see a technique that seems plausable in this archive message: http://rubyforge.org/pipermail/backgroundrb-devel/2007-February/000723.html which addresses the starting aspect, in a lazy fashion. That seems fine,

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 -