Indexer Crash

I am getting an indexing crash which show as follows in the log file:

Error ID: 6143

Error detail: CorruptIndexException: Document ID is out of range.

I tried deleting the LibraryIndex folder, but got the same error (and now no index!)

I did note several metadata warnings in the logos.log file along the lines of:

2018-12-01 08:31:14.6196 5 Warn MetadataServiceUtility Invalid ResourceId (LLS:12.40.1031), Version (2015-05-15T22:35:51Z), or ResourceType (); rejecting metadata record.

Find more posts tagged with

Desktop App

Comments

Jeffrey S Gordon

It looks like the problem happens when trying to merge supplemental index with full index (at least that's my guess). I have a second machine that has the same issue. It puts out somewhat more in the log (listing various resources as it goes through them), and showed more of a progress when indexing (probably because it was more resources to download on that machine). But then it dies trying to merge this set into full index. I tested some "all resources" searches and they indeed do not find anything in newer resources.

This seems to have been happening for a while (since Sept/Oct?), probably prior to Logos 8, and I only noticed it by looking at log files.

It there any way to enable more detailed logging to track down which "Document ID is out of range"?

Jeffrey S Gordon

https://community.logos.com/discussion/comment/1017957#Comment_1017957

Just in case, these are log files (from second machine)...

8228.Logos Log Files.zip

Dave Hooton

https://community.logos.com/discussion/comment/1017968#Comment_1017968

Make sure Logos is not running and delete the Bible Index folder: C:\Users\jeff.LAPTOP-56VRLC4L\AppData\Local\Logos\Data\sujgsm0j.w3o\BibleIndex. Indexing should start when you restart Logos.

Jeffrey S Gordon

https://community.logos.com/discussion/comment/1017991#Comment_1017991

This did change but not fix the behavior. It no longer crashes. But now it indexes for quite some time without finishing (building LibraryIndex, BibleIndex seems to have rebuilt OK). It does complete without logging any errors. If I restart Logos, it starts indexing from 0 again. In looking at the log, it seems this time the indexer is just exiting without an error message (maybe a segv?). I don't know how to debug it, but it did just quit running. I was watching it with resource monitor and it had many files simultaneously open to read but only the two in LibraryIndex folder to write (one was logging 500Mb/s writing, but never showed more directory size than 2Mb).

By the way, this is my original machine, which is described below. I'll try the same operation (deleting BibleIndex folder) on the other machine.

I attached some screen shots and Logos logs.

4075.Logos Log Files.zip

System Model XPS 15 9570
Processor Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz, 2904 Mhz, 6 Core(s), 12 Logical Processor(s)
Installed Physical Memory (RAM) 32.0 GB

Drive C:
Description Local Fixed Disk
Compressed No
File System NTFS
Size 1.85 TB (2,032,689,778,688 bytes)
Free Space 1.62 TB (1,777,853,145,088 bytes)

Jeffrey S Gordon

https://community.logos.com/discussion/comment/1018047#Comment_1018047

I did find some windows description of the crash, not really a crash or core dump, but maybe (barely) better than nothing.

0284.AppCrash_LogosIndexer.exe.zip

Jeffrey S Gordon

https://community.logos.com/discussion/comment/1018053#Comment_1018053

This isn't good. I notice that without an index, even searching in an open resource for a text I see on the page returns no results!

MJ. Smith

https://community.logos.com/discussion/comment/1018054#Comment_1018054

The index is specifically used for searching so you'll get no results until it is rebuilt. You need to give the machine time to rebuild the index - how long? that depends upon your hardware, the free space on disk, the resources you own ... I'll try looking at the dumps ...

Dave Hooton

https://community.logos.com/discussion/comment/1018053#Comment_1018053

I did find some windows description of the crash, not really a crash or core dump, but maybe (barely) better than nothing.

[View:https://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/147/0284.AppCrash_5F00_LogosIndexer.exe.zip:550:0

Please follow these instructions to provide readable information from the Event Viewer

Anthony Grubb

https://community.logos.com/discussion/comment/1018058#Comment_1018058

you'll get no results until it is rebuilt.

It's been my understanding that we get limited results until it indexes...unless we are talking about the existing index file being destroyed, I guess that makes sense. Changing gears; I've been financially strapped for years and have not updated my computer (although, when I see how much I have invested in Logos over that time... lol), and so I have been limited to Logos 5 for a much older Windows. Not so obtuse as to request assistance on that older platform, but found this thread in a search after my indexer quit working a week ago and was searching the forums to see if others mentioned similar problems. Planning to wipe the machine and reinstall soon, anyway. Just leaving this here if anyone else has the same issue.

EDIT: After seeing much discussion here about Log Dumps, happened to be in my Documents folder and saw "Logos Log Files" folder. The developers have apparently discontinued the parts of the Logos website that were responding to the Logos 5 indexer, now that Logos 8 is up and running. Redirect to Logos 5 Forum Topic: https://community.logos.com/forums/p/176284/1018148.aspx

Mike Binks

https://community.logos.com/discussion/comment/1018137#Comment_1018137

Anthony

I note that you have been using Logos 5.

You might like to see how the semi-equivalent edition of Logos 8 which runs on the Web works for you.

Anthony Grubb

https://community.logos.com/discussion/comment/1018160#Comment_1018160

You might like to see how the semi-equivalent edition of Logos 8 which runs on the Web works for you.

Thank you, let's not hijack the thread, and to fix the link you provided; I've had limited success with it that, just tried its Bible Search feature and pretty sure the one on my Logos works better for the moment, thank you!

Jeffrey S Gordon

https://community.logos.com/discussion/comment/1018120#Comment_1018120

Dave,

I already sent (in zip file with Logos logs) the .wer (Windows Error Report) which has a lot more detail than the General tab of Event Viewer. So I attached another file (not zipped, not that big) which has event details per those instructions plus some more. I believe that the issue is indeed a memory access violation.

One interesting thing is that I was able to get my second machine fixed. On that one, I had never deleted the LibraryIndex folder. So I tried deleting ONLY the BibleIndex folder, and what do you know, it indexed and completed. I thought maybe I could copy the index from that machine to my main machine but it didn't work. I might try a complete reinstall (the resources are the same on both machines), but I don't believe I will be able to completely rebuild the index from scratch (it will just die again, it's been tried several times). I'll probably try the copy/reinstall, but it would be good if there were some way to avoid reindexing (i.e., copying the right files from the working machine).

8561.Event Log Info 20181201.txt

MJ. Smith

https://community.logos.com/discussion/comment/1018270#Comment_1018270

Indexes are always installation specific, sorry.

Jeffrey S Gordon

https://community.logos.com/discussion/comment/1018270#Comment_1018270

Actually, this did seem to work (it only failed before because my copy was truncated by a full usb drive):

(1) copy the working LibraryIndex folder from the second machine

(2) delete the BibleIndex folder

(3) Start logos and let it index.

It finished, logs look OK, and searches for texts in newer resources are working. It seems like, whatever caused the original error ("CorruptIndexException: Document ID is out of range") was fixed by deleting the BibleIndex folder and re-indexing. However, it also seems like (for me at least, based on resources, current versions, etc.) I can NOT delete the LibraryIndex folder, or use the "rebuild index" command, lest I encounter this more serious error. So that remains a problem.

At least for now my installation seems to be working. Is there any way to actually test the index as to whether it's consistent with resources? It's hard to know whether searches are missing anything when they return some results.

Dave Hooton

https://community.logos.com/discussion/comment/1018284#Comment_1018284

Is there any way to actually test the index as to whether it's consistent with resources? It's hard to know whether searches are missing anything when they return some results.

Basic Search for the in type:monograph. Type the latter in the Resource box and it will tell you how many resources there are. You should get results from that number of resources.