Backup Non-Indexed Search Functionality
I've emailed Bob and messaged Phil concerning this, but I also wanted to post something publicly offering a solution to the complaints I sent to Bob and Phil.
For a while now, I have ongoing issues with the reliability of the Logos Search Index and the Logos Indexer. This has happened on both a Windows PC and Mac, on Logos 6 and 7.
There are two times when the Logos Indexer and Logos Search Index decides to "go on vacation":
1. With point X releases of Logos (6.3, 6.4, etc.), especially on my Mac, the Logos Indexer would "stall" at 99% when indexing resource updates installed around the time of the point X release. I would then relaunch Logos, and the Logos Indexer would "stall" at 0%, and the only solution was performing a "Rebuild Index" and re-index my entire library to resolve the issue.
2. If I purchased a single book from Logos or Vyrso, or received a single free book from Logos or Vyrso, or a single book update was sent to my system, the Logos Indexer would also "stall" on 99%, and restarting Logos would then cause it to "stall" at 0%. The only solution was again another "Rebuild Index" and undergoing an re-index of my entire library.
The issue happened again to me tonight, and after multiple calls into Customer Service and Tech Support, it seems that the Logos Index is corrupting each time these scenarios occur. "Rebuild Index" even stalled tonight and didn't kick in for a while, but finally kicked in, and we're running it in Logging Mode so we can see what is going on with the indexing process.
My issue is tonight, I need to complete some research for school for a paper due next week, and now with the Logos index "on vacation", there's absolutely no way for me to complete my research, and I'm going to have to push myself to the core to get my research and writing done on time for this paper. My searches are too complex to run at Biblia.com. I may try the Logos Web App and see if I can perform any of my searches in them.
All of this is to say one thing. I cannot put my faith and trust in my Logos Library Index to reliably perform searches for me when I need mission critical searches. I love the fact that when the Logos Library Index is functioning, I can perform blazing fast searches. When it decides to "go on vacation" at mission critical times, I need rock solid reliability beyond what the Logos Library Index can provide me. I need a backup.
Here's what I need:
I need to be able to flip a switch in settings that says "Use Search Index" to "Off/No". With the flip of a switch, all of my searches in Logos, guides, etc., all continue to function exactly as if they would with the search index, but they're running in "manual" mode and taking longer to run. It make take 5, 10, or 15 minutes to run some searches (like the old Libronix days), but I could patiently wait for the searches to run and have them reliably run when the Logos Library Index decides to go "on vacation". When the index is OK, great, I'll enjoy the lightning fast searches. When it's not running properly, I can flip a switch and take a little longer to get my searches done, but have the confidence it'd work.
How hard would it be for Faithlife/Logos to implement such a feature in a future Logos release?
Thanks!
Nathan Parker
Visit my blog at http://focusingonthemarkministries.com
Comments
-
One More Thing: The reason I went to Bob and Phil about the issue was not so much the issue itself, but it was due to the level of service and support I received with Faithlife. When on the phone with Faithlife Customer Service and Support, I felt rushed each time I was on the phone with a rep and in essence, my issue was bothering them. The first time I was emailed a support article (that did not resolve my issue) and briefly sent off the phone. The second time I called in this evening when my issue was still not resolved, after the rep attempted a few things with my system, he assumed my issue was resolved and briefly sent me off the phone when again, it wasn't. Even Technical Support didn't hang on the phone enough to see if the Rebuild Index was actually taking or not (which it took a while before it finally took).
What has disappointed me more than the issue itself is the fact I feel that as a long time and loyal Faithlife customer with over 9,000 books and thousands of dollars in an investment plus multiple Faithlife subscriptions, that Logos Customer Service and Technical Support doesn't care about their customers. We're to jump on, get half-answered support, and jump off without truly ensuring our issues are resolved. This is not the kind of service and support I expect from a company such as Faithlife, and not from someone with my level of investment in the platform.
Nathan Parker
Visit my blog at http://focusingonthemarkministries.com
0 -
Nathan Parker said:
I need to be able to flip a switch in settings that says "Use Search Index" to "Off/No". With the flip of a switch, all of my searches in Logos, guides, etc., all continue to function exactly as if they would with the search index, but they're running in "manual" mode
I think I must misunderstand your request as it sounds like "search with search disabled" ... are you proposing that they support a parallel text only search?
I understand your frustration but it appears that your problem is isolated and thus more likely relating to something specific to your installation rather than a Faithlife issue per se. I am certainly frustrated that the need to reindex is so frequent and wish that its cause be tracked down. And it is certainly unfortunate that Tech Supports believes they have solved the problem when they have not ... please do report back when the actual cause has been successfully tracked down.
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0 -
MJ. Smith said:Nathan Parker said:
I need to be able to flip a switch in settings that says "Use Search Index" to "Off/No". With the flip of a switch, all of my searches in Logos, guides, etc., all continue to function exactly as if they would with the search index, but they're running in "manual" mode
I think I must misunderstand your request as it sounds like "search with search disabled" ... are you proposing that they support a parallel text only search?
I understand your frustration but it appears that your problem is isolated and thus more likely relating to something specific to your installation rather than a Faithlife issue per se. I am certainly frustrated that the need to reindex is so frequent and wish that its cause be tracked down. And it is certainly unfortunate that Tech Supports believes they have solved the problem when they have not ... please do report back when the actual cause has been successfully tracked down.
What I am suggesting is the ability to continue searching even if the index "goes on vacation". Basically non-indexed searching that lakes longer but still accomplishes searches even if the index is corrupted.
I am logging everything during this re-index and have a call into Bradley to see what can be done to pinpoint the issue so ultimately, Faithlife can work to better resolve the culprit in the future. However, with the issue happening on two totally different machines with two totally different operating systems and carrying over into new builds of Logos, something deep is going on, and the issue has been ongoing enough where I can no longer place confidence in the integrity of the index to reliably work when I need it to. I need a way to reliably search when the index corrupts so I do now have to continue losing hours of downtime due to library re-indexing when I need to spend that time in academic research.
Nathan Parker
Visit my blog at http://focusingonthemarkministries.com
0 -
Nathan Parker said:
My issue is tonight, I need to complete some research for school for a paper due next week, and now with the Logos index "on vacation", there's absolutely no way for me to complete my research, and I'm going to have to push myself to the core to get my research and writing done on time for this paper. My searches are too complex to run at Biblia.com. I may try the Logos Web App and see if I can perform any of my searches in them.
Work around is Program Setting:
Personally choose when to download and index resources plus program update.
Nathan Parker said:I need to be able to flip a switch in settings that says "Use Search Index" to "Off/No". With the flip of a switch, all of my searches in Logos, guides, etc., all continue to function exactly as if they would with the search index, but they're running in "manual" mode and taking longer to run. It make take 5, 10, or 15 minutes to run some searches (like the old Libronix days), but I could patiently wait for the searches to run and have them reliably run when the Logos Library Index decides to go "on vacation". When the index is OK, great, I'll enjoy the lightning fast searches. When it's not running properly, I can flip a switch and take a little longer to get my searches done, but have the confidence it'd work.
Suspect adding Text Search option (with Libronix 3 "text" search engine) would be easier to implement than "Use Search Index" setting plus allows choice to use index or not at any time:
Keep Smiling [:)]
0 -
Nathan Parker said:
My issue is tonight, I need to complete some research for school for a paper due next week, and now with the Logos index "on vacation", there's absolutely no way for me to complete my research, and I'm going to have to push myself to the core to get my research and writing done on time for this paper. My searches are too complex to run at Biblia.com. I may try the Logos Web App and see if I can perform any of my searches in them.
Work around is Program Setting:
Personally choose when to download and index resources plus program update.
Nathan Parker said:I need to be able to flip a switch in settings that says "Use Search Index" to "Off/No". With the flip of a switch, all of my searches in Logos, guides, etc., all continue to function exactly as if they would with the search index, but they're running in "manual" mode and taking longer to run. It make take 5, 10, or 15 minutes to run some searches (like the old Libronix days), but I could patiently wait for the searches to run and have them reliably run when the Logos Library Index decides to go "on vacation". When the index is OK, great, I'll enjoy the lightning fast searches. When it's not running properly, I can flip a switch and take a little longer to get my searches done, but have the confidence it'd work.
Suspect adding Text Search option (with Libronix 3 "text" search engine) would be easier to implement than "Use Search Index" setting plus allows choice to use index or not at any time:
Keep Smiling
Thanks for the tip to disable automatic updates. Huge help. I've disabled them and will only manually run updates when on a day I'm not doing mission critical research in Logos.
I like your suggestion about adding a "Text" search option as it would be simpler than disabling the index and allow me to dynamically use either. Two quick questions about it though:
1. Could "Text" search still search fields (largetext, heading, etc.)
2. Does guides, Factbook, etc., rely on the search index?
I do a lot of complex searches with largetext, heading, Bible NEAR Search Term, etc, as well as still use the guides somewhat. I'd like for all this functionality to work regardless of what's going on with the index.
Great pointers though and a huge help! Thanks for the info!
Nathan Parker
Visit my blog at http://focusingonthemarkministries.com
0 -
Nathan Parker said:
What I am suggesting is the ability to continue searching even if the index "goes on vacation".
Okay, I did understand. You are asking for a second search capability that excludes the indexes and thus must be a straight text search. I suspect that you would get more support for a regular expressions search as was in Logos 3. It would supplement the current search capabilities without being index dependent so it could also stand alone.
Nathan Parker said:I do a lot of complex searches with largetext, heading, Bible NEAR Search Term, etc, as well as still use the guides somewhat. I'd like for all this functionality to work regardless of what's going on with the index.
It can't ... that is like asking for bread made with no flour or flour substitute and no liquid. What you are asking for is essentially a character by character search which recognizes any tagging that is within the resources. The other option that could make sense would be to have a switch allowing one to use the search indices on the cloud that support web apps etc. That would maintain the functionality at the cost of the internet traffic time.
Nathan Parker said:2. Does guides, Factbook, etc., rely on the search index?
There are multiple search indexes which is why people are instructed to remove the index for a specific book, for bibles etc. While there probably are exceptions, I suspect it is safe to assume that they all use one or more indexes.
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0 -
MJ. Smith said:Nathan Parker said:
What I am suggesting is the ability to continue searching even if the index "goes on vacation".
Okay, I did understand. You are asking for a second search capability that excludes the indexes and thus must be a straight text search. I suspect that you would get more support for a regular expressions search as was in Logos 3. It would supplement the current search capabilities without being index dependent so it could also stand alone.
Nathan Parker said:I do a lot of complex searches with largetext, heading, Bible NEAR Search Term, etc, as well as still use the guides somewhat. I'd like for all this functionality to work regardless of what's going on with the index.
It can't ... that is like asking for bread made with no flour or flour substitute and no liquid. What you are asking for is essentially a character by character search which recognizes any tagging that is within the resources. The other option that could make sense would be to have a switch allowing one to use the search indices on the cloud that support web apps etc. That would maintain the functionality at the cost of the internet traffic time.
Nathan Parker said:2. Does guides, Factbook, etc., rely on the search index?
There are multiple search indexes which is why people are instructed to remove the index for a specific book, for bibles etc. While there probably are exceptions, I suspect it is safe to assume that they all use one or more indexes.
Good points and I've been thinking along those lines as well. Now that Logos is doing more with building out a web app for Logos Now/Logos Cloud customers (plus if Logos does ever allow partially downloaded libraries or book streaming from the Cloud), an index residing in the Cloud is likely to happen.
Being able to tap into that if my local index "goes on vacation" would be another work around to still allow for fast, powerful searches using the index, but using a backup index in the event of a local index corruption. The only limiting factor is the speed/reliability of my Internet connection, which while I had Internet reliability issues in the past, I've moved to an ISP and equipment that has generally been speedy and reliable.
So it is a very viable option you're recommending that'd certainly work.
Thanks!
Nathan Parker
Visit my blog at http://focusingonthemarkministries.com
0 -
Nathan Parker said:
I like your suggestion about adding a "Text" search option as it would be simpler than disabling the index and allow me to dynamically use either. Two quick questions about it though:
1. Could "Text" search still search fields (largetext, heading, etc.)
Suspect "Text" search of resources that have embedded search fields is feasible without indexing. Harder would be labels and tagging.
Nathan Parker said:2. Does guides, Factbook, etc., rely on the search index?
Yes
MJ. Smith said:Nathan Parker said:What I am suggesting is the ability to continue searching even if the index "goes on vacation".
Okay, I did understand. You are asking for a second search capability that excludes the indexes and thus must be a straight text search. I suspect that you would get more support for a regular expressions search as was in Logos 3.
+1 [Y] for regular expression search support, ideally with indexing. SQLite can use REGEXP in where clause => https://www.sqlite.org/lang_expr.html#regexp
Keep Smiling [:)]
0 -
Nathan Parker said:
I like your suggestion about adding a "Text" search option as it would be simpler than disabling the index and allow me to dynamically use either. Two quick questions about it though:
1. Could "Text" search still search fields (largetext, heading, etc.)
Suspect "Text" search of resources that have embedded search fields is feasible without indexing. Harder would be labels and tagging.
Nathan Parker said:2. Does guides, Factbook, etc., rely on the search index?
Yes
MJ. Smith said:Nathan Parker said:What I am suggesting is the ability to continue searching even if the index "goes on vacation".
Okay, I did understand. You are asking for a second search capability that excludes the indexes and thus must be a straight text search. I suspect that you would get more support for a regular expressions search as was in Logos 3.
+1
for regular expression search support, ideally with indexing. SQLite can use REGEXP in where clause => https://www.sqlite.org/lang_expr.html#regexpKeep Smiling
Thanks for the info! I rely more on embedded fields vs tagging. Sometimes I venture into tagging, but embedded fields much of the time gives me what I need back.
+1 here for Regular Expression searches as well.
Thanks!
Nathan Parker
Visit my blog at http://focusingonthemarkministries.com
0 -
Nathan Parker said:
... the Logos Indexer would "stall" at 99% ...
Replicated Logos 7.1 SR-2 showing 99 % done for indexing (on OS X 10.10.5). Indexer log showed indexing had completed over an hour earlier. Quit Logos 7.1 SR-2 and relaunch was OK.
When "stalled" suggest using Activity Monitor to see if Logos Indexer is running.
FYI: personally have logging always enabled so can look at log files.
Keep Smiling [:D]
0 -
Nathan Parker said:
... the Logos Indexer would "stall" at 99% ...
Replicated Logos 7.1 SR-2 showing 99 % done for indexing (on OS X 10.10.5). Indexer log showed indexing had completed over an hour earlier. Quit Logos 7.1 SR-2 and relaunch was OK.
When "stalled" suggest using Activity Monitor to see if Logos Indexer is running.
FYI: personally have logging always enabled so can look at log files.
Keep Smiling
Thanks for the info. My MacBook Pro has died, so my Surface Book is the machine I'm working off of at the moment (that is also having the stalling issue, so it's not limited to Mac).
When "stalled", Task Manager does show the Logos Indexer as running.
I had logging mode enabled during the rebuild index. Is there a way to permanently turn on Logging mode in Logos for Windows?
Thanks!
Nathan Parker
Visit my blog at http://focusingonthemarkministries.com
0 -
Nathan Parker said:
Is there a way to permanently turn on Logging mode in Logos for Windows?
Step 4 => https://www.logos.com/support/windows/report-problem includes a script that sets a registry key to always enable logging.
Keep Smiling [:)]
0 -
Nathan Parker said:
Is there a way to permanently turn on Logging mode in Logos for Windows?
Step 4 => https://www.logos.com/support/windows/report-problem includes a script that sets a registry key to always enable logging.
Keep Smiling
Thanks. Since it clears the clogs after each session, should I archive my logs after each session in case anyone needs a history of them?
Nathan Parker
Visit my blog at http://focusingonthemarkministries.com
0 -
Nathan Parker said:
Since it clears the clogs after each session, should I archive my logs after each session in case anyone needs a history of them?
When actively troubleshooting issue(s), can be prudent to archive after closing Logos.
Keep Smiling [:)]
0 -
Nathan Parker said:
Since it clears the clogs after each session, should I archive my logs after each session in case anyone needs a history of them?
When actively troubleshooting issue(s), can be prudent to archive after closing Logos.
Keep Smiling
Sounds good. I'll work on getting this enabled and begin extensive monitoring.
Nathan Parker
Visit my blog at http://focusingonthemarkministries.com
0 -
Nathan Parker said:
I need to be able to flip a switch in settings that says "Use Search Index" to "Off/No". With the flip of a switch, all of my searches in Logos, guides, etc., all continue to function exactly as if they would with the search index, but they're running in "manual" mode and taking longer to run. It make take 5, 10, or 15 minutes to run some searches (like the old Libronix days), but I could patiently wait for the searches to run and have them reliably run when the Logos Library Index decides to go "on vacation". When the index is OK, great, I'll enjoy the lightning fast searches. When it's not running properly, I can flip a switch and take a little longer to get my searches done, but have the confidence it'd work.
What we'll do instead is fix the problem that causes your index to "go on vacation". This should not be happening, so instead of adding a complicated setting to work around it, we'd prefer to address the underlying problem.
This may require multiple sets of log files from when the problem occurs, so please enable logging and upload logs from a session when you experience the problem.
0 -
Nathan Parker said:
I need to be able to flip a switch in settings that says "Use Search Index" to "Off/No". With the flip of a switch, all of my searches in Logos, guides, etc., all continue to function exactly as if they would with the search index, but they're running in "manual" mode and taking longer to run. It make take 5, 10, or 15 minutes to run some searches (like the old Libronix days), but I could patiently wait for the searches to run and have them reliably run when the Logos Library Index decides to go "on vacation". When the index is OK, great, I'll enjoy the lightning fast searches. When it's not running properly, I can flip a switch and take a little longer to get my searches done, but have the confidence it'd work.
What we'll do instead is fix the problem that causes your index to "go on vacation". This should not be happening, so instead of adding a complicated setting to work around it, we'd prefer to address the underlying problem.
This may require multiple sets of log files from when the problem occurs, so please enable logging and upload logs from a session when you experience the problem.
Sounds good Bradley. Quick question: Do you want me to enable permanent logging on Logos (I can only test on Logos for Windows at the moment since my Mac is no more), and when I encounter an issue, do you want me to upload logs as attachments to this blog post so we can keep everything together?
I need to purchase a single textbook for next semester, so I may proceed with doing it one day after running Update Now and ensuring that's the only book that'll download and see how it goes. I'll wait and do this after I finish some of my school research first though. :-)
Thanks!
Nathan Parker
Visit my blog at http://focusingonthemarkministries.com
0 -
Nathan Parker said:
Sounds good Bradley. Quick question: Do you want me to enable permanent logging on Logos (I can only test on Logos for Windows at the moment since my Mac is no more), and when I encounter an issue, do you want me to upload logs as attachments to this blog post so we can keep everything together?
Yes, that sounds ideal.
0 -
Nathan Parker said:
Sounds good Bradley. Quick question: Do you want me to enable permanent logging on Logos (I can only test on Logos for Windows at the moment since my Mac is no more), and when I encounter an issue, do you want me to upload logs as attachments to this blog post so we can keep everything together?
Yes, that sounds ideal.
Great. Logging is enabled. I'll continue running testing and report back when I get issues.
Thanks!
Nathan Parker
Visit my blog at http://focusingonthemarkministries.com
0 -
OK, I was able to duplicate the issue again tonight. A single book from Logos.com was downloaded into my library.
The first set of log files was taken when the Logos Indexer stalled at 99%, causing me to force quit the Logos Indexer.
The second set of log files was taken when I restarted Logos, and the Logos Indexer stalled at 0%, again causing me to force quit the Logos Indexer.
I haven't relaunched Logos since then.
Let me know if I need to perform any additional tests. I won't need access to Logos until Wednesday, so if a Rebuild Index is required once more, I can perform it Tuesday.
I am on 7.2 I believe (whichever version hit last week).
Nathan Parker
Visit my blog at http://focusingonthemarkministries.com
0 -
Here is the problem from the log:
2016-11-21 22:10:59.6968 13 Info FileSystemIndexInfo Replacing C:\Users\parke\AppData\Local\Logos\Data\0j0xbc15.5uh\LibraryIndex/index with C:\Users\parke\AppData\Local\Logos\Data\0j0xbc15.5uh\LibraryIndex/index-build
2016-11-21 22:11:00.6328 13 Error FileSystemIndexInfo Couldn't replace 'C:\Users\parke\AppData\Local\Logos\Data\0j0xbc15.5uh\LibraryIndex\index.idx' with 'C:\Users\parke\AppData\Local\Logos\Data\0j0xbc15.5uh\LibraryIndex\index-build.idx'; rolling back replace operation.
2016-11-21 22:11:00.7531 13 Warn LibraryIndex Couldn't replace index; retrying in 30.0s.
2016-11-21 22:11:31.2402 13 Info FileSystemIndexInfo Replacing C:\Users\parke\AppData\Local\Logos\Data\0j0xbc15.5uh\LibraryIndex/index with C:\Users\parke\AppData\Local\Logos\Data\0j0xbc15.5uh\LibraryIndex/index-build
2016-11-21 22:11:31.8138 13 Error FileSystemIndexInfo Couldn't replace 'C:\Users\parke\AppData\Local\Logos\Data\0j0xbc15.5uh\LibraryIndex\index.idx' with 'C:\Users\parke\AppData\Local\Logos\Data\0j0xbc15.5uh\LibraryIndex\index-build.idx'; rolling back replace operation.
2016-11-21 22:11:31.8243 13 Warn LibraryIndex Couldn't replace index; retrying in 30.0s.The indexer will keep sitting at 99% until it can replace your index (at which point it will be done).
The most likely causes are:
- Some program has the index open
- The index is read-only
- The file permissions on the index prevent the indexer from replacing it
We can probably rule out the last two, since that would prevent "rebuild index" working, and it seems like you've done that in the past.
It's possible that Logos 7 is holding the index open. This is also unlikely, since it's designed to close the index as soon as a search finishes, so that it can be replaced if necessary. But just to rule it out, try closing Logos 7 the next time the Indexer gets to 99%. You should be able to monitor its progress from the taskbar notification area icon. If it doesn't disappear right away, then it's probably still trying to replace the file (and Logos wasn't the problem).
Are you running a continuous backup program such as Crashplan, Backblaze or Carbonite? If so, and if you haven't excluded the Logos data folder, then it could well be holding on to the index files and preventing the indexer from completing. Add "C:\Users\parke\AppData\Local\Logos\Data\0j0xbc15.5uh" to the list of excluded backup folders. It may also be worth adding it to your AV exclusion list. (There are no executable files stored in that folder, so there shouldn't be anything to scan.)
If that's still not helping, you could download Process Explorer to collect further diagnostics. https://technet.microsoft.com/en-us/sysinternals/processexplorer.aspx
Run it, then choose File > Show Details for All Processes
When it restarts, choose Find > Find Handle or DLL, enter "index.idx" and click Search. Is any process listed? You can paste a scrednshot here. Also search for "index-build.idx" and see if that finds any (different) processes.
0 -
Here is the problem from the log:
2016-11-21 22:10:59.6968 13 Info FileSystemIndexInfo Replacing C:\Users\parke\AppData\Local\Logos\Data\0j0xbc15.5uh\LibraryIndex/index with C:\Users\parke\AppData\Local\Logos\Data\0j0xbc15.5uh\LibraryIndex/index-build
2016-11-21 22:11:00.6328 13 Error FileSystemIndexInfo Couldn't replace 'C:\Users\parke\AppData\Local\Logos\Data\0j0xbc15.5uh\LibraryIndex\index.idx' with 'C:\Users\parke\AppData\Local\Logos\Data\0j0xbc15.5uh\LibraryIndex\index-build.idx'; rolling back replace operation.
2016-11-21 22:11:00.7531 13 Warn LibraryIndex Couldn't replace index; retrying in 30.0s.
2016-11-21 22:11:31.2402 13 Info FileSystemIndexInfo Replacing C:\Users\parke\AppData\Local\Logos\Data\0j0xbc15.5uh\LibraryIndex/index with C:\Users\parke\AppData\Local\Logos\Data\0j0xbc15.5uh\LibraryIndex/index-build
2016-11-21 22:11:31.8138 13 Error FileSystemIndexInfo Couldn't replace 'C:\Users\parke\AppData\Local\Logos\Data\0j0xbc15.5uh\LibraryIndex\index.idx' with 'C:\Users\parke\AppData\Local\Logos\Data\0j0xbc15.5uh\LibraryIndex\index-build.idx'; rolling back replace operation.
2016-11-21 22:11:31.8243 13 Warn LibraryIndex Couldn't replace index; retrying in 30.0s.The indexer will keep sitting at 99% until it can replace your index (at which point it will be done).
The most likely causes are:
- Some program has the index open
- The index is read-only
- The file permissions on the index prevent the indexer from replacing it
We can probably rule out the last two, since that would prevent "rebuild index" working, and it seems like you've done that in the past.
It's possible that Logos 7 is holding the index open. This is also unlikely, since it's designed to close the index as soon as a search finishes, so that it can be replaced if necessary. But just to rule it out, try closing Logos 7 the next time the Indexer gets to 99%. You should be able to monitor its progress from the taskbar notification area icon. If it doesn't disappear right away, then it's probably still trying to replace the file (and Logos wasn't the problem).
Are you running a continuous backup program such as Crashplan, Backblaze or Carbonite? If so, and if you haven't excluded the Logos data folder, then it could well be holding on to the index files and preventing the indexer from completing. Add "C:\Users\parke\AppData\Local\Logos\Data\0j0xbc15.5uh" to the list of excluded backup folders. It may also be worth adding it to your AV exclusion list. (There are no executable files stored in that folder, so there shouldn't be anything to scan.)
If that's still not helping, you could download Process Explorer to collect further diagnostics. https://technet.microsoft.com/en-us/sysinternals/processexplorer.aspx
Run it, then choose File > Show Details for All Processes
When it restarts, choose Find > Find Handle or DLL, enter "index.idx" and click Search. Is any process listed? You can paste a scrednshot here. Also search for "index-build.idx" and see if that finds any (different) processes.
Thanks for following up!
Generally when I index resources, I go ahead and close Logos until the indexing is finished, then I re-launch Logos to ensure everything takes. So Logos shouldn't be the culprit interfering with the Logos Indexer (I only kept it running this time to ensure the indexing issue was captured in the logs).
The culprit could likely be my online backup tool: CrashPlan. While I have CrashPlan set to only backup changes once and day and not backup "real time" changes, I have noticed it's been trying to backup some files in the Logos Index folder. Should I go ahead and proceed with excluding that file path you gave me above in CrashPlan and see what happens?
I can also exclude it from my AV as well. It's Webroot, so it's all cloud-based, but wouldn't hurt to exclude it there just to be safe.
I'm curious, why does it happen with just a single book and not multiple books? That one is a little bit of a head scratcher for me.
Thanks!
Nathan Parker
Visit my blog at http://focusingonthemarkministries.com
0 -
Update: I just excluded that directory in CrashPlan, as well as Windows Defender and Malwarebytes (neither are running in real time mode, but occasionally I'll manually scan with them, so just adding the exclusion to be cautious).
I can't get the exclusion added to Webroot yet. Got a message into Webroot asking about it (if any Logos users know how to do this, that'd be great).
I'll rebuild Index today to be safe so I know it'll be functional this week when I need to do research, then I'll continue monitoring it to see if my issue is resolved with future book installs or let you know if it surfaces again.
I also disabled auto updates so I can download books and updates on days when mission critical work isn't going on.
Thanks again!
Nathan Parker
Visit my blog at http://focusingonthemarkministries.com
0 -
Nathan Parker said:
I'll rebuild Index today to be safe
Please don't.
The indexer already knows it needs to merge the resource you recently updated/purchased into the main index. It'll keep attempting to do that until it succeeds.
We want to change configuration settings on your computer until we find one that lets it succeed. It's possible that changing CrashPlan will already have fixed it. If you run Logos and the indexer doesn't start automatically, that's a very good sign. Please upload the latest LogosIndexer.log file and we can confirm that it successfully updated your index. And if it did, there's no need to waste time reindexing!
0 -
Nathan Parker said:
I'll rebuild Index today to be safe
Please don't.
The indexer already knows it needs to merge the resource you recently updated/purchased into the main index. It'll keep attempting to do that until it succeeds.
We want to change configuration settings on your computer until we find one that lets it succeed. It's possible that changing CrashPlan will already have fixed it. If you run Logos and the indexer doesn't start automatically, that's a very good sign. Please upload the latest LogosIndexer.log file and we can confirm that it successfully updated your index. And if it did, there's no need to waste time reindexing!
Oops, already rebuilt the index before I heard back from you.
The good news is after excluding it from CrashPlan, the rebuild index went WAY faster than it normally does. It zipped through it fairly fast compared to what it used to do. CrashPlan is also seeming to be faster at backups too. :-)
I also downloaded the SR so I'm on the latest build of Logos.
What I can do now is randomly grab another single book (maybe get a free book off of Vyrso.com when there's one on there to grab), unlock it, then run a download and index and see what happens. If it checks out, we're in the clear.
Nathan Parker
Visit my blog at http://focusingonthemarkministries.com
0 -
I also found out from Webroot Support I cannot exclude folders in Webroot at the moment. Should I exclude each of the files in there, or should I just leave things alone with Webroot setting concerning this? Thanks!
Nathan Parker
Visit my blog at http://focusingonthemarkministries.com
0 -
Let's just leave things alone with Webroot. I know other customers are using Webroot, and they haven't been reporting any indexing problems.
(Although it had caused its own share of problems in the past:
- https://community.logos.com/forums/p/106829/741596.aspx#741596
- https://community.logos.com/forums/p/44373/330363.aspx#330363
- https://community.logos.com/forums/p/42487/316437.aspx#316437
My personal recommendation is to avoid third-party A/V and just stick with the built-in Windows Defender in Windows 10; it's free and effective.)
0 -
Let's just leave things alone with Webroot. I know other customers are using Webroot, and they haven't been reporting any indexing problems.
(Although it had caused its own share of problems in the past:
- https://community.logos.com/forums/p/106829/741596.aspx#741596
- https://community.logos.com/forums/p/44373/330363.aspx#330363
- https://community.logos.com/forums/p/42487/316437.aspx#316437
My personal recommendation is to avoid third-party A/V and just stick with the built-in Windows Defender in Windows 10; it's free and effective.)
Sounds good. I guess what I'll try now is get my hands on a single book, download and index it, and see what happens.
As for Webroot, it's a free trial since I purchased this machine at Best Buy. Still deciding what I want to do when my trial runs out. :-)
Nathan Parker
Visit my blog at http://focusingonthemarkministries.com
0 -
I think we're good to go now after excluding Logos from CrashPlan. I found a single free book on Vyrso.com and downloaded it just to test things out.
Indexing completed successfully from what I've seen. Restarted Logos, no indexing messages. All checked out clean.
Here's the logs from this incident if you want to see them just to see if all did check out clean from logging standpoint.
Quick Question: Should I go ahead and leave logging permanently enabled, that way if there are future issues I encounter with Logos, I'll be able to collect and upload logs instantly without having to go back through and re-enable logging?
Thanks!
Nathan Parker
Visit my blog at http://focusingonthemarkministries.com
0 -
Nathan Parker said:
I think we're good to go now after excluding Logos from CrashPlan. I found a single free book on Vyrso.com and downloaded it just to test things out.
Indexing completed successfully from what I've seen. Restarted Logos, no indexing messages. All checked out clean.
Here's the logs from this incident if you want to see them just to see if all did check out clean from logging standpoint.
Everything looks good in the logs to me; it seems like CrashPlan was probably the problem.
Nathan Parker said:Quick Question: Should I go ahead and leave logging permanently enabled, that way if there are future issues I encounter with Logos, I'll be able to collect and upload logs instantly without having to go back through and re-enable logging?
Yes, having logging always enabled does make it easier to diagnose any future issues. (There is a small amount of overhead from enabling logging, but if you have a recent fast computer, it's probably not noticeable.)
0 -
Nathan Parker said:
I think we're good to go now after excluding Logos from CrashPlan. I found a single free book on Vyrso.com and downloaded it just to test things out.
Indexing completed successfully from what I've seen. Restarted Logos, no indexing messages. All checked out clean.
Here's the logs from this incident if you want to see them just to see if all did check out clean from logging standpoint.
Everything looks good in the logs to me; it seems like CrashPlan was probably the problem.
Nathan Parker said:
Quick Question: Should I go ahead and leave logging permanently enabled, that way if there are future issues I encounter with Logos, I'll be able to collect and upload logs instantly without having to go back through and re-enable logging?
Yes, having logging always enabled does make it easier to diagnose any future issues. (There is a small amount of overhead from enabling logging, but if you have a recent fast computer, it's probably not noticeable.)
Sounds good. Let's hope it was. So far so good. :-)
I'll leave logging on as well. My machine has 16GB RAM in it and all SSD, so I'm not noticing any major performance issues with it enabled. Logos is still running perfectly fine with it, so might as well leave it running for faster troubleshooting measures.
Thanks again for your assistance!
Nathan Parker
Visit my blog at http://focusingonthemarkministries.com
0
said:
