7.8 SR-1 Update ... extremely long time indexing...

Howdy,

I downloaded the new update, and it is taking an extremely long time to index.

After over an hour, it is only at 58% complete, and the resources usage is so great, that I can't use some of my other programs during the index process.

No new resources are showing up, so I have to figure this is an entire system indexing, and can't help but wonder if a Bible index will start next time I open the software? I checked my log files directory, and no new files are listed there to indicate an indexing error.

I would have appreciated a heads up that the indexing would take so long.

Thank you,

Paul L. White, Satisfied Logos user since 1.6 ... feeling a little perplexed

Find more posts tagged with

Comments

Jan Krohn

I can confirm this issue. Indexing of "Revising Hermon" was at 53% after running through the night. [:S]

Dave Hooton

https://community.logos.com/discussion/comment/915038#Comment_915038

OK guys, you need to provide some logs so that Faithlife can see what is happening. Stop Kill the Indexer, enable logging and then upload the compressed Log folder after indexing has reached the same stage.

Dave Hooton

I checked my log files directory, and no new files are listed there to indicate an indexing error.

Errors/Crashes are logged automatically but you need to enable logging for the detailed information that is needed.

Randy W. Sims

https://community.logos.com/discussion/comment/915038#Comment_915038

I can confirm this issue. Indexing of "Revising Hermon" was at 53% after running through the night.

I wasn't at my computer to notice but my log recorded no problem that I can see with this resource.

1185.Logos Log Files.zip

Paul L. White

https://community.logos.com/discussion/comment/915042#Comment_915042

I did open the software so that logs could be created, but no logs were generated. I think, from Dave's comments, that's because I left the indexer working rather than delete it from memory.

I can state that the total indexing time was 2 hours and 17 minutes. I can also state that, in the AppData directory, Logos had installed an entirely new version of itself. I opened one of the files there (not a .txt ending) with Notepad, and examined the information provided, and no error messages were included.

My conclusion is that Logos installed an entirely new version of itself, not just an update. Once the indexing was finished, I tried opening the software again, and there was no indicator for a second round of indexing...which used to happen on a fresh install, i.e. index the entire library first, and then the Bible library.

Also, when I open the software *now*, with Ctrl Alt keys, there is no Log file created.

Thanks.

Dave Hooton

https://community.logos.com/discussion/comment/915060#Comment_915060

no logs were generated. I think, from Dave's comments, that's because I left the indexer working rather than delete it from memory.

Correct, first kill/end the Indexer in Task Manager. Pausing and then Resuming will not allow the Indexer log to be generated.

I can also state that, in the AppData directory, Logos had installed an entirely new version of itself. I opened one of the files there (not a .txt ending) with Notepad, and examined the information provided, and no error messages were included.

The Log files folder is in your Documents folder. Please enable logging as per https://wiki.logos.com/Diagnostic_Logging and then upload the compressed Log files folder. It will contain the log files for the installation, the Logos app and the Indexer.

Dave Hooton

https://community.logos.com/discussion/comment/915051#Comment_915051

my log recorded no problem that I can see with this resource.

Correct. But your experience isn't indicative of what others are experiencing with their installation.

Paul L. White

https://community.logos.com/discussion/comment/915090#Comment_915090

5460.LogosErrorFiles-7-29-17.zip

I was looking in the wrong folder...my user folder, not the documents folder. Apparently that destination has changed, or something or other. [:)]

And apparently I already have logging enabled.

Salute!

PS I included a file from 7/25, I believe. I figured that might contribute to your diagnosis. Logos felt my index file was corrupt. But it was working fantastically after 7.8. I specifically tested the inline search feature, as it used to be that if I did an inline search in the ESV for example, I'd get the results of a topic search. But now, after 7.8, I received *first* an inline search like it used to be, and Then a topic search, if I wanted it. Which is the way it is supposed to work. I was so glad. If the indexer file was truly corrupt, I wouldn't have had such nice results.

Dave Hooton

https://community.logos.com/discussion/comment/915093#Comment_915093

5460.LogosErrorFiles-7-29-17.zip

The Indexer error log file is from 28 July, but there is an history of corrupt files from Feb 14, so I recommend you kill the Indexer and delete the folder C:\Users\Paul White\AppData\Local\Logos\Data\i0c004nz.j3m\LibraryIndex. Ensure logging is enabled, then restart Logos and indexing should recommence. It will take a few hours to reindex your library.

Paul L. White

https://community.logos.com/discussion/comment/915100#Comment_915100

Howdy Dave,

I'm a little confused here.

First, I don't have that particular subdirectory in the Logos Data folder. Mine is entitled "rjqpvz1c.fwy."

Second, I didn't get this machine until around March 9th. So it's baffling to me as to how I could have problems since February ... on this machine.

That's a rather time intensive step to take, so I'd rather not do it unless necessary. I am hoping that the information I just gave you helps to resolve some things.

Thanks,

Paul

PS The indexer is no longer in need of being "killed" ... as it finished in the wee hours this morning.

JT (alabama24)

https://community.logos.com/discussion/comment/915110#Comment_915110

Second, I didn't get this machine until around March 9th. So it's baffling to me as to how I could have problems since February ... on this machine.

Did you use a shortcut method of installation?

Paul L. White

https://community.logos.com/discussion/comment/915111#Comment_915111

Last year, when I had Logos 6, a technician from Logos dialed in remotely and tried a shortcut version to the install of Logos 6 in order to see if that would resolve the problem of having a black screen for the Home Page. But then we ended up having to completely erase Logos, all of its files, and install the program again.

However, that was on a completely different computer. On that same computer, I did have a problem in February as a post describes above.

Again, however, this is a brand new computer. So somehow that information on those previous problems carried over from the archived information that Logos keeps into the current configuration, is what I'm guessing.

If your question involves this particular install of SR-1, no. I wouldn't know how to do a shortcut install by myself. Thanks.

PS That remote work done by the technician was on August 29th, 2016.

Dave Hooton

https://community.logos.com/discussion/comment/915110#Comment_915110

I'm a little confused here.

That makes two of us!

I don't have that particular subdirectory in the Logos Data folder. Mine is entitled "rjqpvz1c.fwy"

The Logos log is for 7.8 SR-1 (0037) and shows that its Data folder is "rjqpvz1c.fwy"

The Indexer Error log starts at Feb 2017 and goes to v7.8 (0031) on 28 July. The Data folder is "i0c004nz.j3m"

The Logos Error Log starts at Aug 2016 and goes to v7.8 (0031) on 25 July. The Data folder changes from "3vqjk1nd.2v5" to "i0c004nz.j3m" on 5 March.

So, is "rjqpvz1c.fwy." the only folder in C:\Users\Paul White\AppData\Local\Logos\Data?

Does Logos function OK now - with no other indexing?

Paul L. White

https://community.logos.com/discussion/comment/915114#Comment_915114

Yes, the rjq.... directory is the only folder in that directory. And yes, Logos functions OK now, without further indexing.

Like I say, it took 2 hours and 17 minutes, though, to do the indexing after install of 7.8, SR-1.

My concern is that it appears that the index error log file is being *appended to* and sent to the cloud. Otherwise, how would you have information from a previous PC that is no longer in use?

The previous PC died on the evening of March 5. So how would there be an Index Error log entry dated Feb. 2017? And August 2016 was when Logos 7 came out, was it not, and I was having trouble with Logos 6 at that same time? Why is that information in the Logos Error file?

I have to conclude that error messages are being appended to that log file, and therefore, as you review the information, you have no clue as to what PC is being used per error message. How can you have?

The question remains though: why did Logos have to completely reindex itself on version 8 SR-1? Something is amiss there. And why did the installer software conclude that my index file was corrupted?

Thanks,

Paul

PS I still have to use the Search feature, and then reference a particular book, if I am looking for something within that book. The inline search doesn't quite work for me as I'm thinking it should. Maybe I don't know how to use inline that well. But this happened before 7.8 came out, and I thought maybe that's what it was fixing.

Paul L. White

https://community.logos.com/discussion/comment/915116#Comment_915116

Also, after the install of version 7.8, I did a Registry Clean, and there were numerous errors left in the registry related to Logos and the Install. Various folders were no longer in existence, and references to the indexer were needing to be deleted from the registry.

I was quite surprised by that. I should have kept a list of the error messages and sent them. But I would suggest that something in the original 7.8 install led to this problem with 7.8 SR-1.

Salute!

Dave Hooton

https://community.logos.com/discussion/comment/915116#Comment_915116

I have to conclude that error messages are being appended to that log file, and therefore, as you review the information, you have no clue as to what PC is being used per error message.

The 'Error' files are normally appended to, but not from another machine. And I've just noticed that the Logos Error Log suddenly shows the Data file to be 'rjqpvz1c.fwy' from 19 March - the first entry after 5 March! The message is formatted as if on the same machine. When you switched machines, did you use a utility to copy data files across?

I still have to use the Search feature, and then reference a particular book, if I am looking for something within that book. The inline search doesn't quite work for me as I'm thinking it should.

Please provide a step-by-step explanation, preferably with screen shots.

Dave Hooton

https://community.logos.com/discussion/comment/915117#Comment_915117

Also, after the install of version 7.8, I did a Registry Clean, and there were numerous errors left in the registry related to Logos and the Install. Various folders were no longer in existence, and references to the indexer were needing to be deleted from the registry.

How did you install Logos for the first time on the new machine?

JT (alabama24)

https://community.logos.com/discussion/comment/915125#Comment_915125

How did you install Logos for the first time on the new machine?

That was the heart of my question above, which I don't know if was directly answered!

Paul - asked in a different way:

Did you personally do the installation on the new machine?
Did you download and install the engine, and allow all the resources to download from the servers?

Paul L. White

https://community.logos.com/discussion/comment/915124#Comment_915124

Yes, Sir, that's exactly what happened Mr. Dave Hooton. After I was just now able to get some sleep, it came to me clear as a bell upon awakening.

The technician who initialized this new (refurbished) computer did copy data files from the previous hard drive. To make matters even *more* interesting, he made a mistake, and copied Drive C data files from my laptop that he was using as an engine to do the file transfer (information from the user directory). I had to point that out, so then he went back and copied from the correct hard drive. From what you're telling me, it sounds like you are now seeing the appended file from my former PC, not the laptop. But I can't swear to it.

As to installing Logos, per Mr. Hooten and Alabama24, I did that install myself. It was all done via the install program. Whether there were some resources copied over from the previous hard drive when this machine was set up, that I'm not able to say.

Suffice it to say, however, I'm not clear as to how any of this affects what happened with the indexer on version 7.8 SR-1. How would any of this corrupt the index file that was working after the install of 7.8 originally?

As to the screen grabs from inline search challenges, I'm going to have to do that in a couple of days, as I am swamped with personal chores, and need to take Monday off in order to be able to catch up on a Sunday, which is usually the day I take off. But I will be more than happy to provide that. It may be that I don't know how to find all the "hits" with an inline search like you can with a regular search. I think you simply click on a down arrow in the toolbar of your resource, I'm not sure.

Thank you so much for your help!

Paul L. White

https://community.logos.com/discussion/comment/915129#Comment_915129

PS Now that I think about it, the install on this machine took far less time than it has previously on my much slower machine, and far less time than on my laptop. The savings was so remarkable I actually wrote Mr. Pritchett and complimented him on the fact that the Logos technicians never told me I had problems before because of a slow machine, and he responded and copied the response Email over to his entire technical staff!!!

However, if resources were inadvertently copied over from my previous hard drive, then I'm now wondering whether that cut down on the install time? I figured the advantage was that this is a quad core machine, instead of dual core, and that I have 16 GB of memory and a terabyte hard drive and 64 bit Windows 7 OS? My previous machine had a 32 bit Windows 7 OS.

I sure would hate to have to erase the entire program and reinstall. But once again, I have to ask: how does any of this affect the fact that indexer had to go for 2 hours and 17 minutes? Especially when others had the same circumstance when downloading 7.8 SR-1?

Also, on this machine the technician created a user name "Paul White" with a space in it. That messed up the install of my Real Player software, and it took the technicians of that company several months to figure it out.

I think millennials would say "bleh" at this point. But I don't know what that means, exactly, so I won't say it. LOL

Paul L. White

https://community.logos.com/discussion/comment/915124#Comment_915124

Please note the first two pictures are of an inline search on Eidersheim. The second is the result of the search. I see no highlighting of memra. However, in the third screen grab, doing a basic search in that same resource shows (to the right of the screen this time) the "hits" and you can see the word memra quite clearly. There, I finished my homework. :-) Thanks, y'all.

Paul L. White

https://community.logos.com/discussion/comment/915129#Comment_915129

One last note: when the technician configured this machine, he also did a backup of my user files from the previous one onto my data drive ... drive D.

On that drive, there is a Logos subdirectory with 16 GB plus of data.

Does Logos keep its eye on drive C? Or can something on Drive D possibly affect it? I'm guessing that the install program doesn't look at anything but drive C.

Thought you should know, though.

Take care,

Paul

Dave Hooton

https://community.logos.com/discussion/comment/915133#Comment_915133

I sure would hate to have to erase the entire program and reinstall. But once again, I have to ask: how does any of this affect the fact that indexer had to go for 2 hours and 17 minutes?

A corrupted index file was logged at 11:34pm on Jul 28th by v7.8 (0031) and it initiated a reindex. v7.8 SR-1 (0037) was installed prior to 07:55 on the 29th, so it could have coincided with that indexing and possibly restarted it (can't tell for sure without logs). As there are no Indexer errors for SR-1 the corruption appears to be fixed.

Dave Hooton

https://community.logos.com/discussion/comment/915141#Comment_915141

On that drive, there is a Logos subdirectory with 16 GB plus of data.

Does Logos keep its eye on drive C? Or can something on Drive D possibly affect it?

You can delete the Logos subdirectory on as it won't affect the installation on drive C:

Dave Hooton

https://community.logos.com/discussion/comment/915135#Comment_915135

The second is the result of the search. I see no highlighting of memra.

It's there if you scroll down (in footnote 3). Alter the view from Article to Sentence to get shorter result text.

Paul L. White

https://community.logos.com/discussion/comment/915172#Comment_915172

Thank you, Dave.

I just wanted to make sure the files on drive D didn't *impede* the install, or *confuse* it in any way. Glad to hear it doesn't do either.

As to the inline search, I tried this twice, and see, now, what you're saying. The first time, I was confused, as there was no "sentence" option, but there was a "search result" option.

But now I see that there are two "headers" after an inline search is initiated. The top once has the "article, page, sentence" option, but only after starting a search. The bottom one has "article, page, search result" options. When I say "bottom," it is still above the text.

But it works, and I can go from hit to hit. Thank you so much for taking time on the Lord's day to help me!!!

Last question: what can I do to prevent index file corruption? That happens every so often, and I'd like to avoid it. Salute!

Dave Hooton

https://community.logos.com/discussion/comment/915175#Comment_915175

Last question: what can I do to prevent index file corruption?

It is rare these days, but you can run a drive utility to minimise/fix file system errors. It won't necessarily detect a corrupt index file as that usually arises from the file being formatted/written during indexing but it will ensure the integrity of the drive.

Paul L. White

https://community.logos.com/discussion/comment/915206#Comment_915206

Okay Dave. I appreciate it.

I've often wondered if there was a way for Logos to, when there is an update available, download *only the software update* and run it *first* .... after that is finished there should be no indexing involved. *Then* download pending resources, and then index.

I checked my schedule for defragmenting the hard drive, and I don't believe that was a factor, as the computer said it was last defragmented end of June.

What baffles me is that 7.8 worked just fine. Indexes were working. My conclusion, from what you just said, is that 7.8 SR-1 installed both the software and an updated resource (not a purchased one, but one that had an update of its own..."Daily Truth: Study and Application Notes (etc.)" ... at the same time, and thus the indexing started before the software install was finished.

Since this is happening at least twice a year for me, then I hope you can understand my concern. Thank you so very much, again, for your time.

Dave Hooton

https://community.logos.com/discussion/comment/915208#Comment_915208

I checked my schedule for defragmenting the hard drive

I meant a utility that checks for hard drive errors

My conclusion, from what you just said, is that 7.8 SR-1 installed both the software and an updated resource (not a purchased one, but one that had an update of its own...and thus the indexing started before the software install was finished.

That wasn't what I said, but we can't be sure about anything without logs. If you have logging permanently enabled then any reoccurrence can be diagnosed with certainty.

Paul L. White

https://community.logos.com/discussion/comment/915212#Comment_915212

Yes, Sir. I understood (about the utility). I only meant, in my comment on defragging, that it wasn't going on in the background during my install of either of the 7.8 updates.

I believe I have the logging permanently enabled. I presume you just run the logging utility that we download, and never run the "turn logging off" utility to have it permanent. Last question, and I'll leave you alone. [:D] I thought you had to start Logos with the control and shift keys in order for logging to take place. It would be nice if it happened just by clicking on the desktop icon, as long as you have logging enabled.

Salute!

Paul

PS My OS is Windows 7, and I checked on scanning for errors, and plan to do that in the very near future as soon as time permits. Blessings.

Graham Criddle

https://community.logos.com/discussion/comment/915241#Comment_915241

It would be nice if it happened just by clicking on the desktop icon, as long as you have logging enabled.

With logging permanently enabled Logos starts automatically when clicking the desktop icon

Paul L. White

https://community.logos.com/discussion/comment/915244#Comment_915244

Thank you, Mr. Criddle.

I did run a chkdsk utility in Cmd mode, and piped the results into a notepad file, which I've attached.2273.diskcheck.txt

However, chkdsk, even though it says it is scheduled to run and fix errors on restart, doesn't do anything on restart. I even shut off my machine, then started it again. And I didn't see the chkdsk messages coming up on the screen before Windows started.

I researched the error that this text file indicates ("the volume bitmap is incorrect"), and apparently that is a problem held over from Vista. So I'm going to presume that my hard drive is clean.

I've spent nearly 45 minutes on this procedure, so I need to get to doing other things. But I do thank you all for your generous time and benevolence.