search for: log_worker

What does the method query_all_workers() do? There is no documentation on what this method returns (1.0.1 version). Orion -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20080118/9f9b8112/attachment.html

...when it happened, I had the fortune of having a "top" log running in a terminal window, so I''m able to present some more data. top was displaying all threads, so most of the processes show up twice or more. I have 5 background workers running, each apparently has 2 threads, plus log_worker with 1 thread and script/backgroundrb with 2 threads. My architecture is set up so that only "master" is started automatically when backgroundrb starts up, and it in turn starts the rest. I''m pasting in data for all the backgroundrb processes, sorry for the terrible formatting b...

Hi there, We''ve been using previous version of bdrb (drb based one) for a while and it was running relatively OK. We recently attempted to upgrade to the new version to keep up / use supported version but we ended up reverting to the older version. Here are the things that moved us to revert : 1) With the workers we never manage to pass this error: '''' You have a nil

...:worker => :foo_worker, :job_key => ''1'') worker = MiddleMan.worker(:worker => :foo_worker, :job_key => ''1'') worker.bar() Querying all workers shows the foo_worker_1 is there.. >> pp MiddleMan.query_all_workers {:type=>:all_worker_status} {:log_worker=>nil, :foo_worker_1=>{:rand=>679}} I''m using rails 2.02, Packet 0.1.5 and Chronic 0.2.3. I tried the mainline git version but got this error. It needs a newer version of Packet? `load_missing_constant'': uninitialized constant Packet::BinParser (NameError) Many Thank...

...t; :foo_worker) will now ABORT the worker, it won''t wait for tasks to finish. I am still skeptic about the behavior, but since that was the behavior in older version, I am continuing it. 4. Get information about all running workers: >> MiddleMan.all_worker_info => [{:worker=>:log_worker, :status=>:running, :job_key=>""}, {:worker=>:foo_worker, :status=>:running, :job_key=>""}] --- :backgroundrb: :port: 11006 :ip: localhost :environment: production :log: foreground :lazy_load: true :debug_log: false Those who have reported any bug...

Hi, Thanks for the help getting the new backgroundrb working, things are working fabulously now. I have two questions: 1) I have a few basic methods I need available on all my workers in order to communicate properly with my application... it seems to make the most sense right now to subclass BackgrounDRb::MetaWorker, or make a mixin module, because I''m actually extending some

...hronize'' from /usr/lib/ruby/1.8/logger.rb:496:in `write'' from /usr/lib/ruby/1.8/logger.rb:326:in `add'' from /usr/lib/ruby/1.8/logger.rb:374:in `info'' from /home/raghus/public_html/ feedflix.com/ff/vendor/plugins/backgroundrb/server/lib/log_worker.rb:17:in`process_request'' from /home/raghus/public_html/ feedflix.com/ff/vendor/plugins/backgroundrb/server/lib/log_worker.rb:10:in`receive_data'' from /usr/lib/ruby/gems/1.8/gems/packet-0.1.6/bin/../lib/packet/packet_worker.rb:56:in `receive_internal_data''...

...erate workers etc, but when I start the backgrounDRB server I get the following errors in the backgroundrb log file: >>/Applications/rubystack-1.4-beta-1/ruby/lib/ruby/gems/1.8/gems/packet-0.1.14/lib/packet/packet_master.rb:116:in `exec'': Exec format error - packet_worker_runner 7:6:log_worker:17:/Volumes/DATA/development/rails/sched/lib/workers:/Volumes/DATA/development/rails/sched/script/load_worker_env (Errno::ENOEXEC) >> from /Applications/rubystack-1.4-beta-1/ruby/lib/ruby/gems/1.8/gems/packet-0.1.14/lib/packet/packet_master.rb:116:in `fork_and_load'' >> fr...

...I select only a few servers, it works just fine! There is no definable threshold, I''ve had failures with only 4 servers selected and success with 12 servers selected. After such a connection error, the worker processes are still running: $ ps -ef | grep worker 09:08 ? 00:00:00 ruby log_worker 09:08 ? 00:00:00 ruby remote_command_worker 09:08 ? 00:00:00 ruby remote_command_worker 09:08 ? 00:00:00 ruby remote_command_worker 09:08 ? 00:00:00 ruby remote_command_worker 09:08 ? 00:00:00 ruby remote_command_worker Your help i...

Hi, I have successfully crossed all the hurdles to install Ruby on rails on a redhat 5 Linux based system. But the last and the biggest hurdle i am facing at this moment is installing backgrounrb :( I followed all the steps from the http://backgroundrb.rubyforge.org/ 1. sudo gem install chronic packet 2. script/plugin install svn://rubyforge.org/var/svn/backgroundrb [IMP:::: I had to drop

I''m using a plugin which adds a method to ActiveRecord::Base http://similetimelinerailshelper.googlecode.com/svn/trunk/simile_timeline/ This adds an "acts_as" type declaration to the Models, via the file in vendor/plugins/simile_timeline/lib/simile_timeline.rb Rails is working with these declarations, and they are being used successfully in ''regular