similar to: [0.10.0] Random error when big import

Hi all ! Is Ferret 0.10.0 realy stable ? Because I converted all my code to the new API and many strange things appened. For exemple this, when I run a import script : /usr/lib/ruby/gems/1.8/gems/ferret-0.10.0/lib/ferret/index.rb:98:in `initialize'': End-of-File Error occured at <except.c>:103 in xpop_context (EOFError) Error occured in store.c:197 - is_refill current

The following exception occurred while trying optimize a large index: vendor/gems/rdig-0.3.4/lib/rdig/index.rb:46:in `optimize'': End-of- File Error occured at <except.c>:93 in xraise (EOFError) Error occured in store.c:216 - is_refill current pos = 0, file length = 0 Now, I get the following error any time I try to create a new index on the directory that I was trying

I was optimizing a 650MB using ferret (0.11.3) and I received the following error. I''ve seen some people have similar issues but I haven''t seen any resolutions. The contents of the index directory follow the error. Has anyone seen anything like this and found a resolution? Many thanks. /mnt/apps/search/releases/20070622175637/script/../config/../vendor/

Perhaps, I found where is my problem (during a big import). Why this silly (really silly :)) example crash ? http://pastie.caboo.se/10357 /usr/lib/ruby/site_ruby/1.8/ferret/index.rb:211:in `add_document'': IO Error occured at <except.c>:79 in xraise (IOError) Error occured in fs_store.c:225 - fso_flush_i flushing src of length -2 from

Everything was working fine till last night. This morning I have many errors. I am using acts_as_ferret. Last updated around a month ago on linux. There are two different type of exceptions. I have over 12 exception emails but these are the two distince types. First exception: A EOFError occurred in home#event_info: End-of-File Error occured at <except.c>:79 in xraise Error occured in

Hi, I''m using acts_as_ferret in with a mongrel and I'' m getting locking errors that after a while result in a corrupt database. I know about the problem with different processes writing to the index but I haven''t been able to get the DRB server working properly yet. I read on this list that another solution is to set :auto_flush to true but I''m not

Hi, I''m having some strange/random crashes with ferret when using different programs on the same index. I created a script to reproduce the errors: http://www.sig11.org/~seb/ferret_crash.rb Usage: In one terminal run: ruby ferret_crash.rb first In another terminal: ruby ferret_crash.rb Errors I usually get are but it is really random:

Hello Dave, Hello all, I''ve got this error because I try to search something and sort it by name : Argument Error occured at <except.c>:93 in xraise Error occured in sort.c:551 - field_cache_get_index Cannot sort by field "name". It doesn''t exist in the index. The problem, occur when my index is empty, so the field "name" does not exists. --

Hi Randomly I get the following error when users search EOFError (End-of-File Error occured at <except.c>:93 in xraise Error occured in compound_io.c:137 - cmpdi_read_i Tried to read past end of file. File length is <303> and tried to read to <351> ): what could be the problem? thanks -- Posted via http://www.ruby-forum.com/.

I am getting this issue also... Does anyone know what this is? When will Acts as Ferret be available for v10? Thanks for your help in desperation! Caspar wrote: > Okay previous post related to me trying to fix this problem with an > upgrade to ferret 0.10.0 but acts as ferret is obviously not compatible > with this new version of ferret. > My app is about to go into production and

Hi again, fields() method of Ferret::Index::LazyDoc return an array of integer (maybe the integer of the symbol? I don''t know) instead of symbols as explained in the doc : http://ferret.davebalmain.com/api_0.10.0/classes/Ferret/Index/LazyDoc.html#M000042 Any ideas ? -- Posted via http://www.ruby-forum.com/.

On an average I get this error twice or thrice a week. After I rebuild the index Event.rebuild_index it works fine. I''m a bit puzzled by this behavior. Why does this happen? I am using AAF. End-of-File Error occured at <except.c>:79 in xraise Error occured in store.c:216 - is_refill current pos = 301, file length = 301 /usr/local/lib/ruby/site_ruby/1.8/ferret/index.rb:517:in

Hello everyone, I was stress-testing my application (running on Rails via FastCGI) by letting two concurrent users (not human .. an app called ''siege'') a) save an Article and b) search for all Articles. I am searching via Article.ferret_index.search_each( ..) do |doc_id,score| doc = index[doc_id] .. end and writing via Article.ferret_index <<

We were using ferret (with acts_as_ferret) on our production boxes. Everything was going OK for a few days then we got a seg fault from it that brought down the box. The specs: * Rails 1.1.6 * Ruby 1.8.4 * Ferret 0.10.6 * RedHat ES 3 * Apache * Pound * 5 instances of Mongrel Can ferret handle multiple processes accessing it''s files at the same time? Not that we were doing this (but

Hi, I just installed ferret for the first time and integrated it with my app. On my dev machine it''s fine but on my production server I get this when I call find_by_contents(): Processing LinksController#results (for 24.185.105.59 at 2007-03-28 05:28:36) [POST] Session ID: 3f2dc7c17147c0e52178ba697a119833 Parameters: {"commit"=>"Search",

Hi Dave, The options hash is not used in search_each() method. -- Posted via http://www.ruby-forum.com/.

Disclaimer: ferret newbie here, don''t blame too hard. Hi, I''m trying to apply acts_as_ferret to apply search to my Person model: class Person < ActiveRecord::Base validates_presence_of :name, :surname acts_as_ferret :fields => [ ''name'', ''surname'' ] ... But when I try to save a new Person instance I get this error:

We''ve been running Ferret for a few months on our site with great result. But, just a monent ago the index suddenly became corrupt. It all started with this error message: :108250 is out of range [0..108183] for IndexWriter#[] /usr/local/lib/ruby/gems/1.8/gems/ferret-0.10.9/lib/ferret/index.rb:382:in `[]'' And after that every search resulted in this error: A IOError

Hi Dave, i just stumbled across a new error i haven''t seen before :) caught error inside loop: IO Error occured at <except.c>:93 in xraise Error occured in fs_store.c:264 - fs_new_output couldn''t create OutStream /var/www/localhost/rails/current/ script/backgroundrb/../../config/../db/ferret.index.production/ _jei_0.f0: <Too many open files> my ulimit is

Hi, after a long indexing run I got the following error. I have 149 MB space left on the disk, the index is 311 MB large; could Ferret have tried to use more than that for the optimizing? Or would that have resulted in a different error message? /usr/local/ruby-1.8.5/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/commands/runner.rb:27: