search for: start_worker

Hi! I''m using the latest&greatest backgroundrb with rails 2.0.2 on ubuntu dapper. I''ve made an app that lets you run a query on several servers at once, which are selected at runtime. Therefore, for each server that is selected, I spawn a new worker and assign its work. After everything is completed, the workers are deleted. I often get this error:

Hi, pardon if this is a duplicate mail, I forgot to click the subscription link the first time around. I''ve been using backgroundrb for a while now (older version) and I''ve had so many headaches because of it that I began looking for a replacement technology. And then I saw the new and shiny backgroundrb website, looking good! Initially I used the version maintained by

.../core.rb:156:in `start_reactor'' from RAILS_HOME/vendor/plugins/backgroundrb/framework/core.rb:147:in `loop'' from RAILS_HOME/vendor/plugins/backgroundrb/framework/core.rb:147:in `start_reactor'' from RAILS_HOME/vendor/plugins/backgroundrb/framework/worker.rb:21:in `start_worker'' from RAILS_HOME/vendor/plugins/backgroundrb/framework/packet_master.rb:134:in `fork_and_load'' from RAILS_HOME/vendor/plugins/backgroundrb/framework/packet_master.rb:115:in `start_worker'' from RAILS_HOME/vendor/plugins/backgroundrb/server/master_worker.rb:165:in...

...l/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_core.rb:124:in `loop'' from /opt/local/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_core.rb:124:in `start_reactor'' from /opt/local/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_worker.rb:20:in `start_worker'' from /opt/local/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_master.rb:133:in `fork_and_load'' from /opt/local/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_master.rb:96:in `load_workers'' from /opt/local/lib/ruby/gems/1.8/gems/pack...

...uby/gems/1.8/gems/packet-0.1.6/bin/../lib/packet/packet_core.rb:126:in `loop'' from /usr/lib/ruby/gems/1.8/gems/packet-0.1.6/bin/../lib/packet/packet_core.rb:126:in `start_reactor'' from /usr/lib/ruby/gems/1.8/gems/packet-0.1.6/bin/../lib/packet/packet_worker.rb:21:in `start_worker'' from /usr/lib/ruby/gems/1.8/gems/packet-0.1.6/bin/packet_worker_runner:33:in `load_worker'' from /usr/lib/ruby/gems/1.8/gems/packet-0.1.6/bin/packet_worker_runner:26:in `initialize'' from /usr/lib/ruby/gems/1.8/gems/packet-0.1.6/bin/packet_worker_runne...

...n is, that the trigger_args are wrong, but i checked everything a thousend times and maybe i dont see the wood for the trees (maybe I have to sleep a litte bit more ;) ) Even the backgroundrb_11006_debug.log don''t say anything i can use to find the error: > 00000012{ > : type:start_worker: > schedule{:calculate{:trigger_args"*/5 * * * * * *: data"6: > job_key@ ; > @ > {:data=>"6", :worker=>:account_worker,...

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

I lost my "connection lost" error.. but now I''ve got a "Mysql::Error: MySQL server has gone away" error.. It comes from: /usr/lib/ruby/gems/1.8/gems/activerecord-1.15.6/lib/active_record/connection_adapters/abstract_adapter.rb:128:in ''log''. I''m not sure if Rails / BackgroundRb uses it .. but i''ve got the mysql (2.7) gem

Hi there, I''ve been digging around trying to find some information (mostly examples) on how one would handle a progress bar upload using BackgrounDRb and File Column. I did read http://backgroundrb.rubyforge.org/ and Ezra''s blog of course, but I still have a few questions. I made a simple upload form (as a test) that is submitted to the "upload_song" action. def

...register_status'' for #<SessionWorker:0xb6e7d52c> (NoMethodError) from /home/rut216/dev/illinicourses/vendor/plugins/backgroundrb/server/lib/meta_worker.rb:129:in `worker_init'' from /var/lib/gems/1.8/gems/packet-0.1.14/bin/../lib/packet/packet_worker.rb:19:in `start_worker'' from /var/lib/gems/1.8/gems/packet-0.1.14/bin/packet_worker_runner:33:in `load_worker'' from /var/lib/gems/1.8/gems/packet-0.1.14/bin/packet_worker_runner:26:in `initialize'' from /var/lib/gems/1.8/gems/packet-0.1.14/bin/packet_worker_runner:47:in `...

...71224050255/vendor/plugins/backgroundrb/framework/core.rb:147:in `loop'' /var/www/apps/rpg/releases/20071224050255/vendor/plugins/backgroundrb/framework/core.rb:147:in `start_reactor'' /var/www/apps/rpg/releases/20071224050255/vendor/plugins/backgroundrb/framework/worker.rb:21:in `start_worker'' /var/www/apps/rpg/releases/20071224050255/vendor/plugins/backgroundrb/framework/packet_master.rb:134:in `fork_and_load'' /var/www/apps/rpg/releases/20071224050255/vendor/plugins/backgroundrb/framework/packet_master.rb:98:in `load_workers'' /var/www/apps/rpg/releases/200...

Hi, nice work on BackgrounDrb! I have a question, though: What would be the best way to enable database access for a worker, preferably through ActiveRecord models. Background: I''m trying to write a worker that periodically gets data from an external source, writes it to the database and is then displayed by Rails. Anybody done something like this? Thanks in advance! ciao,

...#39;' from brb-test/vendor/plugins/backgroundrb/server/meta_worker.rb:258:in `new_load_schedule'' from brb-test/vendor/plugins/backgroundrb/server/meta_worker.rb:183:in `worker_init'' from brb-test/vendor/plugins/backgroundrb/framework/worker.rb:20:in `start_worker'' from brb-test/vendor/plugins/backgroundrb/framework/packet_master.rb:134:in `fork_and_load'' from brb-test/vendor/plugins/backgroundrb/framework/packet_master.rb:98:in `load_workers'' from brb-test/vendor/plugins/backgroundrb/framework/packet_mas...

...ib/workers (Errno::ENOENT) from /opt/ruby-enterprise-1.8.6-20081215/lib/ruby/gems/1.8/ gems/packet-0.1.14/lib/packet/packet_master.rb:116:in `fork_and_load'' from /opt/ruby-enterprise-1.8.6-20081215/lib/ruby/gems/1.8/ gems/packet-0.1.14/lib/packet/packet_master.rb:80:in `start_worker'' from /home/antz/declix.com/production/vendor/plugins/ backgroundrb/server/lib/master_proxy.rb:101:in `load_and_invoke'' from /home/antz/declix.com/production/vendor/plugins/ backgroundrb/server/lib/master_proxy.rb:88:in `reload_workers'' from /...

Hi there, I''m trying to create a worker to do some asynchronous web client work and update the data model with its results. It seems, however, that every call I make to an ActiveRecord subclass causes the whole thing to block. At least I think it''s blocked. Right now I''m just using debug log output. Is there a decent way to debug/test workers I can try? Is there any

...from /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_core.rb:124:in `loop'' from /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_core.rb:124:in `start_reactor'' from /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_worker.rb:20:in `start_worker'' from /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_master.rb:133:in `fork_and_load'' from /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_master.rb:96:in `load_workers'' from /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packe...

Hi there, I''ve been digging around trying to find some information (mostly examples) on how one would handle a progress bar upload using BackgrounDRb and File Column. I did read http://backgroundrb.rubyforge.org/ and Ezra''s blog of course, but I still have a few questions. I made a simple upload form (as a test) that is submitted to the "upload_song" action. def

Hey all, I need to launce a rather lengthy process from a small Rails application. It''s the sort of thing (sending out an email newsletter) that would need to be launched from a browser window, but the browser doesn''t need to stick around to see it through. I played around with Thread.new, but I think, based on limited testing, that the threads need to complete before the view

Probably a simple question, but humor me: Let''s say I have a page (in Rails) that lets a user type a shell command (say, ''ping blah.com'') into a form and it fires off a worker that then updates that page using AJAX (all of this is working so far). How would I correctly wrap the worker in a begin..rescue so that it spits out ''invalid command''

...(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'' >> from /Applications/rubystack-1.4-beta-1/ruby/lib/ruby/gems/1.8/gems/packet-0.1.14/lib/packet/packet_master.rb:80:in `start_worker'' >> from /Volumes/DATA/development/rails/sched/vendor/plugins/backgroundrb/server/lib/master_proxy.rb:16:in `initialize'' >> from /Applications/rubystack-1.4-beta-1/ruby/lib/ruby/gems/1.8/gems/packet-0.1.14/lib/packet/packet_master.rb:19:in `run'' >>...