5.1a SR-1: Indexer Crashes at 99% Complete

This has been happening for me for the last few beta releases. My indexer nearly completes and then crashes (windows tells me that Logos has encountered an error and whether I want to close it or look online for a solution to the problem).

I'm using Windows7.

Logs attached.0576.LogosIndexerError_ryanschatz.zip

Find more posts tagged with

Comments

Bradley Grainger (Logos)

It looks like the indexer is failing at the very last step of merging indexes. The easiest way to fix it (although it will require a complete reindex) is simply to wipe out the existing index by deleting this folder:

C:\Users\schatzr\AppData\Local\Logos4\Data\ujcnlvdh.qnv\LibraryIndex

BTW, I noticed that you have at least one resource collection with the rule "title:*". You'll see a speed improvement in Logos 5 if you change the rule to just "*" (without quotes).

Ryan Schatz

It looks like the indexer is failing at the very last step of merging indexes. The easiest way to fix it (although it will require a complete reindex) is simply to wipe out the existing index by deleting this folder:

C:\Users\schatzr\AppData\Local\Logos4\Data\ujcnlvdh.qnv\LibraryIndex

Ok, thanks... I'm reindexing now.

BTW, I noticed that you have at least one resource collection with the rule "title:*". You'll see a speed improvement in Logos 5 if you change the rule to just "*" (without quotes).

Hmm... but this seems to change my results. For instance, I have a collection which is:

type:commentary AND (title:john OR subject:john) ANDNOT (subject:"1 John","2 John","3 John","John, 1st","John, 2nd","John, 3rd",epistles-of-john)

This produces 78 matching results.

If I replace it with the following, I get 489 matching results:

type:commentary AND (john OR subject:john) ANDNOT (subject:"1 John","2 John","3 John","John, 1st","John, 2nd","John, 3rd",epistles-of-john)

Am I misunderstanding you?

Thanks,

Ryan

JT (alabama24)

Am I misunderstanding you?

I think he is talking about a rule with the wildcard (*). Using a rule of title:* will reveal all resources with a title (in other words, your entire collection). Using a rule of just * will do the same thing, but be more efficient… At least, that is what I understood him to be saying. [:)]

Ryan Schatz

Ah, I see it now. Got it.... thanks!

NB.Mick

Am I misunderstanding you?

I think he is talking about a rule with the wildcard (*). Using a rule of title:* will reveal all resources with a title (in other words, your entire collection). Using a rule of just * will do the same thing, but be more efficient… At least, that is what I understood him to be saying.

and unless Logos have implemented a new feature in search evaluation which detects * and resolves the whole library without taking much time (just tested, seems not to be the case), using a rule like rating:<6 is much faster than both.