similar to: backgrounDRb + mongrel_upload_progress

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

i get this: undefined method `object'' for nil:NilClass when i try to get the status of a worker after backgroundrb has been restarted using a job key saved in the DB. how do i get around this? i know the process is nonexistent, but shouldnt it return something more friendly if it doesnt exist? am i forgetting something? Thanks! -Jerrod Jerrod Blavos ph. 919.341.0143 fx.

ok, i was wrong. the failure on deployment using capistrano is 100% using these commands ## Our Handlers desc "Restart BackgrounDrb" task :restart_uploader, :roles => :app do run "#{current_path}/script/backgroundrb stop" run "#{current_path}/script/backgroundrb start" end here is the console post deploy on the remote server ######## [current]$

Im checking out the mongrel_upload_progress plugin and have it working beautifully on my dev box. however, now that i am ready to push this up into production i have run into a few gotchas that i cannot seem to find any documentation or examples for. the lib/upload.rb doesnt seem to want to run in the background. perhaps im doing something wrong? Does anyone have any experience

so i have an after_create method on my track model that kicks off a background process that converts an mp3 to a swf. this is working fine locally on my machine, but upon moving it to my production server, i am getting the following error. I''ve only been using backgroundRB for like 48 hours, so i''m not really sure what this means or where to go. any ideas?

What is the status of the mongrel_upload_progress gem and Rails? I have been playing around with _why and technoweenie''s code but I''m not sure what is current and what is old. It is not working for me. I am running Mongrel 0.3.13.3 (gem) with mongrel_upload_progress 0.1. My upload URI is /agronomics/sample_cycle/upload, and my progress URI is

I''m getting strange data back from my worker whenever I run our rails app with more than one dispatcher under lighttpd. just to give some info on what the app does: user submits data to rails app. rails app hands off data to worker, which goes and does it''s thing, storing results in an array of response objects (the array is an attribute of the worker). the response object

Hi Is there some definitive guide for upload progress plugin ? We have in this mailing list a lot of testimonials, bug reports, bug fixes, but there are still people like me who cannot use it correctly. Here is my config: - mongrel 1.0RC and upload progress plugin 0.2.1 - a 6 mongrels cluster - config/mongrel_upload_progress.conf: uri "/", :handler =>

I started actually using the upload progress handler, and noticed it was leaking memory over time. Looking at the code, I noticed that cancelled uploads weren''t being cleaned up. I bugged Zed about adding a request_abort callback to handlers, but I found a simple way to monkey patch that in: # config/mongrel_upload_progress.conf # yes, this file is being used with -S meaning

Hey. I have a very annoying problem, and was wondering what is wrong. Suppose I have backgroundrb running, and then I have an action in some controller. In the action I define a worker. When leaving the action, suddenly the connection to backgroundrb is lost: DRb URI: druby://localhost:22222 Pid: 3976 Autostart... done druby://localhost:42531 - #<Errno::EBADF: Bad file descriptor -

Hello, I''m trying to install the upload_progress gem and i can''t see the upload progress status. My config is : apache2 with mod_proxy mongrel rails upload.rb : ############## require ''rubygems'' require ''drb'' require ''gem_plugin'' GemPlugin::Manager.instance.load ''mongrel'' => GemPlugin::INCLUDE

Whenever I tried to start mongrel_rails with the upload progress script, it would die with the following error: /usr/local/lib/ruby/1.8/drb/drb.rb:837:in `getaddrinfo'': getaddrinfo: No address associated with nodename (SocketError) from /usr/local/lib/ruby/1.8/drb/drb.rb:837:in `open_server_inaddr_any'' from /usr/local/lib/ruby/1.8/drb/drb.rb:860:in

Hi Folks, Thanks for your patience, new release of BackgrounDRb is available now. You can get it from here: http://svn.devjavu.com/backgroundrb/trunk/ Yes, older version is deprecated and not supported anymore. A brief list of changes since last release is: 1. Now, each worker has logger objects, which can be used to log stuff. 2. A worker can be started or scheduled dynamically. 3. Multiple

Hello, I am trying to make DRb calls to a external server from a backgrounDRb worker, but I''m getting always the next exception when I make the remote call. > ERROR: > drbunix:///tmp/backgroundrb.11175/experimenter_worker_3e899de945f0803a82cd257cfac316d0_0_0.0738904928422051 > - #<Errno::ENOENT: No such file or directory - >

Hi, pardon if this is a duplicate mail, I forgot to click the subscription link the first time around. I''ve been using backgroundrb for a while now (older version) and I''ve had so many headaches because of it that I began looking for a replacement technology. And then I saw the new and shiny backgroundrb website, looking good! Initially I used the version maintained by

Hey there bdrb''ers! I have been so very busy with http://engineyard.com that I have not had time to complete the new release of backgroundrb. But I have done substantial work towards it. It is basically an entirely new beast with a complete rethinking of how it works. I have put up a zip file of the new code base in the hopes that some folks will be able to start playing with

Hello! I have been using backgroundrb for a small project. My worker task is run every minute, checks the processing queue in data-base and execute the business method from Rails if something is to be done. Unfortunately I was hit by the problem of backgroundrb server dying after some runs. The exception is: 20070531-11:06:05 (31816) Starting worker: s_e_work sql_exe (s_e_work_sql_exe) ()

example: :host: 192.168.1.101 :protocol: druby :worker_dir: lib/workers :rails_env: production :pool_size: 15 :load_rails: true :timer_sleep: 60 :acl: :deny: all :allow: localhost 192.168.1.* :order: deny allow I have this config file on 2 app servers running rails. The 2 servers are running behind a load balancer. I''m starting the backgroundrb server on the one server with the

Can one use mongrel_upload_progress in combination with attachment_fu (db_file)? I wan''t to store uploaded files directly in a mysql-database - not in the filesystem. Is there a way to use mongrel_upload_progress to do this, or do I have to store files in the filesystem and copy them to the database? Thanx

Hello all, I''m having some trouble getting backgroundrb set up so that all the processing happens on a single machine. I have 3 load balanced machines. Right now, all three run our web application and create MiddleMan workers to generate a large PDF report. However, because of the processing power needed to generate the PDFs, I want to change our setup so that two servers run