search for: xraise

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 `close'' /usr/local/lib/ruby/site_ruby/1.8/ferret/index.rb:517:in `flush'' /usr/local/lib/ruby/1.8/monitor.rb:229:in `synchronize'' /usr/...

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 to optimize. Ferret::Index::IndexReader.new("indexes/my_index_dir") IOError: IO Error oc...

...g? 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: /usr/local/ruby-1.8.5/lib/ruby/gems/1.8/gems/ferret-0.10.11/lib/ferret/index.rb:536:in `optimize'': IO Error occured at <except.c>:79 in xraise (IOError) Error occured in fs_store.c:226 - fso_flush_i flushing src of length 1024 from /usr/local/ruby-1.8.5/lib/ruby/gems/1.8/gems/ferret-0.10.11/lib/ferret/index.rb:536:in `optimize'' from /usr/local/ruby-1.8.5/lib/ruby/1.8/monitor.rb:238:in `synchronize'...

....rb. I ran 3 three times my script (I deleted my index every time before), and only the third was successful. That was STRANGE ! :) These are the errors : /usr/lib/ruby/gems/1.8/gems/ferret-0.10.0/lib/ferret/index.rb:204:in `commit'': End-of-File Error occured at <except.c>:79 in xraise (EOFError) Error occured in store.c:197 - is_refill current pos = 117, file length = 68 from /usr/lib/ruby/gems/1.8/gems/ferret-0.10.0/lib/ferret/index.rb:204:in `<<'' from /usr/lib/ruby/1.8/monitor.rb:229:in `synchronize'' from /usr/lib/ruby/gems/1.8/gems/f...

...3f2dc7c17147c0e52178ba697a119833 Parameters: {"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 `...

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 set to 1024 files, the error occurs regularly.. any id...

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. -- Florent -- Posted via http://www.ruby-forum.com/.

...reation 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 Error occured in fs_store.c:289 - fsi_seek_i seeking pos -1206037603: <Invalid argument> As you can see it is seeking on a negative position. I did a strace on this with the following results: _llseek(3, 18446744072766697140, 0xbfc555e0, SEEK_SET) = -1 EINVAL (Invalid argument) rt_s...

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 /usr/lib/ruby/site_ruby/1.8/ferret/index.rb:211:in `<<'' from /usr/lib/ruby/1.8/monitor.rb:229:in `synchronize'' from /usr/lib/ruby/site_ruby/1.8/ferret/inde...

...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 occured at <except.c>:79 in xraise Error occured in fs_store.c:146 - fs_clear_locks clearing locks in persistence_path/00000000001: <No such file or directory> The persistence_path/ directory is the one that was File.rm_r''d. How can I stop this from happening? Is it a bug, or have I messed something up?...

...his 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 occurred in search#rss: IO Error occured at <except.c>:79 in xraise Error occured in fs_store.c:323 - fs_open_input couldn''t create InStream /home/newsdesk_prod/current/config/../index/production/pressrelease/_2tap.fdt: <No such file or directory> /usr/local/lib/ruby/gems/1.8/gems/ferret-0.10.9/lib/ferret/index.rb:679:in `initialize'&...

...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/ gems/rdig-0.3.4/lib/rdig/index.rb:48: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 from /mnt/apps/search/releases/20070622175637/script/../ config/../vendor/gems/rdig-0.3.4/lib/rdig/index.rb:48:in `close'' from /mnt/apps/search/releases/20070622175637/script/....

I''m hoping someone has encountered this before. I''m using AAF trunk and trying to multi_search across 2 models. It works fine on my windows (Webricks) dev env but now that i''ve deployed to linux, (Apache, FastCGI) I''m getting the following error: ArgumentError ( isn''t a valid directory argument. You should use either a String or a Directory):

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

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

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

..._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: /usr/lib/ruby/gems/1.8/gems/ferret-0.11.3/lib/ferret/index.rb:542:in `close'': 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 from /usr/lib/ruby/gems/1.8/gems/ferret-0.11.3/lib/ferret/index.rb:542:in `flush'' from /usr/lib/ruby/1.8/monitor.rb:229:in `synchronize'' from /usr/lib/ruby/gems/1....

Hello, I''m usin gferret and I''ve just attempted to build an index that contains 15,968,046 documents. I''ve rebuild the index from scratch, but when I try to search for some items I get this error: IOError: IO Error occured at <except.c>:79 in xraise Error occured in fs_store.c:289 - fsi_seek_i seeking pos -1284143798: <Invalid argument> This is happening when I''m trying to look up a document with id 13,677,803. Interestingly, any document after id 12,098,067 seems to trigger the error. Any ideas? Thanks! -Mike -- P...

...uby/gems/1.8/gems/ferret-0.10.8/lib/ferret/index.rb:382:in `[]'' /usr/lib/ruby/1.8/monitor.rb:229:in `synchronize'' /usr/lib/ruby/gems/1.8/gems/ferret-0.10.8/lib/ferret/index.rb:375:in `[]'' ... Ferret::StateError (State Error occured at <except.c>:79 in xraise Error occured in index.c:3404 - sr_get_lazy_doc Document 0 has already been deleted ): /usr/lib/ruby/gems/1.8/gems/ferret-0.10.8/lib/ferret/index.rb:382:in `[]'' /usr/lib/ruby/gems/1.8/gems/ferret-0.10.8/lib/ferret/index.rb:382:in `[]'' /usr/lib/ruby/1.8/monitor.rb:...

...rret or a bug I should report. I''m currently running Ferret 0.10.11 with acts_as_ferret (latest via svn external) and 3 times today I''ve seen the following error in production: A Ferret::StateError occurred in directory#search: State Error occurred at <except.c>:79 in xraise Error occurred in index.c:2098 - stde_doc_num Illegal state of TermDocEnum. You must call #next before you call #doc_num /usr/local/lib/ruby/gems/1.8/gems/ferret-0.10.11/lib/ferret/index.rb:370:in `search.each'' The index in question is on a single model and contains about 330K...