similar to: -c switch in the startup command

I''m running a fresh checkout of release 1.0.1 ... It''s now 11:32 am local time on January 31. I''ve configured a single worker for a test. If I use the following schedule in my background.yaml file: :schedules: :debugger_worker: :ping: :trigger_args: 0 35 11 * * * * Backgroundrb starts up without error. If I make the following

Not sure this is known behaviour but it seems that if want to set the environment to, for example, test, and you want to use Active Record you have to both explicitly set the RAILS_ENV and the BackgrounDRb environment. So, if you have a config file backgroundrb_test.yml (as well as the default) and set the environment to test in that, this is what *seems* to happen: $

Hello, I''m trying to send emails from a backgroundrb worker and the email doesn''t send. I get no log messages in the sendmail log or the system log, nothing in the backgroundrb logs at all, nothing in the production log. Below is my code for each component worker: class QuizReviewerWorker < BackgrounDRb::MetaWorker set_worker_name :quiz_review_sender def create(args =

> Chris T wrote: > > Not sure this is known behaviour but it seems that if want to set > the > > environment to, for example, test, and you want to use Active > Record you > > have to both explicitly set the RAILS_ENV and the BackgrounDRb > environment. > > I ran into essentially the same problem (needing to run BRB in the > test > environment so

Hi gang, Thanks to other help I''ve gotten on this list, I''ve got backgroundrb up and running using postgres alongside my rails app. I''ve designed the system to have several eternally-running workers that periodically poll the database to see if there''s any work for them to do, and set things up in the config file to make them restart quickly if any of them

Greetings all, Unit tests are passing, but I''m having mucho problems getting brb to run without exceptions for more than 6 hours. I''m seeing a mixture of the following 2 exceptions: 20070605-11:26:56 (21497) failed to find slave socket - (RuntimeError) 20070605-11:26:56 (21497) /usr/local/lib/ruby/gems/1.8/gems/ slave-1.2.1/lib/slave.rb:435:in `initialize''

Folks, I am strugging with Asterisk 1.4 Vs 1.6 differences over AMI Originate? Here is the pastebin... http://pastebin.ca/1805594 Not sure why the local channel won't send to context while the remote channel does. Worked fine in 1.4 but 1.6.1 has issues. Any help? Ritesh -------------- next part -------------- An HTML attachment was scrubbed... URL:

strugging with things here... tried tracking the info on the Wiki (which apparently is now in need of a maintainer)... http://wiki.centos.org/HowTos/JavaOnCentOS My primary interest is using Xalan/Saxon/xslt/xsl-fo docbook generation. I was thinking that all I really need is jre but downloaded both jre and jdk just in case. can anyone tell me what I'm doing wrong? (after removing both jdk

I''m having some trouble with using brb for polling for work. Basically, what I want to do is update the state of a record and have brb notice and start a process. I do not want to call ask_work for each process because there may be several places where the object''s state is changed, and I only want to process once. Plus, I can schedule things better this way. My first thought

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

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

Hi everyone. Backgroundrb is doing some really sweet stuff for my project. Thanks! I am trying to integrate backgroundrb with cruisecontrol.rb. I started off by creating a simple Rakefile::::: desc ''task for starting up backgroundrb'' task :cruise do template = <<-EOF :backgroundrb: :ip: 0.0.0.0 :port: 11006 :development: :backgroundrb: :log: foreground

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

I have a scheduled worker that runs every minute, checking for new eBay auctions to post. If it finds an auction, then it posts it. If there are no auctions in the database that are queued up, it simply does nothing. I got the worker to finally run as a scheduled worker, every minute. However, after about 30-45 scheduled runs, it simply stops running. My backgroundrb_schedules.yml file: ------

hi, i am using drb and it is working fine on my local pc on windows.. and after uploading the code to the server it was working for sometime but now it gives me error every time i invoke the process.. error--- uninitialized constant EmailWorker::Notifier - (NameError) /usr/lib64/ruby/gems/1.8/gems/activesupport-1.4.2/lib/active_support/ dependencies.rb:477:in `const_missing''

Hi all, I''ve got the error below in my backgroundrb_debug.log. I''ve tried to reproduce the error in the development environment, but the only way I can get the same thing is by calling ask_work with a bogus worker name. Calling it with the production code causes no error. Here''s an example of what the code calls: MiddleMan.ask_work(:worker => :agronomy_worker,

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)

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

I am new to this list and relatively new to the backgroundrb plugin,. So first i will say hello to everybody here, especially to Ezra Zygmuntowicz! I played a little bit with a dummy worker and so far everything worked well. But now i want to do real work in a worker but now i get that error[1]. It looks like that the constants configured in environment* configs are not available to the worker

I''m using backgroundrb for session management and deletion of visitor-entered information when a session is abandoned. The visitor can either click a button to end their session and remove their data, or backgroundrb will do it for them after 5 minutes of inactivity. Everything''s working fine, I think. If the visitor explicitly logs out, then when the worker checks for their