similar to: Acts_as_ferret and auto-flush

Hi, we are using ferret and acts_as_ferret in a single server setup. We have 2 models that use acts_as_ferret. We are running into problems where a create or update of the models cause a ferret error Ferret::FileNotFoundError occured at <except.c>:117 in xpop_context Error occured in fs_store.c:329 - fs_open_input Where the file that needs to be opened isn''t there. The error

Folks, Since upgrading to ferret 0.11.4 on Mac OS X Tiger, I''ve been running into constant crashes when running my Rails tests. Here''s an example of the output. -- snip -- 1) Error: test_published_blog_can_be_ferreted(BlogTest): Ferret::FileNotFoundError: File Not Found Error occured at <except.c>:117 in xpop_context Error occured in fs_store.c:329 - fs_open_input

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, I saw someone else have this earlier. The recommendation is still to downgrade to 0.11.3? Oct 01 19:56:09 ey01-s00116 rails[3175]: Ferret::FileNotFoundError (File Not Found Error occured at <except.c>:117 in xpop_contextError occured in fs_store .c:329 - fs_open_input tried to open "/data/zendesk/current/config/../index/production/ticket/_l.cfs" but it

Hi, I have a model that I''ve been indexing and searching with ferret some problem. We get the following error when accessing the model File Not Found Error occured at <except.c>:117 in xpop_context Error occured in fs_store.c:329 - fs_open_input tried to open "/var/www/html/cuproject/index/development/album/_b.cfs" but it doesn''t exist: <No such file or

Hey folks, Sorry for cross posting like this but this is an important announcement for all Ferret users. ** Description ** Firstly for those who don''t know, Ferret is a full-text search library which makes adding search to your application a breeze. It''s much faster than MySQL full-text search as well most other search libraries out there. It allows you to do Boolean (+ruby +

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 I use Ferret 0.11.4 and the latest stabel version of the acts_as_ferret plugin. To the issue. if I do Model.rebuild_index and after that try to update one of my objects of that Model I get: File Not Found Error occured at <except.c>:117 in xpop_context Error occured in fs_store.c:329 - fs_open_input tried to open

Hi, I noticed a 0.11.3 release and gave it a whirl. I''ve so far not been able to reproduce any segfaults with my ferret_killer[1] script, though I do get some errors. 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

Gents, I successfully installed AAF on my TextDrive OpenSolaris Container, but I''m having some issues with indexing. I have a model called Blogs which has AAF enabled. The first time I tried to find_by_contents for a ''word'' I know was on the Database I got now results. Apparently the index was not ready yet. Then I waited a few hours and checked that the /index

Hi All, I''m using acts as ferret and getting a lot of these errors: ---- Error occured in fs_store.c:324 - fs_open_input couldn''t create InStream /var/rails/projectblue/website/public/../config/../index/production/content_page/_347i.fdt: <No such file or directory> ---- and also some of these errors: ---- uninitialized constant Ferret::Index::Index::LockError

Hi all, I''ve got a slight problem with using Ferret in unit tests. In order to create as little cross-contamination between test suites as possible, some of my tests are creating a fresh index per test case, and then calling Index#close and deleting the containing dir during the teardown. The problem comes when GC.start kicks in after the deleting the directory: IOError: IO Error

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

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

Hello, Ferret created a 4.5GB> index file. $ 4534029210 2007-02-26 12:46 _el.cfs The creation of the index went smoothly. Searching through this index also works fine. However whenever I try to get the contents of an indexed document I get an error when the document number is above 621108: irb(main):080:0> searcher[621108].load IOError: IO Error occured at <except.c>:79 in xraise

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

Hi all, I upgraded from Ferret 0.11.3 to Ferret 0.11.4 because I was getting intermittent segfaults that seemed to be due to a bug which was fixed (changeset 749). Unfortunately, 0.11.4 + acts_as_ferret seems to be a bad combination. I''m getting the some "fs_store/File Not Found Error occured at <except.c>:117" which was reported in the "Constant 0.11.4

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:

We have still having problems with Ferret dying on us regularly with the error message: >> ferret server error IO Error occured at <except.c>:93 in xraiseError occured in fs_store.c:127 - fs_each doing ''each'' in /var/www/web1/oms/current/script/../config/../index/production/band/20070805130005: <Too many open files> << We are running Ferret as a

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