Indexing... 373 hours to go

No, that's not a typo - I received the latest "resource updates are available" message and blindly pressed OK when I finished my work (still no UI to know what's in the list of updates). It's been about 12 hours since I Logos started indexing and the estimate till completion time just keeps getting longer and longer.

Any ideas?

I'm running on Windows XP + SP3, version 4.20.4.7970 (latest beta channel update).

Find more posts tagged with

Comments

Dave Hooton

You might have the 1 GB update that came with 4.2 so you will get wild estimates because it tries to cover indexing the Bible Index and the main Library Index. 12 hours does seem a long time, though. Is this taking longer than a re-index you would have done in the past (including initial installation? Do you have any files in \My documents\Logos Log files? If so upload them.

Stuart Robertson

https://community.logos.com/discussion/comment/198235#Comment_198235

Still indexing - coming up on 14 hours now - estimate is now at 385 hours to go. There is nothing in \My documents\Logos Log files - just an old Logos4Crash.txt from about 2 weeks ago. Any other ideas - 385 hours is 16 days, which is a tad long to have my CPU at 100%... :-(

Rich DeRuiter

https://community.logos.com/discussion/comment/198250#Comment_198250

Still indexing - coming up on 14 hours now - estimate is now at 385 hours to go. There is nothing in \My documents\Logos Log files - just an old Logos4Crash.txt from about 2 weeks ago. Any other ideas - 385 hours is 16 days, which is a tad long to have my CPU at 100%... :-(

If your anti-virus does 'on access' (AKA 'real time') file scanning, that can really slow things down. You may want to disable that function and see what happens.

I know. I'm guessing. But it's something to try, and it doesn't cost anything.

Dave Hooton

https://community.logos.com/discussion/comment/198250#Comment_198250

The best idea is to let Customer Support peek at your computer to see what is happening as we (in the forum) need some logs.

If you think it is going nowhere, then enable permanent logging, Pause indexing by right clicking the Logos icon in the Task Bar (Notification area) and kill logos4Indexer.exe in Task Manager. Restart L4 and upload the logs after a couple of hours (don't stop the indexing!).

David Ames

https://community.logos.com/discussion/comment/198385#Comment_198385

Did you try rebooting? [shut the computer off and restart from totally off]

Stuart Robertson

https://community.logos.com/discussion/comment/198525#Comment_198525

I've rebooted the machine (twice now), paused indexing, then killed the indexer exe via Process Explorer. I've defragmented the disk and disabled antivirus. But each time I restart indexing (that is, start up Logos and the indexer auto-starts) the estimate just climbs and climbs. It was first at 8 minutes when I restarted, then 20 minutes and now, after about 10 minutes of indexing, the estimate is sitting at 47 minutes.

There is nothing in the logs folder so I will enable permanent logging and post whatever logs are produced as a result.

All of this grief because of an update - that I didn't "approve" - Logos simply says "Resources will be added - press OK to restart", basically and this is the result... Some means of reviewing and/or "approving" or selecting resource updates really should be provided by Logos. I can still run Logos for Mac, but my Windows Logos is, currently, totally dead.

I'll run the permanent logging thing for a bit but I'm not overly hopeful. And the tired part of me wonders whether a re-install won't simply run into the same issue... ?

Stuart Robertson

https://community.logos.com/discussion/comment/198571#Comment_198571

Attached is Logos4Indexer.log. Indexing seems fast in the beginning (CPU runs at nearly 100%) and then slows down to a crawl, estimated time till completion climbs steadily and CPU stays at about 60% - less than at the start when things seemed to be "moving".

Stuart Robertson

https://community.logos.com/discussion/comment/198583#Comment_198583

Would help if I attached the log file... :-) 8030.Logos4Indexer.log

Dave Hooton

https://community.logos.com/discussion/comment/198584#Comment_198584

Progress is being made. You can check the log periodically eg.

Info WindowsIndexerProgress 79 of 118 resources indexed; total progress is 39.2%

Info BibleIndex (1m 11.1s) Indexing LLS:LDGNT

These lines let you know how many resources have been indexed and that it is in the Bible Index.

Ignore the time estimates.

Later on, you should see similar lines for the main Library Index eg.

Info WindowsIndexerProgress 12 of ??? resources indexed; total progress is 39.2%

Info LibraryIndex (1m 11.1s) Indexing LLS:29.2.6

Note that there will be more resources (???) in the Library Index than the 118 in Bible Index.

Stuart Robertson

https://community.logos.com/discussion/comment/198763#Comment_198763

Restarted indexing - seems to be hung on entry 79 - see log with line: BibleIndex (Timed) Indexing LLS:LEB

Any ideas how to get it past entry 79?2072.Logos4Indexer.log

Estimate just keeps on growing... remind me again why I'm doing this indexing thing...?!

Dave Hooton

https://community.logos.com/discussion/comment/198787#Comment_198787

Restarted indexing

Please don't do that (rebuild index?) because you can cause it to re-index unnecessarily eg. you don't want it to repeat Bible indexing if it was doing Library indexing (use rebuild library index in that case).

Any ideas how to get it past entry 79?

It is also indexing KJV1900, AV1873 and 1.0.710 (ESV) -- which are Reverse Interlinears and each one can take about 4-5 minutes on your system.

How's it going now?

Tell me about your computer system (you seem to have a quad-core processor, but how fast?).

Stuart Robertson

https://community.logos.com/discussion/comment/198812#Comment_198812

I didn't restart indexing using a Logos command - I just restarted the VM (Parallels 5) that it was running in and then restarted Logos. I'm running Logos for Win inside an XP VM on a 17" Macbook Pro 2.66GHz, i7 with 8GB RAM. It's normally very fast - faster than Logos for Mac, actually - but since the last resource update it's taking forever - I gave the VM 2 extra CPUs - was 2 previously and increased to 4 in the hopes of speeding up indexing, but to no avail.

I've killed the indexer again so I can get some reading done - tomorrow's another day. If the same issues continue then I will likely ask for advice on how to reinstall entirely - I've wasted so much time on this already... :-(

Dave Hooton

https://community.logos.com/discussion/comment/198854#Comment_198854

I didn't restart indexing using a Logos command - I just restarted the VM (Parallels 5) that it was running in and then restarted Logos.

Which then starts indexing from scratch! If you pause indexing (by right clicking the Logos icon in Task Bar) can you save the state of the VM, so that it allows the indexing to resume where you paused it?

I'm running Logos for Win inside an XP VM on a 17" Macbook Pro 2.66GHz, i7 with 8GB RAM. It's normally very fast - faster than Logos for Mac, actually - but since the last resource update it's taking forever - I gave the VM 2 extra CPUs - was 2 previously and increased to 4 in the hopes of speeding up indexing, but to no avail.

I doubt that you are getting 4 books indexing simultaneously or they are heavily using other VM resources and slowing each other down (specifically, the Reverse Interlinears). I'd go back to 2 CPU's for the VM, although it would mean starting the indexing from scratch.

If the same issues continue then I will likely ask for advice on how to reinstall entirely - I've wasted so much time on this already... :-(

It would still need to index!

Stuart Robertson

https://community.logos.com/discussion/comment/198948#Comment_198948

Which then starts indexing from scratch! If you pause indexing (by right clicking the Logos icon in Task Bar) can you save the state of the VM, so that it allows the indexing to resume where you paused it?

I didn't know restarting the machine would cause the entire indexing process to be started from scratch... :-( That's not tremendously helpful behaviour, especially since at the current rate indexing doesn't finish in 12 hours (not even close). Basically have to leave it running all weekend and hope the estimate isn't at 4000 hours come Monday morning...