Indexer gives up at 38%

First time indexing following the massive file updates of last week (Windows Vista machine so still working with Logos 5.2b SR-7 (5.2.2.1584). Had deleted the Library Index folder just prior to this indexing as without that it seemed unable to get past 1% on repeated attempts: This time it got to 38.6% and gave up....
(LogosIndexer.log file edited to remove the middle where it seemed to be progressing well as the original file was 8MB).

It seems to be suggesting it ran out of space, yet it still has 56.6 GB free space on the drive, 74.4GB used.

8686.LogosIndexer 2014Nov02 edited.log

Find more posts tagged with

Comments

Bradley Grainger (Logos)

Indexing was aborted because SQLite (an embedded database engine used during indexing) encountered database corruption. SQLite is extensively tested, so this could indicate a local hardware problem.

Indexing has been known to overstress computers in the past; is it possible yours could be overheating? Some users with laptops have reported success with using a cooling pad during indexing. For a desktop computer, it could be good to blow out any dust that has accumulated.

It may also be worthwhile running an overnight memory burn-in test to verify it doesn't have any errors.

David Wilson

https://community.logos.com/discussion/comment/651855#Comment_651855

Hi Bradley:

The system is an HP desktop and was returned from our local computer shop just a few weeks ago (September) after some maintenance which included a new power supply and thorough internal cleaning. It passed the built in monthly HP hardware testing package on October 31 with no hardware errors identified (everything passed during those extensive tests). It has not had a recent "stress test" like re-indexing the entire library in quite a while so anything is possible. Will try again while I am away today with the side off the case and see how far it gets.....

David Wilson

https://community.logos.com/discussion/comment/651931#Comment_651931

Tried again to Rebuid Index: hover over the Indexer icon suggested it was well over 40% but that is not what the log is saying. Seems to be running cool. Says it is running out of space which is not true on the drive opn which it is running, it has over 56GB Free Space (drive C: has 222GB Free Space, not sure why it thinks it is running out of space.....

7455.LogosIndexer 2014Nov03pm edited.log

Dave Hooton

https://community.logos.com/discussion/comment/652882#Comment_652882

It was a similar error to previously. Running out of space is one of the reasons listed for aborting; cancelled & failed are the others.

As it was a different file and different reason, but still a database corruption, I can only refer to Bradley's earlier comment.