similar to: Starting script/ferret_start problems

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

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

Hi folks, I have several models that index well in Drb mode. However, I have one scenario where it works in normal mode, but not in Drb mode. model A field :one end model B belongs_to :a field :two delegate :one, :to => :a acts_as_ferret :fields => { :one => {}, :two => {} }, :remote => true end If I leave off the :remote parameter, it works. Or, if I don''t

I''m having problems getting the DRb server running with the aaf gem. I tried it with the plugin installed in my application, and it worked. I suspect the problem has something to do with the startup scripts expecting certain files to be in certain relative file paths. Any insights are appreciated, and maybe if you have time you can update the wiki document :) Thanks for a great

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

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

Jesse Grosjean wrote: > I''m trying to write a solaris SMF file to launch the ferret drb server. Hmm, I think I''ve hit a similar problem. I''ve just upgraded to the latest ferret trunk from an old aaf stable where the script/ferret_start and script/ferret_stop scripts were still in use. now if I call the old script... RAILS_ENV=production script/ferret_start

I would like to unify the ferret_start and ferret_stop scripts into a single script. My motivation is to make the scripts more like the other rails scripts, and to also make it fit into monitoring schemes better. I realize that some work was done recently to allow the scripts to be run from script/runner, but I think a unified script is a better approach. A unified script would allow more

hi, guys: two acts_as_ferret questions! 1, ruby script/plugin install svn://projects.jkraemer.net/acts_as_ferret/tags/stable/acts_as_ferret sh: svn: command not found i can not install acts_as_ferret to my Rails project. what''s wrong? i''m useing rhel 4! 2, i downloaded the acts_as_ferret-0.4.0.tgz at http://rubyforge.org/frs/?group_id=2916&release_id=10617 and uploaded to

Hi, Rails 1.2.2 Ruby 1.8.5 Ferret 0.11.4 I have pretty big forum that has 2 columns that are indexed, in addition to this couple more tables with far less data are indexed. It seems that first index update works. Mysqld process takes the idle CPU time, but behaves nicely.. until at some point it takes 99% and doesn''t let other processes use it :) I''m forced to restart mysqld.

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

I set up ferret and it''s running fine normally. Now I want to hook up the backgroundrb server. However whenever I try to do a search, I get this error: (druby://localhost:9010) /usr/local/lib/ruby/1.8/drb/drb.rb:1075:in `method_missing'' (druby://localhost:9010) ./vendor/plugins/acts_as_ferret/lib/remote_index.rb:20:in `find_id_by_contents'' (druby://localhost:9010)

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

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

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

Hi, I have been running ferret for several months now, but want to make use of the new Drb functionality. So I am running Rails Stable (off the branch), Ferret 0.11.4, and the latest AAF. I have a ferret_server_yml file in my RAILS_ROOT/config folder: production: host: localhost port: 9009 pid_file: log/ferret.pid And I took the three scripts from the AAF plugin and put them into my

Hello, First the specs: ruby 1.8.6, rails 1.2.3, ferret 0.11.4, mongrel 1.0.1, mongrel_cluster 0.2.1 And the model''s aaf config: # Ferret search engine acts_as_ferret({:fields => {:name => {:boost => 10}, :summary => {:boost => 2}, :body => {:boost => 1, :store => :no},

Hello all, I''m using AAF right now to index my ~3million db records. However, any additions to these records are added to the database through an external script so the aaf activerecord hooks will not catch any updates. Since new records are only added rarely, I figured I could just add the new records manually in ferret from some type of script. I''ve been looking at the