First Time Index of whole library, for 1 book??

I apologize for not paying attention to the whole indexing subject. I never really had a problem with it, until now.

Recently I have noticed my Logos 5 goes into "First Time Indexing" whenever it downloads a new resource. This would not concern me if it quickly indexed. I The indexing takes about 24 hours no matter how large (400 books) or small (1 book) the download is.

I still have functionality while indexing is taking place. There are a couple seconds delay when searching. I am a patient guy so this doesn't bug me.

Do I have a problem? Or, is this just the way it goes? It just seems like overkill to index the whole library for one free Tozer book.

Find more posts tagged with

Comments

Bradley Grainger (Logos)

Do you have error log files?

DAL

https://community.logos.com/discussion/comment/551615#Comment_551615

Do you have error log files?

How do you get logs? Because the SAME thing happened to me. First it spent quite some time indexing and when it got to 29% it downloaded some more resources and restarted again. Then turned my computer off and it restarted the indexing process from 0% and 18 hours later it finally finished. Will it be any good to get logs for you now or wait til it happens again when it downloads a new resource?

Thanks!

DAL

PS. By the way, there were no error logs windows popping up, it just started indexing and said "First-time indexing underway." No error window or anything similar.

JT (alabama24)

https://community.logos.com/discussion/comment/551636#Comment_551636

How do you get logs?

See the wiki on diagnostic logging. NOTE: You must enable logging first.

Simon’s Brother

I had this issue also. I thought it might have been because it was the first time my system indexed while in Verbum mode. Wondered if it was indexinto for Deuterocannonical resources as in verbum mode these are covered in tools like bible facts but ignored in Logos mode. Sorry didn't catch logs at the time.

Mark Barnes

https://community.logos.com/discussion/comment/551636#Comment_551636

By the way, there were no error logs windows popping up, it just started indexing and said "First-time indexing underway."

What almost certainly happened in this case is that Logos detected index corruption during the first indexing. It then deleted the corrupt index, hence the "first-time indexing" message next. The Indexer Error log should confirm that, but if it keeps occurring, then a proper indexer log might help to pinpoint the problem.

DAL

https://community.logos.com/discussion/comment/551694#Comment_551694

By the way, there were no error logs windows popping up, it just started indexing and said "First-time indexing underway."

What almost certainly happened in this case is that Logos detected index corruption during the first indexing. It then deleted the corrupt index, hence the "first-time indexing" message next. The Indexer Error log should confirm that, but if it keeps occurring, then a proper indexer log might help to pinpoint the problem.

Question, though: If it does happen again, do I have to wait for the whole thing to get "re-indexed" for "the first time" again? That would totally not be good. Just wondering...

DAL

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/551636#Comment_551636

How do you get logs?

Go to "Documents\Logos Log Files" and find the files LogosError.log and LogosIndexerError.log. (These files will be created for more serious problems--such as reindexing--and do not require logging to be enabled.)

On Mac, the files should be in ~/Library/Application Support/Logos4/Logging

DAL

https://community.logos.com/discussion/comment/551718#Comment_551718

6724.LogosIndexer.log

4075.LogosIndexerCrash.txt

1263.LogosIndexerError.log

Alright, those are it I guess you know what to do with them, because I don't...hehehe

DAL

Mark Barnes

https://community.logos.com/discussion/comment/551753#Comment_551753

Looking through the Indexer error log, you've had three corrupted indexes: 16 March, 17 Sept, and 18 Nov. That's relatively high amount of failures, particularly when you think indexing might only happen once every few weeks.

These failures indicate a hardware problem with your PC. It could be:

Cooling is inadequate, and indexing causes the CPU to overheat (this is much more likely on a laptop than a desktop).
Your hard disk drive is worn out, and is approaching failure.
Something else.

You can check CPU temperatures whilst indexing with something like CoreTemp or SpeedFan. SpeedFan is probably better as it monitors HDD temperatures too, if you turn on SMART monitoring.

That said, you should run a proper SMART monitoring program in case the issue is with the hard disk. CrystalDiskInfo is very good. If you want to be very thorough, try HDDScan.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/551801#Comment_551801

The very last crash is: "The language tag 'Xn' is not supported."

'X' is actually the character 0x05, which is a control character. It was probably supposed to be 0x65 'e' (as in "en" == "English"), which means that two bits got flipped in memory during indexing. This is a fairly worrying indicator of system unreliability: your computer will not be able to function correctly if data is getting corrupted in memory.

As Mark said, this could be caused by overheating. It may also be due to bad RAM. I'd recommend running an overnight memory checker like memtest86+ (http://www.memtest.org/).

DAL

https://community.logos.com/discussion/comment/551858#Comment_551858

Well I hope is not needing a new laptop since I've only had this for a little over a year. I just downloaded a free vyrso book and it will be indexing soon, once it restarts. I hope the indexer doesn't kick in to first time indexing again. We'll see...

DAL

Edit: Well after 10 or 12 minutes it finally indexed the one book from Vyrso I downloaded. So I guess the problem got fixed. Thanks! I'll keep in mind your great suggestions to prevent future crashes.