search for: packet_cor

...39;' from /usr/lib/ruby/gems/1.8/gems/packet-0.1.6/lib/packet/packet_nbio.rb:51:in `each_with_index'' from /usr/lib/ruby/gems/1.8/gems/packet-0.1.6/lib/packet/packet_nbio.rb:51:in `write_and_schedule'' from /usr/lib/ruby/gems/1.8/gems/packet-0.1.6/lib/packet/packet_core.rb:166:in `handle_write_event'' from /usr/lib/ruby/gems/1.8/gems/packet-0.1.6/lib/packet/packet_core.rb:163:in `each'' from /usr/lib/ruby/gems/1.8/gems/packet-0.1.6/lib/packet/packet_core.rb:163:in `handle_write_event'' from /usr/lib/ruby/gems/1.8/gems/...

.../home/d96440a6/testapp/vendor/plugins/backgroundrb/server/lib/master_worker.rb:170:in `post_init'' from /opt/local/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_connection.rb:21:in `invoke_init'' from /opt/local/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_core.rb:302:in `decorate_handler'' from /opt/local/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_core.rb:76:in `accept_connection'' from /opt/local/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_core.rb:202:in `handle_external_messages'' fr...

...from /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_meta_pimp.rb:18:in `receive_data'' from /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_master.rb:64:in `handle_internal_messages'' from /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_core.rb:176:in `handle_read_event'' from /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_core.rb:174:in `each'' from /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_core.rb:174:in `handle_read_event'' from /usr/lib/ruby/gems/1.8/gems...

...'' from /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/ packet_meta_pimp.rb:18:in `receive_data'' from /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/ packet_master.rb:64:in `handle_internal_messages'' from /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/ packet_core.rb:176:in `handle_read_event'' from /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/ packet_core.rb:174:in `each'' from /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/ packet_core.rb:174:in `handle_read_event'' from /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib...

...l/lib/ruby/gems/1.8/gems/packet-0.1.10/lib/packet/packet_parser.rb:26:in `extract'' /Users/brent/near-time/near-time.net-exp-rescue-princexml-5504/vendor/plugins/backgroundrb/server/lib/master_worker.rb:32:in `receive_data'' /opt/local/lib/ruby/gems/1.8/gems/packet-0.1.10/lib/packet/packet_core.rb:228:in `read_external_socket'' /opt/local/lib/ruby/gems/1.8/gems/packet-0.1.10/lib/packet/packet_core.rb:220:in `handle_external_messages'' /opt/local/lib/ruby/gems/1.8/gems/packet-0.1.10/lib/packet/packet_core.rb:194:in `handle_read_event'' /opt/local/lib/ruby/gems/1.8/...

...#39; /usr/local/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/ packet_parser.rb:29:in `extract'' /Users/sweiss/Documents/workspace/RACE-local/vendor/plugins/ backgroundrb/server/lib/master_worker.rb:31:in `receive_data'' /usr/local/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/ packet_core.rb:212:in `read_external_socket'' /usr/local/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/ packet_core.rb:204:in `handle_external_messages'' /usr/local/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/ packet_core.rb:178:in `handle_read_event'' /usr/local/lib/ruby/gems/1....

...groundrb/server/lib/master_proxy.rb:84:in `reload_workers'' from /home/antz/declix.com/production/vendor/plugins/ backgroundrb/server/lib/master_proxy.rb:21:in `initialize'' from /opt/ruby-enterprise-1.8.6-20081215/lib/ruby/gems/1.8/ gems/packet-0.1.14/lib/packet/packet_core.rb:141:in `call'' from /opt/ruby-enterprise-1.8.6-20081215/lib/ruby/gems/1.8/ gems/packet-0.1.14/lib/packet/packet_core.rb:141:in `start_reactor'' from /opt/ruby-enterprise-1.8.6-20081215/lib/ruby/gems/1.8/ gems/packet-0.1.14/lib/packet/packet_core.rb:139:in `lo...

...n get around it by limiting the DB query to return no more than 255 records and then all is fine. No problems at all. But over that, I see this issue. Repeatedly. Here''s what I found in my log/backgroundrb_11007_debug.log file. ========= /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_core.rb:124:in `start_reactor'' /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_master.rb:21:in `run'' /home/raghus/public_html/ feedflix.com/ff/vendor/plugins/backgroundrb/server/lib/master_worker.rb:166:in`initialize'' ./script/backgroundrb:42:in `new'' ./sc...

...c/src/propertyadmin/trunk/vendor/plugins/backgroundrb/server/lib/meta_worker.rb:325:in `each'' from /Users/pkmiec/src/propertyadmin/trunk/vendor/plugins/backgroundrb/server/lib/meta_worker.rb:325:in `check_for_timer_events'' from /Library/Ruby/Gems/1.8/gems/packet-0.1.5/lib/packet/packet_core.rb:125:in `start_reactor'' from /Library/Ruby/Gems/1.8/gems/packet-0.1.5/lib/packet/packet_core.rb:124:in `loop'' ... 6 levels... from /Library/Ruby/Gems/1.8/gems/packet-0.1.5/lib/packet/packet_master.rb:20:in `run'' from /Users/pkmiec/src/propertyadmin/trunk/vendor/pl...

...nDRb server intermittently bails out with the following exception in the middle of a long running task running on a Worker sub classed from BackgrounDRb::MetaWorker (the point at which it raises this exception is different each time it runs) /opt/local/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_core.rb:145:in `schedule_write'': You have a nil object when you didn''t expect it! (NoMethodError) The error occurred while evaluating nil.instance from /opt/local/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_nbio.rb:57:in `write_and_schedule'' from /Users/joel/git/dea...

...y backgroundrb_server_11007.log This seems to happen in a non-repeatable way - so every 2 days or sometimes after 4-5 days, my b/g process dies with this error. Is this something anyone else has seen - any fixes? Thanks, Raghu ===============true /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_core.rb:145:in `schedule_write'': You have a nil object when you didn''t expect it! (NoMethodError) The error occurred while evaluating nil.instance from /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_nbio.rb:57:in `write_and_schedule'' from /usr/lib/ru...

...d 4/03/08) I installed the packet and chronic gems as per instructions. I used git to download BDrb as per instructions and ran the rake setup script. When I run script/backgroundrb from my rails app main directory, I get the following error: /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_core.rb:145:in `schedule_write'': You have a nil object when you didn''t expect it! (NoMethodError) The error occurred while evaluating nil.instance from /usr/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/packet_nbio.rb:57:in `write_and_schedule'' from /usr/lib/r...

...the middle of a long running task running on a Worker sub classed >>> from BackgrounDRb::MetaWorker (the point at which it raises this >> exception >>> is different each time it runs) >>> >> /opt/local/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/ >> packet_core.rb:145:in >>> `schedule_write'': You have a nil object when you didn''t expect it! >>> (NoMethodError) >>> The error occurred while evaluating nil.instance from >>> >> /opt/local/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/ >> pac...