BUG: Corrupted index—AGAIN
Ran the following search with these pathetic results.
Tried Bible Search and received results only from NRSV. Ran command "Rebuild Bible Index" and received proper results from all Bibles.
Comments
-
It seems like indexes are getting corrupted more often these days. Two people reported no results in a search the other day, and rebuilding the index fixed it for them. I wish there was some way for Faithlife to get to the bottom of this. The problem is, people usually don't collect logs until it's too late. There needs to be a way of having Logos not overwrite the previous set of logs when running, so that you can go back one or two sets of logs after the fact when something like this happens and send the logs in so FL can diagnose what caused it.
0 -
Rosie Perera said:
It seems like indexes are getting corrupted more often these days.
Which is the reason for AGAIN in the thread title. This is the second time this bug has bitten me. Again, Rebuild Index restored search results. The results from the screenshot in the OP show results only from resources added/updated 06-26 & 27. Nothing prior to June 26 yielded any results.
Don't know if it will help, but here is the indexer log for the rebuild.
The log indicates that indexing was completed at 20:47:46, but the notice remained in the tool bar—at 99%—until I restarted Logos at 05:30 this morning. The indicator was gone from the OS Menu Bar however.
0 -
We're still investigating, but as you say, there isn't much for us to go on yet. I'll alert devs to this thread. Thanks!
0 -
Eli Evans said:
We're still investigating, but as you say, there isn't much for us to go on yet. I'll alert devs to this thread. Thanks!
Understand how difficult intermittent problems can be to troubleshoot. If it happens to me again, I will try to gather as much information as I can.
0 -
It would of course be best of all if the indexes never got corrupt. But for now, accepting that they do ...
Maybe an option to build an alternative copy in some kind of compare mode. i.e. a verify in effect. Then it could tell you there is a problem and maybe even something about the nature of the error or corruption so the result from the verify could be submitted as a bug.
I would gladly give up additional disk on my main PC if it could somehow massively improve the indexing stability and/or rebuild times. This would of course be much less a starter on small portables with 64 or 128 GB flash SSD only etc.
0
