similar to: Is DRb server *really* required in production mode?

Hi, we still have the problem in that the Ferret Drb server dies on us sometimes. Looking through ferret_server.out and we come accross this: deadlock 0xb7261cb0: sleep:F(1012) - /usr/lib/ruby/1.8/drb/drb.rb:566 deadlock 0xb71d8654: sleep:F(409) - /usr/lib/ruby/1.8/drb/drb.rb:566 deadlock 0xb723f3e0: sleep:F(7) - /usr/lib/ruby/1.8/drb/drb.rb:566 deadlock 0xb72607c0: sleep:F(11) -

Whenever I tried to start mongrel_rails with the upload progress script, it would die with the following error: /usr/local/lib/ruby/1.8/drb/drb.rb:837:in `getaddrinfo'': getaddrinfo: No address associated with nodename (SocketError) from /usr/local/lib/ruby/1.8/drb/drb.rb:837:in `open_server_inaddr_any'' from /usr/local/lib/ruby/1.8/drb/drb.rb:860:in

Hi, all- I started playing with RSpec in a new Rails app. I''ve installed the plugin and bootstrapped it, and run ''script/rails_spec_runner'' (not rails_spec_server as the website currently reads, btw) in a separate shell, then in another shell I run ''script/rails_spec'' and get the following: /usr/local/lib/ruby/1.8/drb/drb.rb:837:in

Hi All, I''m using Backgroundrb as a general purpose long-running-task back-end (upload processing, email sending, etc), and it''s been a great solution. However I''ve recently run into some some intermittent connection issues that have me baffled. I''m running on apache2/fcgid and the problem occurs in both devlopment and production mode. The problem seems to

Hi all! We use the DRB-Server Backend and are getting strange DRb::DRbConnErrors lately. It started with: too large packet 687865856 (druby:/10.0.0.10:9010) /usr/lib/ruby/1.8/drb/drb.rb:573:in `load'' and later only this one: premature marshal format(can''t read) (druby:/10.0.0.10:9010) /usr/lib/ruby/1.8/drb/drb.rb:580:in `load'' Do you have any ideas what that

I was just trying to use acts_as_ferret with DRb and filter_proc, without much success. My guess is that this isn''t possible because there''s no way to send the proc to the DRb server, correct? Person.find_by_contents("jonathan", :filter_proc => proc {}) causes an exception when using DRb (DRb::DRbConnError: DRb::DRbServerNotFound). I can work around this by

I''m trying to use the Ferret DRB server to avoid concurrency issues when using multiple mongrels. I can successfully add and edit data on my index via the DRB server, however, when I search the index, I get the following error: DRb::DRbConnError (DRb::DRbServerNotFound): /usr/lib/ruby/1.8/drb/drb.rb:1647:in `current_server'' /usr/lib/ruby/1.8/drb/drb.rb:1709:in

I want to use DRb within my Rails app. Right now I''ve got a very basic class: class PaymentGateway cattr_accessor :ssl_config, :host, :port def self.gateway @@gateway ||= new end def process(amount, card, type = :auth) @biller.process(amount, card, type) end def set_card(user_id, number) @biller.set_card(user_id, number) end protected def initialize

Hi, Sorry if this is a stupid question! I used to have a site running on Merb 0.1.0. When running as a cluster, it would automatically start a drb process to co-ordinate the upload progress monitoring. Since uploading to 0.3.7 (a bit of a jump!), the drb process hasn''t started automatically. I seem to start one if I run merb -s 32323 manually, but when I do check on a file

The problem with getting DRb to luanch on reboot is the same problem causing some people to ahve trouble getting mongrel clustersw to come back up on reboot. The problem is the PATH. ON many new RH distributions running SELinux, /usr/local/bin is not added to the PATH until reboot is complete. Therefore, those of having installed ruby in /usr/local/bin run in to issues. SO, hoping to save

Hello List, For a small project I''ve been using ''ruby script/spec -X spec'' to execute my specs. Now that I added ZenTest on it, found that the test takes longer to run due the complete load of test environment. Since autotest uses ''script/spec -O spec/spec.opts'' as the command, I decided to add --drb to spec.opts Using --drb or -X, spec_server is

(Sorry if some people see this twice. I originally posted this question from ruby-forum.com, but didn''t realize that the Ferret forum was a mirror and that I actually wasn''t a member.) Anyway, I''ve read all the documentation I could find, and read most of this forum, but I''m a still a little confused on running a ferret DRb server. All the examples seem to be

I''ve installed the ferret gem. I installed AAF as a plugin into my vendor/plugins directory of my project. In development environment my searches work just fine, without any problems. For production I configured the ferret_server.yml file with correct information about the machine my DRb server is running on. I start the ferret server with the following command: ruby script/runner

Hi all, We''re attempting to use Ferret with the DRb server at the moment, and it doesn''t work, at all... = Executive Summary The DRb server process keeps on calling the remote index to the DRb server process... Which means DRb is calling itself, and itself, and itself, until Ruby kills the Thread with a SystemStackLevel error. = The excruciating details... # Mongrel is

I am seeing this in my ferret_server.log when I do a search: DRb server: ensure_index_exists for class Myclass1 DRb server: ensure_index_exists for class Myclass2 DRb server: ensure_index_exists for class Myclass3 DRb server: ensure_index_exists for class Myclass4 #method_missing(:id_multi_search, ["Myclass1", "test*", ["Myclass4", "Myclass3",

Hi, I have my Model as follows: class Mutation < ActiveRecord::Base acts_as_ferret ({:fields => {:description=>{}, :product_id=>{:index => :untokenized}, :product_description=>{}, :product_label_description=>{}, :product_label_free=>{}, :product_product_id_supplier=>{}, :product_description_supplier=>{}, :supplier_description=>{}, :pub_date_sort

Before I chalk this up as a bug and report it, I just want to make sure I''m not doing something silly. Running ZenTest''s autotest on OS 10.4.10 with RSpec 1.0.8, drb, produces the following failed test: ActiveRecord::AssociationTypeMismatch in ''User should create an avatar with uploaded_data'' Avatar expected, got Avatar This only happens with that exact

Hi, I have a question regarding RoR and DRb. First of all, I tested with simple client/server examples and everything worked as expected. I have the following lines in my environment.rb: DRb.start_service $rem_obj = DRbObject.new(nil, "druby://#{rname}:9001") Since rem_obj is a global variable, I can call it from any controller and the invoked procedure is run on the server. However,

The Problem: The application is using the AAF plugin. When I attempt to rebuild the index on the production server from the console, I get the following error: ------ DRb::DRbConnError: druby://ferret.mydomain.com:9010 - #<Errno::ETIMEDOUT: Connection timed out - connect(2)> from /usr/lib/ruby/1.8/drb/drb.rb:736:in `open'' from /usr/lib/ruby/1.8/drb/drb.rb:729:in

We all know that using ferret/aaf without the drb server is not thread-safe-- but why not? Would it be so hard to sacrifice performance by using a simple locking system? Very often I run into a situation where I want to quickly stage a project, and I want to use a few mongrels but don''t want to configure every last piece of the system, including the drb server. It would be nice