BUG: Indexer always fails without completing full index

Rev. Steven Poelman

Description

My Logos 5 program with data takes up at least 20 GB of space.  The indexer worked for a smaller size library.  But now indexing always fails within the first 20% of indexing.

Steps to reproduce

    October 6, 2013

    Loaded Logos5  normally, but with CTRL button held, to produce a diagnostic log.

    Logos ran normally.  Indexer started, then failed.  I kept this log file in case you would like it submitted.

 

    October 7, 2013

    Downloaded new program updates

    Ran setup to install latest Logos5 version updates

    Loaded  Logos 5 to see if indexer would now complete

    Indexer failed before 20%

    Typed command: Rebuild Index

    Indexer failed.

    Loaded Logos 5 normally, with CTRL button held.

    Program started normally.

    Indexing began.  Program indicating first time indexing was underway.

 Actual Result

    Indexing failed again at 5% completion.  I am uploading this log file with this post.

 Expected Result

    I expect the index should complete in 4 to 5 hours to 100%, and all my books should be indexed.

 System Specs

Desktop | Intel Core i3/ M350@2.27Ghz / 4GB Ram (3.80 GB usable) / x64-based processor, 64-bit Windows 8.1 Preview / Dell Laptop / Intel Motherboard integral Intel HD Graphics /AVG Premium Security, Webroot Secure Anywhere /  Keyscrambler

 Comments

I have tried running the indexer with all security software disabled (and completely unloaded) and with no other process except system required processes, but there is always the same result.

I'm including the Log Files from two days,, before and after the latest updates to Logos5.   The second log is after commanding Rebuild Index.

Bradley Grainger (Logos)

LogosIndexerError.log shows that there has been a continual failure to successfully create the SQLite indexes used during indexing. The most recent error is the most interesting, because it shows an error reading from a reverse interlinear resource. Since these resources are verified here (before upload) and on your machine (after download), it's highly unlikely that it was corrupted during the download process. My gut feeling is that there is a hardware error causing incorrect data to be written or read during indexing, which corrupts and crashes the indexer.

Some potential diagnostic steps or workarounds:

1) Run hardware diagnostics to make sure you don't have a faulty disk or memory. A full disk surface scan and running Memtest86+ could be worthwhile.

2) Make sure your CPU and RAM are not overclocked; this can cause data corruption. (It's unlikely that a laptop would have come overclocked from Dell, so if you've never changed your BIOS settings this probably isn't the problem.)

3) Logos 5 can (very rarely) cause inadequately-cooled systems to overheat, which can cause memory glitches that might result in this problem. Some users have reported success after using a household fan or buying a laptop cooling pad. Alternatively, in HKEY_CURRENT_USER\Software\Logos4, create a DWORD value named "MaxIndexingThreads" and set it to 1 to prevent the indexer using all your CPUs. Indexing will now take significantly longer. If that completes successfully, you can try increasing it to 2 or 3 (until it fails again, then reduce it).