I've been having a terrible time with the backgroundrb scheduler. The issues I'm having is that the scheduled actions aren't ran at all and if they do, the process stays around forever. I'm using the backgroundrb as a nightly cron to run some accounting operations. questions: 1. How can I have the process destroyed after the worker completes? 2. Any idea on what would keep the prcesses from being started. The backgroundrb.log is empty. I'll post the backgroundrb_server.log 3. Is backgroundrb even the right choice for nightly rails crons? Thanks for any help, and of course for backgroundrb! Charlie This is the backgroundrb_server.log for last night. It called and ran this worker but none of the rest (about 7 others). Again, nothing was written to the backgroundrb.log. all the workers run fine when manually called, and even run fine some of the time through cron. 20070604-06:00:00 (29111) Schedule triggered: #<struct #<Class:0xb7a2a5ac> job=#<Proc:0xb7982dac@/var/www/companyapp/releases/20070531073057/vendor/plugins/backgroundrb/server/lib/backgroundrb/middleman.rb:355>, trigger=#<BackgrounDRb::CronTrigger:0xb7366cc0 @sec=[0], @wday=0..6, @min=[0], @month=1..12, @hour=[6], @year=nil, @day=1..31, @cron_expr="0 0 6 * * * *">, earliest=Mon Jun 04 06:00:00 EDT 2007, last=Mon Jun 04 06:00:00 EDT 2007> 20070604-10:00:03 (29111) Starting worker: collect_worker collect (collect_worker_collect) () -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20070604/ab998b...
CHarlie- If all you need is nightly type jobs then bdrb is not the right choice,. I would just use cron and script/runner. Cheers- -Ezra On Jun 4, 2007, at 12:57 PM, Charlie Bowman wrote: > I've been having a terrible time with the backgroundrb scheduler. > The issues I'm having is that the scheduled actions aren't ran at > all and if they do, the process stays around forever. I'm using > the backgroundrb as a nightly cron to run some accounting operations. > > questions: > 1. How can I have the process destroyed after the worker completes? > 2. Any idea on what would keep the prcesses from being started. > The backgroundrb.log is empty. I'll post the backgroundrb_server.log > 3. Is backgroundrb even the right choice for nightly rails crons? > > Thanks for any help, and of course for backgroundrb! > > Charlie > > This is the backgroundrb_server.log for last night. It called and > ran this worker but none of the rest (about 7 others). Again, > nothing was written to the backgroundrb.log. all the workers run > fine when manually called, and even run fine some of the time > through cron. > > 20070604-06:00:00 (29111) Schedule triggered: #<struct #<Class: > 0xb7a2a5ac> job=#<Proc:0xb7982dac@/var/www/companyapp/releases/ > 20070531073057/vendor/plugins/backgroundrb/server/lib/backgroundrb/ > middleman.rb:355>, trigger=#<BackgrounDRb::CronTrigger:0xb7366cc0 > @sec=[0], @wday=0..6, @min=[0], @month=1..12, @hour=[6], @year=nil, > @day=1..31, @cron_expr="0 0 6 * * * *">, earliest=Mon Jun 04 > 06:00:00 EDT 2007, last=Mon Jun 04 06:00:00 EDT 2007> > 20070604-10:00:03 (29111) Starting worker: collect_worker collect > (collect_worker_collect) () > _______________________________________________ > Backgroundrb-devel mailing list > Backgroundrb-devel at rubyforge.org > http://rubyforge.org/mailman/listinfo/backgroundrb-devel -- Ezra Zygmuntowicz -- Lead Rails Evangelist -- ez at engineyard.com -- Engine Yard, Serious Rails Hosting -- (866) 518-YARD (9273)
Thanks for the quick reply! I'll definitely take your advice on this. On 6/4/07, Ezra Zygmuntowicz <ezmobius at gmail.com> wrote: > > CHarlie- > > If all you need is nightly type jobs then bdrb is not the right > choice,. I would just use cron and script/runner. > > Cheers- > -Ezra > > On Jun 4, 2007, at 12:57 PM, Charlie Bowman wrote: > > > I've been having a terrible time with the backgroundrb scheduler. > > The issues I'm having is that the scheduled actions aren't ran at > > all and if they do, the process stays around forever. I'm using > > the backgroundrb as a nightly cron to run some accounting operations. > > > > questions: > > 1. How can I have the process destroyed after the worker completes? > > 2. Any idea on what would keep the prcesses from being started. > > The backgroundrb.log is empty. I'll post the backgroundrb_server.log > > 3. Is backgroundrb even the right choice for nightly rails crons? > > > > Thanks for any help, and of course for backgroundrb! > > > > Charlie > > > > This is the backgroundrb_server.log for last night. It called and > > ran this worker but none of the rest (about 7 others). Again, > > nothing was written to the backgroundrb.log. all the workers run > > fine when manually called, and even run fine some of the time > > through cron. > > > > 20070604-06:00:00 (29111) Schedule triggered: #<struct #<Class: > > 0xb7a2a5ac> job=#<Proc:0xb7982dac@/var/www/companyapp/releases/ > > 20070531073057/vendor/plugins/backgroundrb/server/lib/backgroundrb/ > > middleman.rb:355>, trigger=#<BackgrounDRb::CronTrigger:0xb7366cc0 > > @sec=[0], @wday=0..6, @min=[0], @month=1..12, @hour=[6], @year=nil, > > @day=1..31, @cron_expr="0 0 6 * * * *">, earliest=Mon Jun 04 > > 06:00:00 EDT 2007, last=Mon Jun 04 06:00:00 EDT 2007> > > 20070604-10:00:03 (29111) Starting worker: collect_worker collect > > (collect_worker_collect) () > > _______________________________________________ > > Backgroundrb-devel mailing list > > Backgroundrb-devel at rubyforge.org > > http://rubyforge.org/mailman/listinfo/backgroundrb-devel > > -- Ezra Zygmuntowicz > -- Lead Rails Evangelist > -- ez at engineyard.com > -- Engine Yard, Serious Rails Hosting > -- (866) 518-YARD (9273) > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20070604/e8b7bb...