similar to: ''stack level too deep'' error

Hi, I''m brand new to BackgrounDRb and trying to figure out the setup. I cloned the git repository today as listed on the BackgrounDRb website. Starting out with a very basic worker, but BackgroundDRb is crashing on a NameError. Any help to resolve this issue would be greatly appreciated! Thank you in advance!! I am also attaching a text file with the output below since it might be

Hello, I''ve been using backgroundrb successfully for months now, but suddenly I''m getting the error below when trying to start it up. I did some searching and I see that someone posted about it last month: http://rubyforge.org/pipermail/backgroundrb-devel/2008-April/001685.html Anyone have any idea what could have happened? I made no changes to the code or configs, but I did

Hi all, I''m new to this list (and pretty new to backgroundrb). I''d like to jump in with a question, I hope you don''t mind. I''m trying to get my site working with backgroundrb to sent mail. It''s pretty basic stuff and I got it working pretty fast on my local machine (os x leopard). Unfortunately, when I try to deploy to my production machine I

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

Sorry if this comes through twice. I already sent this once, before joining the mailing list. I''m attempting to use Backgroundrb to handle asynchronous pdf creation, but in doing so, I''ve run into a very strange problem. Below is a method that''s called from the controller which creates a new worker, then grabs the worker and calls the ''build_pdf''

Hi, I''m a long time backgroundrb user, still stuck using the very ancient original version from Ezra (not even Ezra''s 2.0 version, I''m using the one that didn''t really have a version number). The 2.0 version did very little but crash for me. Anyway I finally got some time set aside to try out this new version you all have been developing.

My BackgrounDRb server intermittently bails out with the following exception in the middle of a long running task running on a Worker sub classed from BackgrounDRb::MetaWorker (the point at which it raises this exception is different each time it runs) /opt/local/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_core.rb:145:in `schedule_write'': You have a nil object when you

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 use BDRb to process RSS feeds for users on my site (http://feedflix.com). I have a batch job that queries the DB for records that haven''t been updated in the last so many hours and kicks off a background job for each of them. If N records are returned by the DB, N background jobs gets queued and get done serially. As long as N is 255 or under, everything works like a charm.

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

Hello, I am unable to get the backgroundrb server to run. Initially I got: /usr/local/lib/ruby/gems/1.8/gems/activesupport-2.0.1/lib/active_support/dependencies.rb:263:in `load_missing_constant'': uninitialized constant BackgrounDRb::MasterProxy (NameError) from /usr/local/lib/ruby/gems/1.8/gems/activesupport-2.0.1/lib/active_support/dependencies.rb:453:in

Below is the content of my backgroundrb_server_11007.log This seems to happen in a non-repeatable way - so every 2 days or sometimes after 4-5 days, my b/g process dies with this error. Is this something anyone else has seen - any fixes? Thanks, Raghu ===============true /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_core.rb:145:in `schedule_write'': You have a nil object when

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

I tried to upgrade my existing application to RC2 last night. Like many, I use this mostly for running scheduled tasks. For the moment, I''ve abandoned the effort, but am looking forward to being able to use this. Feedback below: First, the reason I was looking forward to this upgrade was to use the threaded scheduler. I have an application with long-running tasks. I found that

Hi, New BackgrounDrb user struggling for a couple of days to get things up an going. System: Ruby 1.8.6 Packet 0.1.5 chronic 0.2.3 BackgrounDrb 1.0.3 (downloaded 4/02/08 and 4/03/08) I installed the packet and chronic gems as per instructions. I used git to download BDrb as per instructions and ran the rake setup script. When I run script/backgroundrb from my rails app main directory, I get

Hey all, Been reading through all the old posts (and the docs) to familiarize myself but I still feel a bit lost. I''m on trunk and am having a bit of a hard time knowing where to start with the particular I''m trying to solve. So far, I''ve downloaded backgroundrb, done the basic rails setup, created my worker and started it using `script/backgroundrb start`.

Hi, A pre-release version of backgroundrb is available now from svn. Download it from here: http://svn.devjavu.com/backgroundrb/branches/version099/ Since this release marks significant migration from existing practices, i intend to keep trunk untouched for a while. There are no install scripts, but you should copy "backgroundrb" file from script directory of plugin to script

Hi, all. Just wondering if anyone has tried using the Paperclip file upload plugin with Backgroundrb. My current implementation uses attachment_fu - I save the file initially to the file system without generating thumbs, then a bdrb process picks up that file, generates thumbs, and saves to S3. This works fine and dandy, the only hitch is I want to save image metadata in the same table

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

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