L4.2a Indexer Crashes

With just over 3,000 resources, I consider myself quite fortunate to have had no problems since installing L4 in late 2009. However, with the new L4.2a, I am now getting indexer stopped working Windows error message. Here is the last few lines from the indexer log file. Both the indexer log file and the crash reports are also posted. Can someone give me an idea of what I need to do to get my normally wonderful Logos back to working order? Thx!!!

2011-03-02 20:07:13.7080 8 Info BibleIndex Finished indexing resources (in 04:02:58.5520859); writing postings.

2011-03-02 20:18:22.1313 1 Info WindowsIndexerProgram Setting notification icon tool tip to: Logos Bible Software is indexing (6% complete)

2011-03-02 20:41:07.7904 1 Info WindowsIndexerProgram Setting notification icon tool tip to: Logos Bible Software is indexing (7% complete)

2011-03-02 20:41:31.6117 8 Info BibleIndex (Timed) Attempting to replace index 'C:\Users\Bruce\AppData\Local\Logos4\Data\cbeykvea.dyh\BibleIndex/supplemental' with new index 'C:\Users\Bruce\AppData\Local\Logos4\Data\cbeykvea.dyh\BibleIndex/supplemental-build'.

2011-03-02 20:41:31.6447 8 Info FileSystemIndexInfo Replacing C:\Users\Bruce\AppData\Local\Logos4\Data\cbeykvea.dyh\BibleIndex/supplemental with C:\Users\Bruce\AppData\Local\Logos4\Data\cbeykvea.dyh\BibleIndex/supplemental-build

2011-03-02 20:41:31.9498 8 Info BibleIndex (327ms) Attempting to replace index 'C:\Users\Bruce\AppData\Local\Logos4\Data\cbeykvea.dyh\BibleIndex/supplemental' with new index 'C:\Users\Bruce\AppData\Local\Logos4\Data\cbeykvea.dyh\BibleIndex/supplemental-build'.

2011-03-02 20:41:32.4938 8 Info BibleIndex Library indexing completed in 04:37:17.3377924.

2011-03-02 20:41:32.4998 8 Info BibleIndex Merging supplemental index into main index.

2011-03-02 20:41:32.4998 8 Info BibleIndex Merging indexes 'index' and 'supplemental' into index in C:\Users\Bruce\AppData\Local\Logos4\Data\cbeykvea.dyh\BibleIndex

2011-03-02 20:41:32.9538 8 Error WindowsIndexerProgram Unhandled exception: System.InvalidOperationException: Unable to merge non-skiplist index with skiplist index.

at Libronix.SearchEngine.Indexer.MergeIndexes(FileSystemIndexInfo infoToMergeLeft, FileSystemIndexInfo infoToMergeRight, IWorkState state, IIndexerProgress progress, ICollection`1 allDocumentIdsInRight, Func`1 fnIsInsufficientDiskSpace)

at Libronix.DigitalLibrary.LibraryIndex.MergeIndexes(ILibraryIndexWorkState state, String strBigIndexName, String strSmallIndexName, String strNewIndexName)

at Libronix.DigitalLibrary.LibraryIndex.IndexResources(IPausableWorkState threadOwnerWorkState, LibraryIndexWorkState state)

at Libronix.Utility.Threading.WorkStateThreadOwner`1.ThreadProc(Object objData)

at System.Threading.ThreadHelper.ThreadStart_Context(Object state)

at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

at System.Threading.ThreadHelper.ThreadStart(Object obj)5428.Logos4Indexer.log 4477.Logos4IndexerCrash.txt

Find more posts tagged with

Comments

Bradley Grainger (Logos)

The indexer needs to rebuild both your indexes, but isn't clearing out some out data properly, which is causing the crash. You should be able to "reset" it by running Logos 4, then entering the following command in the command box (at the top). You won't be able to search until it completes:

rebuild indexes

TCBlack

https://community.logos.com/discussion/comment/226307#Comment_226307

rebuild indexes

rebuild index

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/226402#Comment_226402

rebuild indexes
rebuild index

It will accept either "spelling", but that command will rebuild both indexes (Bible and Library), so I felt I should use the plural. [:)]

Dave Hooton

https://community.logos.com/discussion/comment/226638#Comment_226638

It will accept either "spelling"

Yes, rebuild indexz also works[H]

Milford Charles Murray

https://community.logos.com/discussion/comment/226645#Comment_226645

Great Humour, Dave!

*smile*

Peace!

TCBlack

https://community.logos.com/discussion/comment/226638#Comment_226638

My correction stands corrected. We could have a lot of fun taking this one down a spiraling path.

MJ. Smith

https://community.logos.com/discussion/comment/226638#Comment_226638

It will accept either "spelling", but that command will rebuild both indexes (Bible and Library), so I felt I should use the plural.

Isn't that "indices"?[:P]

Bruce

https://community.logos.com/discussion/comment/226900#Comment_226900

Gentlemen: Thank you for both the technical assistance and the light-hearted humor. Both are appreciated when working through software issues! [:)]

As a way of providing a bit of feedback/ closure to this, I provide the following update along with a question.

It appears that SR-1 to 4.2a was the solution to the indexing failure I experienced.

· Starting Logos again, indexing failed.

· I had read other threads indicating that SR-1 might solve indexing issues.

· Allowed Logos to download and install SR-1

· Indexing started upon Logos restart

· Indexing appears to have successfully completed in about 18 hours; (I did not try the rebuild index command as I wanted to see if the SR-1 solved the problem on its own).

Question: I note in the index log there are quite a number of items in which indexing could not be completed. It appears that some have to do with Galaxie Software items (GC?) and others I do not recognize. As there seem to be a significant number of these “Can't load article” warnings, wouldn’t a search fail to include these resources? Is there a way to include these in the indexing or are these resources not that critical? Log is posted for info. Thx again!!

5344.Logos4Indexer.log

Dave Hooton

https://community.logos.com/discussion/comment/226969#Comment_226969

Bruce,

Thanks for putting up with our humour and for solving the issue with SR-1.

Many articles in my resources eg. Bible Knowledge Commentary, Believer's Bible Commentary (especially) cannot be loaded, but I have not noticed the lack thereof - mainly because I do not read them from cover to cover. They have to be fixed in the resource and whilst Logos would be aware of these "typos" there is no indication that they will be fixed.