similar to: Share monit.rc entry for Ferret Drb?

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

(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

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

Greetings, I''m certainly :-) too thick, but after reading Ferret and AAF''s documentation I''m still wondering if I really need a DRb server in production. At the moment, the planned structure for production mode is a single server running the app with Apache and fastcgi; as far as I know, Ferret is multithread-safe, isn''t it? So, is a DRb server required to

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

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:

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 am looking for solution to work with ferret without DRB. I would like to turn off ferret indexing from application and use existing ferret index only for searching (read only), while I would create indexes once a day from script. Is it possible and how to turn indexing off and would ferret still complain if 2 mongrels try to open index file. thanks, Bojan -- Posted via

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

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''re running Ferret and acts_as_ferret in our production environment. We have multiple mongrels talking to a single index on a separate (virtual) server over DRb. This is working ok for now, as our index updates are fairly infrequent. I''m concerned with the lack of rendundancy/scalability in this layout. Our index won''t get too big - maybe 100k indexed objects, each no

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

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

I''m finishing up a rails app that uses Ferret / AAF. I''m using shared hosting provided by railsplayground.com. My app is pretty small and is never going to get much traffic, so I''m going with the cheapest plan. Unfortunately, the cheapest plan doesn''t allow any static processes. I''ve read multiple recommendations to use a DRB server when using ferret

Hi ferreteers, I came across a segfault in the query parser. It had already been reported[1] and fixed[2], but it can lead to a denial of service. If you use Ferret anywhere that you allow users to execute queries, those users can crash your Ruby process with a specially crafted query. I''m sure you''re all using Monit or something for your Rails or drb processes, so

I am getting these errors after switchign to dRb: It is trying to call ''add'' on MY SourceListing class, not extended with the ferret indexing methods. Any ideas on where to fix this? I''m combing through the code now. no luck, trying to call class method instead ferret server error undefined method `add'' for SourceListing:Class

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

I''m getting an error that seems to be unique when trying to run ferret as a DRb in conjunction with acts_as_ferret. Locally, I can run in production mode with ferret running as a DRb and everything works great. When I transfer my project to my host, things begin to fall apart. Running ferret remotely as a DRb appears to work just fine, but ''mongrel_rails start''