similar to: solaris SMF to start ferret drb server

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

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

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

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 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 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 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/.

Hi there, after recently deploying my app, I have noticed that the search results are not being displayed... When I look in my app, I also notice that the apps content (search criterea) is not being indexed, so I dont have an index folder being created. I read on a google post that it may be that the ferret.yml server isn''t started (or perhaps the content of this file are not right) I

(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''m doing the next. 1, rails hecc 2, cd hecc 3, script/plugin install svn://projects.jkraemer.net/acts_as_ferret/tags/stable/acts_as_ferret 4, RAILS_ENV=production vendor/plugins/acts_as_ferret/script/ferret_start vendor/plugins/acts_as_ferret/script/ferret_start:21:in `require'': no such file to load -- vendor/plugins/acts_as_ferret/script/../config/boot (LoadError)

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

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

AFAICT, ferret_server should be able to handle multiple clients writing to it at once, since ferret itself is thread safe. However, it''s not clear whether running concurrent index rebuilds on different would be possible, since they run inside ferret_server. Anyone have experience with this? -ryan

Hi - I have a fresh install of OSX, Rails, Ruby, Ferret, AAF etc ... Everything is working fine, I can start mongrel, I can start backgroundrb, but Ferret Drb ... doesn''t want to work. RAILS_ENV=development script/ferret_start Gives me: env: script/runner: Permission denied Is there a way I can debug this to figure out what is going on - or is there another way to start Ferret Drb?

Hi, I''d like to share the ferret indexes between deployments of a Rails app. At the moment the index is stored in #{RAILS_ROOT}/index meaning that it gets moved and must be rebuilt after every deploy. I guess the simplest solution would be to put it under log/ which is already shared by capistrano, any other ideas? Also, script/ferret_stop doesn''t work when run on a fresh