I don't know what was indexing, but I had an issue with overheating and a VERY long indexing.
8473.LogosLogs.20160211-173207.zip
From your log:
02/11/2016 12:29:40 | INFO | 5 | LibraryIndex | Re-indexing because the existing index is corrupt or missing. 02/11/2016 12:29:40 | INFO | 5 | LibraryIndex | Final count: 6,242 resources need to be indexed; no merge necessary.
So it was a complete reindex. Interesting. Any idea why?
The indexer log shows you are on Mac Beta 6.10 version 2.
There are recurring problems with the implementation of the new "mono". See the forum there.
My advice: wait patiently for a next beta and do not index at the moment.
FWIW, Hans
It does??? I am NOT on beta! That is weird...
The indexer log shows you are on Mac Beta 6.10 version 2. It does??? I am NOT on beta! That is weird...
Sorry, you are right. I downloaded the zip file you uploaded, opened the indexer.log and it seems I got another log first. Strange....
I have had that happen too! [:)]
Indexing is roughly equivalent to the number of resources you own, divided by the speed of your computer. In general, and so long as your computer isn't acting up.
it seems I got another log first. Strange....
I have had this happen after I quit Console with a log file still open. I have developed the habit of closing open log files prior to quitting Console.
Of course, you and Bama may have some other strange gremlin.
It wasn't long for a full reindexing. It was long for what I thought was no more than a couple Vyrso titles.
It wasn't long for a full reindexing
The log shows it took 5 hours for the Library indexing to complete normally (no Bible indexing needed) i.e. problem now corrected, but the cause of corrupt indexes is unknown!
the cause of corrupt indexes is unknown!
Meaning mine, or in general? Should I consider this a "one off," or is there something larger at play (on my machine or in the code)?
Should I consider this a "one off," or is there something larger at play (on my machine or in the code)?
Time will tell [^o)]
Meaning mine, or in general?
Faithlife do not understand why SQLite databases become corrupt; whether used as resource indexes or otherwise. They are usually fixable, which shows that the corruption is related to content and not the file system.
Meaning mine, or in general? Faithlife do not understand why SQLite databases become corrupt; whether used as resource indexes or otherwise. They are usually fixable, which shows that the corruption is related to content and not the file system.
My MacBook is again performing a FULL indexing. Thoughts anyone? Help?
Logs?
Now that is just unreasonable. Just because I ask OTHER people for logs, why should YOU ask me for them? [:D]
2705.LogosLogs.20160211-173207.zip
Now that is just unreasonable. Just because I ask OTHER people for logs, why should YOU ask me for them? 2705.LogosLogs.20160211-173207.zip
Now that is just unreasonable. Just because I ask OTHER people for logs, why should YOU ask me for them?
Those logs are dated Feb 11th (and kind of look like the ones attached to the OP...); are they the latest that you have?
I'll double check when I get home. I tried to upload to you a "sample" from today.
I did grab the wrong one. Sorry. [:s]
1070.LogosLogs.20160216-102306.zip
Logs? Now that is just unreasonable. Just because I ask OTHER people for logs, why should YOU ask me for them? 2705.LogosLogs.20160211-173207.zip
Now this did amuse me, my mirth was compounded when you sent the wrong ones.
Glad to be of amusement. [:P]
