Indexer Needs Rebuilding
Why am I having to rebuild my index? The picture shows that it updated twice in addition to updating to Beta 3. Just performed a full reindex last week.
Are there any plans to correct this issue?
Mission: To serve God as He desires.
Comments
-
Lynden Williams said:
Why am I having to rebuild my index?
There were multiple corruption errors logged while trying to build a supplemental index (of your new/updated books) to merge into your existing index, so the Indexer decided to reindex everything.
This seems unnecessary in this case; we should just be rebuilding the supplemental index from scratch. Thanks for posting these logs; I think we can improve this in the next beta.
0 -
Thanks Bradley. While you are at it, can there be some sort of popup explaining that the software needs to bebuild its index.
I was wondering why it was taking so long to index a couple of books no more than a few MBs.
Mission: To serve God as He desires.
0 -
Any idea when this will be fixed? I downloaded a resource, Logos started to index, then it downloaded a 13.8 MB. I thought it had finished indexing, before installing the next update (what ever it is) and Logos is now rebuilding my index from scratch.
Mission: To serve God as He desires.
0 -
I am experiencing the same issue since updating to 5.2 RC1. I downloaded 3 resources and it is indexing showing a first time index. I hope this matter is resolved soon!
0 -
Bump
Mission: To serve God as He desires.
0 -
0
-
Mission: To serve God as He desires.
0 -
Bradley, the bottom line seems to be, if you download a resource (s) and hit restart while another one is index, the indexer crashes and you have to rebuild.
A feature needs to be put in place to prevent this.
Just finished downloading and indexing the same files that caused the crash on the other computer on this one. Went without a hitch. Both on the beta channel.
Mission: To serve God as He desires.
0 -
0
-
Lynden Williams said:
the indexer crashes
The previous log you posted showed multiple "Data error (cyclic redundancy check)."
This usually indicates an underlying hardware problem. I would strongly recommend running a full disk check and--especially if physical errors are reported--making frequent backups of your data and buying a replacement hard disk as soon as possible.
These disk failures are likely to be causing many different crashes in the app and indexer.
0 -
Will run the checks, but the last log was from my desktop. This time it was my laptop. Will run disk checker on both.
Mission: To serve God as He desires.
0 -
Lynden Williams said:
Will run the checks, but the last log was from my desktop. This time it was my laptop.
There's only been one LogosIndexerError.log file posted on this thread (in the first post), as far as I can see. That's the one I was commenting on.
0
