search for: sis_find_segments_file

...rameters: {"commit"=>"Search", "action"=>"results", "controller"=>"links", "link"=>{"search"=>"test"}} IOError (IO Error occured at <except.c>:93 in xraise Error occured in index.c:886 - sis_find_segments_file Error reading the segment infos. Store listing was ): /usr/local/lib/ruby/gems/1.8/gems/ferret-0.11.3/lib/ferret/index.rb:706:in `initialize'' /usr/local/lib/ruby/gems/1.8/gems/ferret-0.11.3/lib/ferret/index.rb:706:in `new'' /usr/local/lib/ruby/gems/1.8/gems/fe...

...} I''ve run a similar script before with no issues. However today I received the following error after 30 minutes or so: /usr/lib/ruby/site_ruby/1.8/ferret/index.rb:726:in `initialize'': IO Error occured at <except.c>:93 in xraise (IOError) Error occured in index.c:901 - sis_find_segments_file Error reading the segment infos. Store listing was from /usr/lib/ruby/site_ruby/1.8/ferret/index.rb:726:in `ensure_reader_open'' from /usr/lib/ruby/site_ruby/1.8/ferret/index.rb:434:in `delete'' from /usr/lib/ruby/site_ruby/1.8/ferret/index....

....4. After they see this, the index is not recoverable and they have to rebuild from scratch. Any ideas? --- cut here --- /var/lib/gems/1.8/gems/ferret-0.11.4/lib/ferret/index.rb:726:in `initialize'': IO Error occured at <except.c>:93 in xraise (IOError) Error occured in index.c:901 - sis_find_segments_file Error reading the segment infos. Store listing was from /var/lib/gems/1.8/gems/ferret-0.11.4/lib/ferret/index.rb:726:in `new'' from /var/lib/gems/1.8/gems/ferret-0.11.4/lib/ferret/index.rb:726:in `ensure_reader_open'' from /var/lib/gems/1.8/gems/fer...

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

...e RDig just to index using urls, no files. Both use acts_as_ferret for an administrative search that works fine. On the Windows machine, I get no errors, but get no results. On the Linux machine, I get: File Not Found Error occured at <except.c>:93 in xraise Error occured in index.c:840 - sis_find_segments_file couldn''t find segments file On both machines I have run the indexer with no errors using: rdig -c config/rdig_config.rb Both machines have an index dir at the rails root that has two files, segments and segments_0. Both files look like they have next to nothing in them. Both rdig_conf...

...ors. when the searching process is running and I start the indexing process, I immediately get: /usr/lib/ruby/gems/1.8/gems/ferret-0.11.3/lib/ferret/index.rb:692:in `latest?'': File Not Found Error occured at <except.c>:93 in xraise (FileNotFoundError) Error occured in index.c:825 - sis_find_segments_file couldn''t find segments file from /usr/lib/ruby/gems/1.8/gems/ferret-0.11.3/lib/ferret/index.rb:692:in `ensure_reader_open'' from /usr/lib/ruby/gems/1.8/gems/ferret-0.11.3/lib/ferret/index.rb:713:in `ensure_searcher_open'' from /usr/lib/ruby/...

...ess crashes after a few (generally fewer than 100) queries, in one of at least two different ways selected apparently at random: Failure Mode #1: script/ferret_speedtest2_reader:30:in `initialize'': IO Error occured at <except.c>:93 in xraise (IOError) Error occured in index.c:901 - sis_find_segments_file Error reading the segment infos. Store listing was from script/ferret_speedtest2_reader:30:in `new'' from script/ferret_speedtest2_reader:30:in `run_test_query'' [Yes, there really are two blank lines after "Store listing was".] Failure Mode #2: script/ferret_speedt...