Displaying 20 results from an estimated 800 matches similar to: "Problem with large index file"
2007 Jan 18
5
corrupt index immediately after rebuild
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
2013 Apr 16
2
An error occurred while installing jk-ferret (0.11.8.3), and Bundler cannot continue.
*Hi guys..
i got this type of error when i configured Gemfile
then what to do?*
gem "thinking-sphinx"
gem ''ferret''
Updating git://github.com/mark-moseley/linecache
Fetching gem metadata from https://rubygems.org/.......
Fetching gem metadata from https://rubygems.org/..
Resolving dependencies...
Using rake (10.0.3)
Using ClothRed (0.4.1)
Using RedCloth (4.2.9)
2006 Sep 22
4
IOError on clearing locks
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
2006 Oct 12
3
IO Error occured at <except.c>:79 in xraise (IOError)
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:
2007 Apr 14
3
Error on optimize leads to corrupt index?
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
2007 Mar 12
2
Too many open files error
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
2006 Aug 26
4
[0.10.0] Index#add_document bug with strange value ?
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
2007 Mar 29
2
Nasty looking warnings on Debian Etch AMD64 bit box
Running gem install ferret and selecting 0.11.3 on a Dual Xeon or Dual Opteron 64 bit box running Debian Etch gives the following list of nasty looking warnings, anyone running successfully on 64 bit linux?
Building native extensions. This could take a while...
fs_store.c: In function ?fso_seek_i?:
fs_store.c:238: warning: format ?%lld? expects type ?long long int?, but argument 4 has type
2005 Nov 30
8
Compilation of ferret C-extension under Windows.
Hi, David.
I have recently fixed ferret C sources and successfully compile extension
with MSVC.Net The problem was that MS compiler is more stricter that GCC and
require that all variables were declared before using. There was ~30 such
declaration. I have fixed them all.
But I am not sure that it works because tests failed with following error
both on clean and patched versions. So seems that it
2005 Dec 19
17
Indexing so slow......
I am indexing over 10,000 rows of data, it is very slow when it is
indexing the 100,1000,10000 row, and now it is over 1 hour passed on
the row 10,000.
how to make it faster?
here is my code:
==================
doc = Document.new
doc << Field.new("id", t.id, Field::Store::YES,
Field::Index::UNTOKENIZED)
doc << Field.new("title", t.title,
2007 Jun 24
4
IO Error when querying on a single field
I''m getting an exception when I query a large index (4GB, ~700K docs)
on a particular field.
For example:
supplier_id:77490
IO Error occured at <except.c>:93 in xraise (IOError)
Error occured in fs_store.c:293 - fsi_seek_i
seeking pos -1515676213: <Invalid argument>
Anecdotally it seems to happen for supplier_ids > 76900.
Here is the field info for that
2007 Mar 13
6
Acts_as_ferret and auto-flush
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
2006 Jun 02
1
Indexing fails -- _ntc6.tmp exceeds 2 gigabyte maximum
Ferret 0.9.3
Ruby 1.8.2
NOT storing file contents in the index.
Only indexing first 25k of each file.
Very large data set (1 million files, 350 Gb)
Code based on snippet from David Balmain''s forum posts.
After 6 hours, Ferret bails out with Ruby "exceeds max file size".
Cache:
-rw-r--r-- 1 bill bill 2147483647 2006-06-01 22:45 _ntc6.tmp
-rw-r--r-- 1 bill bill 1690862924
2006 Nov 24
2
Strange error. Index corrupt on production server
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
2007 Mar 28
7
Newbie problem on production server
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",
2007 Apr 07
19
Constant 0.11.4 Errors
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
2013 Apr 16
1
An error occurred while installing jk-ferret (0.11.8.3), and Bundler cannot continue.
*Hi guys..
i got this type of error when i configured Gemfile
then what to do?*
gem "thinking-sphinx"
gem ''ferret''
Updating git://github.com/mark-moseley/linecache
Fetching gem metadata from https://rubygems.org/.......
Fetching gem metadata from https://rubygems.org/..
Resolving dependencies...
Using rake (10.0.3)
Using ClothRed (0.4.1)
Using RedCloth (4.2.9)
2006 Oct 31
3
No search results using Searcher
I just started using Ferret and I successfully indexed some documents. I
can search this index using the following code:
index = Index::Index.new(:path => path)
index.search_each("something") do |doc, score|
print "##{doc} #{index[doc][''url'']} - #{score}"
print "\n"
end
However, when I try to use Search::Searcher and QueryParser
2007 Jan 21
14
[ActsAsFerret] OpenSolaris (TextDrive) indexing issues
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
2006 Aug 04
5
A couple of ferret 0.9.4 exceptions
Hi Dave,
I am using ferret at my site http://gifthat.com and I just had a few
exceptions pop up. I don''t have a way to reproduce them, but my site
just was listed on lifehacker.com and these issues have popped up
under multiple concurrent users (only twice though which I think isn''t
too bad). I am using two lighttpd instances both with read/write
access to the index:
1) Error