similar to: acts_as_ferret, DRb, and filter_proc

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''m having problems sorting on untokenized fields. I have one field that sorts fine, but there are others that seem to sort on a different field. Here''s the index description: acts_as_ferret :remote=>true,:fields=>{:name=>{:boost=>2},:name_for_sort=>{:index => :untokenized}, :city=>{:boost=>2}, :city_for_sort=>{:index=>:untokenized},

I am having a strange problem starting the acts_as_ferret Drb server on a particular Linux machine (Debian Etch). The same setup works fine on my Mac (OSX). Without the Rails application running (yes, I''ve checked several times) I get the following error if I try to start the ferret server and one of my models contains :remote => true for acts_as_ferret: >> script/ferret_start

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

I am running ferret (0.11.4) and acts_as_ferret (stable from svn) in a rails 1.2.3 app in production using the DRb server. I recently upgraded my configuration and the method with which I start and stop the server no longer works: Here is the command I would like to use (and have used in the past) to start the aaf server: $ /Library/WebServer/rails/ccdb/current/script/runner -e production

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

People, I''m trying to run the ruby debugger against a Test::Unit::TestCase class which is a parent of a Rails class. I started my study with a simple script: # # bikle_test.rb # require ''test/unit'' class BikleTest < Test::Unit::TestCase def setup @string10 = "hello" end def test10 assert_equal @string10, "hello" end end The

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

so i have an after_create method on my track model that kicks off a background process that converts an mp3 to a swf. this is working fine locally on my machine, but upon moving it to my production server, i am getting the following error. I''ve only been using backgroundRB for like 48 hours, so i''m not really sure what this means or where to go. any ideas?

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",

I just had an interesting issue on a production system that has been running nicely for about a year. There were approximately 10,000 backgroundrb temp files in the /tmp directory. It looks like backgroundrb wasn''t cleaning them up. I noticed it with the following error: DRb::DRbConnError: drbunix:///tmp/backgroundrb.20015/ backgroundrb_logger_0_0.101544829808665 -

Hi! Aaf trunk has undergone several major refactorings the last days, with the result that you can now transparently switch your app from local to remote indexing and back :-) If you plan to scale your app to more than one physical machine, or if you have problems with corrupted indexes and the like under high load, you really should give this a try. I wrote some documentation to get you

After switching to the DRb server, I am experiencing strange behavior when sorting on score. My app was working as expected before the switch. Both before and after the switch, my app sorts properly on other fields, such as date. For sorting on score, I am using the following option find_by_contents option: :sort => Ferret::Search::SortField::SCORE Before switching to DRb, this worked

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

Hi, I''m not much of a developer but I''ve been using backgroundrb for a while now and with the release of 0.2.1 it looks like I can finally upgrade from the old version (0.2.0 had some weird issues when jobs just wouldn''t run, seems to have cleared up now - Thanks!). Anyhow, while I''m doing this, I would like to tackle this problem. Most tasks I run in

I need a way to kill the ferret_server drb process programatically, so I can start/stop it as part of the capistrano deployment process. This should be as simple as adding some sort of stop method to ActsAsFerret::Remote::Server. I was just messing around and was able to do it by modifying method_missing to look for the :stop method and then calling DRb.thread.exit -- this is not good enough for

Hello, maybe someone can help with backgroundrb. I''ve written an application, which makes use of backgroundrb. Everything works fine on my development machine, but it crashes on my production server. Something seems to be wrong with backgroundrb, but I don''t know the cause. All I get is the error message attached below, which is extracted from the production.log. I

Hello, I have been trying to set up the remote indexing for acts_as_ferret and followed the guide here: http://projects.jkraemer.net/acts_as_ferret/wiki/DrbServer I added :remote => true to my models and then specified host and port for the production environment. After defining the host/port for production, I tried to run my development server and received the following error:

I''m having a problem where the DRb server seems to be disappearing (crashing?) and I don''t know how to track down the cause or work around the problem. Unfortunately I haven''t found a way to reproduce the problem, but it seems to happen fairly often (maybe once a day). Other then that ferret seems to be working well. I can''t seem to find any trace of the

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