Jim Kane wrote: > David Balmain wrote: >> On 10/13/06, Jim Kane <[EMAIL PROTECTED]> wrote: >>> Error occurred in index.c:2098 - stde_doc_num >>> to find_by_contents sorted by a timestamp (stored nontokenized). Can >>> anyone offer some advice on what I might be doing to cause this? I'm >>> also getting occasional segfaults (already submitted as a ticket on the >>> trac) but they don't _appear_ to be tied to this error. >>> >>> Jim >> >> Hi Jim, >> I'm not sure what might be causing this error. Did you reindex when >> you upgraded to 0.10.11? That may help. If it doesn't, try going back >> to version 0.10.9. This error may have been introduced in the >> performance enhancements I added in version 0.10.10. >> >> Let me know how you go. > I tried reindexing with 0.10.11 but this didn't seem to help matters > (and it REALLY barfed while the reindex was going on). I downgraded to > 0.10.9 and reindexed this morning; since the reindex finished, I haven't > had a single segfault or StateError (previously I had plenty of both). Alright, I was going to add this to the open trac ticket I have regarding segfaults but akismet appears to be in a bad mood today. My earlier observations were based on a static index, which is great and all, but I do need to update it throughout the day. I restarted the update process and within an hour I encountered 2 segfaults. I'm not sure where to go from here.
Jim -- Posted via http://www.ruby-forum.com/. _______________________________________________ Ferret-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/ferret-talk
