similar to: deadlocks in Drb Server

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 have spent days trying to figure out how to get UTF-8 working with my site. Here''s my environment: Linux version 2.6.16.29-xen_3.0.3.0 Ruby 1.8.4 (2005-12-24 [i386-linux] Rails 1.2.3 mongrel (1.0.1) mongrel_cluster (1.0.2, 0.2.1) ferret (0.11.4) acts_as_ferret stable plugin Ferret DRB server When I don''t use an analyzer with my acts_as_ferret declaration, everything works

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''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''m running a bunch of proxybalanced mongrels on a windows server. and since the memory consumption of all those mongrels is getting too high i wanted to set up the DRb''ed ferret server. but script/ferret_start doesn''t work and seems to be written for linux (unix) only. is there a way to run it on windows? -- Posted via http://www.ruby-forum.com/.

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

Hello, I''ve been trying to get my head around ferret and the one thing that stumps me is how I might use Drb on a dedicated server with multiple clients using the SAME application but each with their own private database and other file assets (in an uploads directory within the app) Thank you for any suggestions, pointer etc. Also I''d be very interested in hearing from those

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 folks! Does anyone have any example code for using a DRb Ferret server? No AAF. Dave - is yours ready? I know Jens has one, but I was hoping for something more stand-alone. I assume Jens has a lot of other code in there. Schnitz -------------- next part -------------- An HTML attachment was scrubbed... URL:

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

Hi. We''ve had some problems with ferret not being able to load our classes (stack trace below for the curious). I nailed it down to a deployment issue, where an old instance of ferret drb was running. I don''t understand the details quite yet, but the result was the the old ferret was never shutdown during redeployment, and attempts were made to start up a new one. Anywho,

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

I''m hoping for a little insight. We''re using ferret with DRb server and having a hard time getting it to come back up on reboot of the machine. In our RAILS_ROOT directory, we''ve got a script named start_ferret. Here''s the content: #!/bin/bash FERRET_USE_LOCAL_INDEX=1 script/runner -e production vendor/plugins/acts_as_ferret/script/ferret_start

I blogged about some of the problems with aaf in production (http://www.jroller.com/BrightCandle) yesterday but inspired by the poitive response I thought I would share the perceived problems and discuss some of the potential solutions to help newcomers and make aaf work as if by magic just like Rails does. All of these problems boil down to one simple problem, running acts as ferret in a

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

(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 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 am new to ferret and am just reading about it in the O''reilly shortcuts as well as other web resources. My app is a Rails app and so I am looking into acts_as_ferret as well. There are some questions for which I couldn''t find answers in the material I have read so far so I''d appreciate any help on these from the list. A bit of a background. My app will have 10,000 -

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