Jens, answering your questions: 1. Yes, it took a few hours from the start of the rebuild_index and the failure.
2. I don't think that any other process is modifying the index folder, but I'll try your suggestion. Cleaning the index folder and running rebuild_index again. Thanks for the attention. Jens Kraemer wrote: > On Sun, Jan 21, 2007 at 09:32:25PM +0100, Manoel Lemos wrote: >> receiving no changes, so the indexing was not happening also. >> >> Then I tried to re-index and I got the following error after a few hours >> of work: > > does this mean it took a few hours for rebuilding the index, or did you > only start the rebuild after a few hours? > >> >> Blog.rebuild_index >> >> IOError: IO Error occured at <except.c>:79 in xraise >> Error occured in fs_store.c:324 - fs_open_input >> couldn't create InStream >> script/../config/../config/../index/production/blog/_73j.fdx: <No such >> file or directory> > > strange. This does really look like the index has been modified by > something else while the rebuild was running. Could you try to start > over with a new, empty index directory? > > Jens > > -- > webit! Gesellschaft f�r neue Medien mbH www.webit.de > Dipl.-Wirtschaftsingenieur Jens Kr�mer [EMAIL PROTECTED] > Schnorrstra�e 76 Tel +49 351 46766 0 > D-01069 Dresden Fax +49 351 46766 66 -- Posted via http://www.ruby-forum.com/. _______________________________________________ Ferret-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/ferret-talk
