Logos Indexer has encountered a problem and needs to close.
I have had Logos 5 installed for some time now, and the indexer consistently crashed at 5% and has never completed. As a result, not only does the indexer runs every time I boot the machine significantly slowing the machine for 15-20 minutes until it crashes but I also get slim to no results from searches rendering my Logos virtually useless. I've search the forums and only come across one possible solution, which was to delete the index files in order to force a rebuild, but that hasn't helped at all. I'm running Logos 5 on a 64bit Windows 8 desktop PC.
Comments
-
Welcome Jeremy
The message in the log file is "BibleIndex Library indexing canceled, failed, or ran out of storage space; deleting temporary files". So you need to make more space available on the C:\ drive (at least 4GB). Delete temporary files, browser Temp files and empty recycle bin or get Cclean. Also remove restore points with the Windows Disk cleanup.
EDIT: another message shows an error in a reverse interlinear bible and that the indexer would restart. I can't determine if it is NIV2011 or NASB95, but you can try deleting these files from C:\Users\Jeremy\AppData\Local\Logos4\Data\1pytfo0k.4pk\ResourceManager\Resources:
- NIV2011NT.lbsrvi
- NIV2011OT.lbsrvi
- NIV2011.logos4
- NASBNT.lbsrvi
- NASBOT.lbsrvi
- NASB95.logos4
EDIT: Also include
- NIV.logos4
- NIVNT.lbsrvi
These should be redownloaded when Logos restarts & indexed.
Dave
===Windows 11 & Android 13
0 -
Hello Jeremy,
Dave is right about the error message in your log file, and the possible cause. But he might also have been right about running out of disk space. According to your error log you only have 1.6Gb free, which really isn't very much at all. During reindexing, Logos needs enough space to create a copy of your index, and I don't think 1.6Gb is enough for that.
So I'd be more likely to think that disk space is the issue, rather than corrupt download files, and would suggest you try the advice that Dave crossed out before anything else.
As to the indexing error - I would be more confident than David that it was caused during indexing the NIV.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
Thanks to both of you for your responses. I'll try deleting the files. I'm not sure why the log file says 1.6Gb free when i have 1.55Tb free. I know space is not the issue.
EDIT:
Deleted the files with no effect. Still crashing at 5%. I've read through the Log files, but other than a reference to "reverse interlineral" I don't see how you can tell what files might be corrupt. Could this be an upgrade from Logos 4 issue?
0 -
The log file indeed shows 1,783,016 MB free = 1.7 TB, so the issue is related to the reverse interlinear resources.
Dave
===Windows 11 & Android 13
0 -
Jeremy, is the indexing issue resolved?
Dave
===Windows 11 & Android 13
0 -
Dave, thanks for the follow-up, but no the issue remains unsolved. i tried deleting the the NIV and NASB files. They did redownload, but the indexer failed at 5% again. I may try deleting the files again, but allow the indexer to run "offline" before the files redownload. What was it about the logs that led you to believe it was the NIV or NASB books?
0 -
The error is directly related to reverse interlinear bibles, probably a mismatch between the OT/NT interlinear datasets and the bible, and these were being indexed at the time the error occurred.
I suggest you contact Logos Tech Support if your workaround is not satisfactory e.g. when you go back online the cycle will likely repeat.
Dave
===Windows 11 & Android 13
0 -
Jeremy Blanford said:
What was it about the logs that led you to believe it was the NIV or NASB books?
Indexing is a multi-threaded operation, so several books are indexed at the same time, one on each thread, with each thread using a different core of your processor.
The error says "Library indexing canceled, failed, or ran out of storage space; deleting temporary files.", but prior to that, each of the threads reported "No more resources to index; stopping thread." This doesn't appear to be true, because at the same time it also says "WindowsIndexerProgress 100 of 136 resources indexed". So the question is: "What is causing indexing to stop?". The NIV and NASB resources were the ones being indexed around the time of the problem, so it's natural to assume they caused the problem. That's apparently not the case.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
It's just possible the error was caused by the Logos LXX. That's also a reverse interlinear, and the log says it finishes indexing about the time there's a problem. If that's the case, the two files to delete are:
- LogosLXX.logos4
- LXXHEB.lbsrvi
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
Mark, Dave, thank you both for helping out. The issue seems to be resolved.
Solution: I went back through and deleted each of the above mentioned files including all NASB and NIV resources. Prior to launching Logos, I unplugged the network in order to ensure i remained off line and allowed the indexer to run and finally complete its task w/out the deleted files. I then re-plugged the machine and Logos downloaded the missing files and successfully re-indexed the new resources.
Again, I appreciate the support.
Jeremy
0 -
Good to hear.
Dave
===Windows 11 & Android 13
0
