search for: packet_worker_runn

...b/ruby/gems/1.8/gems/packet-0.1.6/bin/../lib/packet/packet_worker.rb:56:in `receive_internal_data'' from /usr/lib/ruby/gems/1.8/gems/packet-0.1.6/bin/../lib/packet/packet_parser.rb:38:in `call'' ... 13 levels... from /usr/lib/ruby/gems/1.8/gems/packet-0.1.6/bin/packet_worker_runner:47:in `new'' from /usr/lib/ruby/gems/1.8/gems/packet-0.1.6/bin/packet_worker_runner:47 from /usr/bin/packet_worker_runner:19:in `load'' from /usr/bin/packet_worker_runner:19 /usr/lib/ruby/gems/1.8/gems/packet-0.1.6/lib/packet/packet_nbio.rb:41:in `write_once...

..."normal" state I found before it starting going haywire: top - 15:11:13 up 5 days, 5:05, 3 users, load average: 3.10, 3.09, 3.02 PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 17508 deploy 15 0 49300 35m 2688 S 11.8 1.7 7:54.65 /usr/bin/ruby1.8 /usr/bin/packet_worker_runner 18:16:mblox_sender:94:/home/deploy/mbargo/lib/workers:/home/deploy/mbar 17504 deploy 15 0 49648 35m 2688 S 8.2 1.7 8:01.64 /usr/bin/ruby1.8 /usr/bin/packet_worker_runner 16:14:mblox_sender:94:/home/deploy/mbargo/lib/workers:/home/deploy/mbar 14141 deploy 15 0 20796 17m 1612 S 0.3...

...r) 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 `new'' from /var/lib/gems/1.8/gems/packet-0.1.14/bin/packet_worker_r...

...install works, I can generate 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'...

Hi, I still have the following error while loading backgroundrb : /opt/ruby-enterprise-1.8.6-20081215/lib/ruby/gems/1.8/gems/ packet-0.1.14/lib/packet/packet_master.rb:116:in `exec'': No such file or directory - packet_worker_runner 14:11:maintenance_worker:64:/home/ antz/declix.com/production/lib/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/rub...

Hi Folks, I have been working to fix BackgrounDRb memory usage as such. Ruby1.8 GC isn''t fork friendly and it seems to use a lot of memory because when you fork, it sets a bit in all the objects in global scope which causes OS to all pages in child process. A classic solution is to use fork and exec, rather than just fork. Its working and pretty stable, but you loose ability to pass

I''m working on an application that does extensive database searching. These searches can take a long time, so we have been working on moving the searches to a backgroundrb worker task so we can provide a sexy AJAX progress bar, and populate the search results as they are available. All of this seems to work fine until the size of the search results gets sufficiently large, when we start

...ver. I have noticed that I have 2 ruby processes running on my server: "ruby" and "ruby1.8". Is this normal? If not, how do I get rid of the 2nd one? For Apache, I have 6 processes running - what is that good for? How can I reduce them or should I not? Thridly, I have 3 "packet_worker_runner" (from backgroundRB) processes running. Is it possible and OK to have only 1? If yes, how? Thanks a lot for any hints! Tom -- Posted via http://www.ruby-forum.com/.

I started emailing monit mailing list because I started getting this problem where I couldn''t start backgroundrb with monit anymore, thinking it was a monit problem. However, I back tracked a bit since I had added code to my project, and monit was able to start backgroundrb again. I seem to have zeroed in on the problem. I''m not sure where the problem lies - maybe monit or