search for: bgrb

I get the error when trying to start backgroundRb 1.0.3 running on Rails 1.2.6 ./backgroundrb start ./backgroundrb:11:in `require'': no such file to load -- /var/www/test/vendor/plugins/backgroundrb/config/boot.rb (LoadError) from ./backgroundrb:11 is 1.0.3 able to run on rails 1.26 ? this was my thought as to why it wasn''t working unfortunately i cannot upgrade rails

...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. Is there a way to put a hard ceiling on the server side thread pool? Here is our setup: 5 app boxes, app01 - app05, with 8 mongrel instances each (this is where the 40 comes from, I think) Each app box points to a load balancer in front of two backgroundrb boxes, crawler01...

I recently switched over to v1.0, and things are rolling along pretty well. However, one thing that has always been a little confusing to me is knowing when to use thread_pool. Since most of my bgrb workers are called from my web app to process rather than being scheduled, I''m using the thread_pool for every call. Unfortunately, that means that I have to split up workers by how many threads I can have. It would be great if one worker could partition a single thread pool among the me...

Anyone have a a good monit config section for bgrb? I''m thinking something like this: check process backgroundrb with pidfile /var/www/apps/foo/current/log/backgroundrb.pid start program = "/var/www/apps/foo/current/script/backgroundrb start" stop program = "/var/www/apps/foo/current/script/backgroundrb stop"...

...it invariably returns nil. The log file remains empty. I''ve only tried this from the console so far. If I can''t even do this successfully, I''m in no mood to try to start to write code, I''ve followed the example instructions to the letter, and confirmed that the BGRB server is running, as well as my Mongrel. I''m running on Leopard. Rails 2.2.2 ruby 1.8.6 (2008-03-03 patchlevel 114) [universal-darwin9.0] I''d really appreciate it if someone could give me some feedback on this fast. Otherwise I''ll have to drop BackgroundRb and go with...

...rb_server log. I''m guessing this has something to do with why I''m supposed to be using thread_pool instead of Thread). When I get those read errors, the backgroundrb_debug.log shows "Client disconected" (sic). I don''t know if this is normal for rails talking to bgrb or if it''s an error. I don''t see it on every line, but it seems to coincide with the "some read error" messages in the script. Am I doing something wrong? Anyone have a working example using thread_pool? Also, I''ve never used Mutex before, so if my usage is off...

...I see very little chatter about these problems on the list or when searching the web, but I seriously can install a completely new 10.4 system, fresh ruby/rails/everything compiled from scratch, make a totally new Rails program, and plug in a worker straight from the examples that come with bgrb-2, and so help me when you run that worker the second time, it always seg- faults! Intel or PPC, server or client version, no difference! Just how does anyone with OS X get this running? Really, any advice at all... if someone with Mac OS X 10.4 has gotten version 2 to work, and you coul...

...le.read(path)) logger.debug " ...done" logger.debug " Getting file size for #{path}..." results[:file_stats][path][:size] = File.size(path) logger.debug results[:file_stats][path][:size] So as soon as I attempt the checksum assignment above, bgrb disappears. I see the ''generating checksum'' message, but it never says ''...done''. Jason Sydes has intimated to me in another thread that I can''t do what I''m attempting above. But a hash is a hash is a hash, right? Or is it? James ps. I initia...