similar to: Error while creating one worker from another

Hello, We are working on a centralized report generating project, which calls for data processing on different servers and then centralizes the reports into a single project. What we would like to do is have a Monitor BackgrounDRb worker call another BackgrounDRb worker to process data on a different server, and then have our Monitor Worker collect the data and then store it according to our

Hi, I have an application that receives XML files, and then hands each one off to a backgroundrb worker to parse and store the info. Everything was working, until I needed to support a larger character set. So I added the following to the top of my XML files: <?xml version="1.0" encoding="ISO-8859-1"?> Adding this worked fine when I tested it without using

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 all, We''re currently running version .1.x in our environment. We would like to move to .2.x to take advantage of some of the improvements made running in a multi-process environment. We deploy to a linux environment but develop locally in Windows. I''m aware that a number of people have reported the ability to run .2.x of backgroundrb inside cygwin, and for the most part,

(Sorry my last email had the wrong subject) Hi, I''ve just installed background rb 0.2.1. When I try start a worker in my application controller I receive the following error: wrong number of arguments (2 for 1) - (ArgumentError) /home/chris/projects/call_manager/trunk/call_manager_app/vendor/plugins/backgroundrb/server/lib/backgroundrb/middleman.rb:211:in `initialize''

Hey, I have scheduled script that is not working very well. It will only run once or twice before I have to restart the server to get it running again. If I try to the worker manually after it has stopped exceuting the schedule I get this in the server log: 20070522-07:33:36 (5030) Connection reset by peer - (DRb::DRbConnError) 20070522-07:33:36 (5030) /usr/local/lib/ruby/1.8/drb/drb.rb:566:in

Hi all I''m experiencing something strange with a :job_key, it took me a very long time to find out a worker wasn''t doing it''s job because of the name of my job_key. The first one I tried was :make_kohier, and with that name (and lot''s of other ones) I can''t get the worker to work. I do get my key in return, but the job doesn''t start

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)

Hello - Can anyone explain why I get the stack trace in background_server.log when I try to start my first worker? I don''t get this on subsequent workers, only the first one. I should note, the method I am using to start backgroundrb is documented in the archives, and is likely the root of this problem. Suggestions about how to "fix" or avoid this issue are appreciated.

Hi All, I''m using Backgroundrb as a general purpose long-running-task back-end (upload processing, email sending, etc), and it''s been a great solution. However I''ve recently run into some some intermittent connection issues that have me baffled. I''m running on apache2/fcgid and the problem occurs in both devlopment and production mode. The problem seems to

I''m at a loss to explain a very strange error I''m getting. This seems to happen on our production system where we have a backgroundrb server sharing a host with a Rails app running on Mongrel. The first one or two, occasionally three, calls to a worker (direct MiddleMan calls from Rails, not scheduled) succeed, but afterwards, the server fails to initialize new workers.

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

Hello everyone, I''m stuck with this very obscure error whenever I try to create a new worker. My worker is a subclass of BackgrounDRb::Worker::RailsBase, and if you follow the stack trace below, you can tell that the error occurs while trying to load Rails. There is no problem starting up the server, by the way. Does anyone have any idea what might be causing this? I didn''t have

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

Hello all, After upgrading to Rails 1.2.2, I''m getting a strange error when one of my workers is invoked. The worker is responsible for monitoring a folder (using directory_watcher) and emailing a specific user when a file is dropped there, but it''s bombing immediately upon instantiation (or maybe when trying to instantiate ActionMailer?) with the error "Text is not a

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) ()

Hi everyone, I''ve a class that try to spawn two workers, every 5 seconds. The code is something like: while true do MiddleMan.new_worker(:class => :researches_worker,:job_key => :researches) MiddleMan.new_worker(:class => :products_worker,:job_key => :products) sleep(5) end I''m using ":job_key", so if a worker hasn''t already ended its work

Hey, I''ve got a problem where my worker is not being properly executed.... it used to work in an earlier version of brb, but i realized my vendor/plugins was out of whack, upgraded to the newer schedule- oriented release (0.2.1). I can start brb, and run the new_worker middleman, but ntohing happens. When putting brb in ''run'' mode, i see this: undefined method

Ok two things that bug me 1) http://backgroundrb.devjavu.com/projects/backgroundrb/ticket/48 i thought i''ll just post ticket link - but well - it''s strange 2) when i switch base class from RailsBase to Base i can''t access MiddleMan - i get error NameError: uninitialized constant MiddleMan from (drbunix:///tmp/backgroundrbunix_localhost_2999)

I''m struggling to keep backgroundrb v2 running for more than 24 hours. It appears to be running fine for a while, then tries to fire off a worker (exactly the same worker it''s been running for the past few hours), and it suddenly dies. I haven''t found any pattern for the cause of this. In backgroundrb_server.log, the final entry is this : 20070206-10:41:45