Can any inform me as to how I get Logos to get past 15% with it Indexing/
The first question is always how much free space do you have? If you have 2.5 * the size of your indexes, the we need the logs to see what it is doing when it stalls.
Mine keeps stopping on 21%. I have to restart Logos to make it continue.
Thanks for the reply. I've more than enough space on the Drive, so that wasn't the issue. I also restarted Logos & the snag subsided. I don't recall this happening before but with the memory banks depleting, one cannot be absolutely sure.
If you want my logs still, I can send them.
Logs please.
I usually send the wrong one, so I'll send two. I'm going to be away from my system all day tomorrow but will get back to you if indeed I've still sent the wrong ones.
5367.LogosError.log
6675.LogosIndexer.log
I have reported this in the past. In my case the workaround it to exit L8, and restart it. it usually will continue the indexing. sometimes I have to do it a couple times. mine usually stops at about 3%, sometimes 8%. but once I exit and restart it, it seems to continue and move past the stop-place.
I usually send the wrong one, so I'll send two
We need logs when you are experiencing the issue, so the indexer log doesn't help. To prevent sending the wrong ones, just upload the compressed (zipped) Log Files folder.
Sorry Dave, but when you say "logs please" I understand from that you need 'log files' now. Also, adding to the confusion is that you ask for a 'compressed (zipped) Log Files Folder' when there is no such thing found.
I have six different 'Logos Files' in a 'Logos File Directory' so asking me for the one you mention can only leave one perplexed, or at least it does me!
The link I applied to "logs please" is https://wiki.logos.com/Diagnostic_Logging and this clarifies what the Log Files folder (or directory) is i.e. Documents\Logos Log Files in Windows. It also states how to "zip" the Log Files i.e. right-click the folder and choose Send to, then Compressed (zipped) folder. That way, you upload all the log files it contains.
I did not realize "logs please" was a link and therefore did not click on it. It might be more helpful for us simple ones to put a 'click on this link' and thus save on the confusion & misunderstanding.
Also, I had no idea I should only upload them when the problem was in progression. I thought you wanted it right away, so with an appointment to be kept, I was doing my best at the time to rush them off to you.
Whatever, if I see it hang again when indexing, I'll upload them to you & others the way you have clarified it to be done & thus you or someone might find the snag.
I did not realize "logs please" was a link
The log files you supplied are provided as a link, and have the traditional blue colour; so we don't need to state that it is a link. If one cannot distinguish colours, then hovering over a "suspect" link will change the mouse pointer.
Also, I had no idea I should only upload them when the problem was in progression.
Most problems are repeatable, so that gives you a chance to enable logging, restart Logos and reproduce it.
Maybe it's my screen or just my eyes, but I seriously never noticed that. Therefore from where I'm sitting, there was no need to hover the mouse over the line you gave. I take that as a simple request. Not sure, but for those are colour blind, reading "logs now" could send someone down the garden path as it did I.
However, the fault apparently does lie more with myself than anything you did. I just need to sharpen up a bit.
I'm rebuilding the Index now, so if it sticks, I'll attempt to upload what you are asking for.
Ok, I see Logos seems to be sticking this time at 12%. I'm finding 'enabling logging' isn't doing anything, so I must have it enabled already.
I've picked up on a file that was created at this very moment, so I'm going to zip it and send. Hopefully this time, I'll do it right. If not, I'll make another attempt.
7750.LogosIndexer.zip
Not being sure, I'm going to send this other File that was created at the same time.
0676.LogosIndexer (2).zip
Having overlooked your earlier instructions, I've zipped the whole Folder. Here it is.
2870.Logos Log Files.zip
You are getting a number of messages in the indexer log file of the form:
2019-03-24 03:33:40.0996 12 Info BibleIndex (Timed) Attempting to replace index 'F:\Logos\Data\12o2kucd.14j\BibleIndex/index' with new index 'F:\Logos\Data\12o2kucd.14j\BibleIndex/index-build'.2019-03-24 03:33:40.1046 12 Info FileSystemIndexInfo Replacing F:\Logos\Data\12o2kucd.14j\BibleIndex/index with F:\Logos\Data\12o2kucd.14j\BibleIndex/index-build2019-03-24 03:33:40.6165 12 Error FileSystemIndexInfo Couldn't replace 'F:\Logos\Data\12o2kucd.14j\BibleIndex\index.dcm' with 'F:\Logos\Data\12o2kucd.14j\BibleIndex\index-build.dcm'; rolling back replace operation.2019-03-24 03:33:40.6175 12 Warn BibleIndex Couldn't replace index; retrying in 0.5s.
Questions:
Thanks for the feedback Graham. I'm using an SSD Drive with a C:& F:
I've been using the SSD probably at least two years and Norton since the early '90's. I've not run into the Indexing problem only as of late.
I should add, that after restarting Logos, all is proceeding as normal. It would be interesting if J.Eric who reported this same snag would send in his log files. Apparently, this is not limited to one user.
Apparently, this is not limited to one user.
No, you are not alone. There was an earlier post (forgot where) on this issue. It was no sense for me to add the "me too" on this post.
But I have worked around it until a fix can be made.
I've found that if I just exit Logos, the indexing would resume to completion. I don't have the logs because the issue only occurs when new or updates resources are added to the library.
Interesting. Not knowing how the mechanics of this program works, I still assumed it to be a snag within the Logos software. But since assumptions can too often be erroneous, I tossed the question out here to see what the Professionals thought.Thanks for the reply!
I've found that if I just exit Logos, the indexing would resume to completion
Agreed
The indexing algorithm was changed to speed it up between 7 and 8 so I guess there may be a bug lurking in there somewhere
An unhappy bug obviously!
Is anyone as of late been enjoying Indexing problems?
Not I.
Interesting that some are and others are not. I have two computers here & the problem remains on both. Homebase is also able to reproduce the same error.
It remains with me still
I'm beginning to feel better already in that I am not alone. As said, there is a snag somewhere in the software and it has been presented more than once to the development team. I asked the question to see how many others were enjoying the same problem.
From the vast amount of responses, one would conclude there is none. Obviously most are just too shy to bring it forward!
Thanks for the reply!
This is a bug in Logos 8.4 (and probably earlier releases) that will be fixed in an upcoming release.
Thanks for the heads up on that Bradley.
I also am having the same issue. Indexing stops at around 11 or 12%.
You can work around the problem by closing Logos, which will allow indexing to finish. (It may be good to wait a minute before starting it again, to make sure that indexing does get unblocked.)
This has been fixed in 8.4 SR-1.
Thanks for this Philana. Much appreciated.
