Your Library is Indexing - Stuck at 0%
L8 downloaded a dozen or so new resources this evening. I see a blue circle with a "1" in the upper right (as I've seen for years whenever new resources are being added). BUT... it stays stuck on "Your library is indexing 0%" There is no blue LOGOS up in the system bar at the top showing index progress. Just a blue "1" stuck on the upper right LOGOS screen saying it is indexing at 0%.
Saw this for 45 minutes. Restarted LOGOS. Same thing. Any suggestions? Thx. (Oh, iMac Mojave).
Comments
-
Same here...we might have the same problem Steve
Keith Pang, PhD Check out my blog @ https://keithkpang.wixsite.com/magnifyingjesus
0 -
On Windows, it appears to be working.
0 -
Yes, something updated/downloaded tonight. Seems to reindexing everything, taking awhile.
On Windows 10, but is slowly progressing
0 -
I spoke too soon. Stuck at 13% on Windows.
0 -
I've gotten this a few times with 8 on Windows. My solution has been to use a command to reindex some part of my library--either Rebuild Bible Index or a specific resource--and that has always cleared it up.
“The trouble is that everyone talks about reforming others and no one thinks about reforming himself.” St. Peter of Alcántara
0 -
I've just started the update here on Windows (42 resources, 88.7MB download). Waiting to see what happens... Does anyone have logs?
EDIT: Indexing complete without problems here. Latest beta, L8.2b1. Windows.
0 -
Randy W. Sims said:
I've just started the update here on Windows (42 resources, 88.7MB download). Waiting to see what happens... Does anyone have logs?
EDIT: Indexing complete without problems here. Latest beta, L8.2b1. Windows.
Windows logs from laptop. I'm currently trying SinNomine's method on my desktop. Both machines are Windows 10.
0 -
So, launched L8 on my MacBook. It indexed as it should, all the way to 100%.
Decided to buy a book. Launched the desktop L8. The book downloaded. Started indexing showing 0%.. both blue circles showing (system bar at top, and upper right of the Logos desktop. Then the blue circle on the system bar at the top vanished after 1-2 minutes and the blue circle on L8 desktop stays visible stuck with a "1" and "Your library is indexing (0%).
0 -
Steve Farson said:
Decided to buy a book. Launched the desktop L8. The book downloaded. Started indexing showing 0%.. both blue circles showing (system bar at top, and upper right of the Logos desktop. Then the blue circle on the system bar at the top vanished after 1-2 minutes and the blue circle on L8 desktop stays visible stuck with a "1" and "Your library is indexing (0%).
Please provide logs. See instructions in my signature line.
macOS, iOS & iPadOS |Logs| Install
Choose Truth Over Tribe | Become a Joyful Outsider!0 -
Thx, Here they are... archive and sampling...
0 -
-
macOS, iOS & iPadOS |Logs| Install
Choose Truth Over Tribe | Become a Joyful Outsider!0 -
Steve Farson said:
Steve
I recommend you kill the Indexer (if running), exit Logos and delete this folder - /Users/sfarson/Library/Application Support/Logos4/Data/wocrkj8v.9la/BibleIndex. Then restart Logos.
This advice only applies to Steve.
Dave
===Windows 11 & Android 13
0 -
Erwin Stull, Sr. said:
Windows logs from laptop. I'm currently trying SinNomine's method on my desktop. Both machines are Windows 10.
Laptop logs are OK. Need logs from desktop, else you are working in the dark!
Dave
===Windows 11 & Android 13
0 -
I am on stable Mac and had the same problem starting about 24 hours ago.
What I did is reindex the bible index and now Logos is working fine.
0 -
HansK said:
What I did is reindex the bible index and now Logos is working fine.
That worked for you, but there is also a Library index! And there could be other causes; which is why we need Logs.
Dave
===Windows 11 & Android 13
0 -
Thanks everyone. Back from a day away from the PC. Before leaving I called tech support. They had me "rebuild index" and this seems to have cured the situation. Good thing I had stuff to do away from home. I left when the index was 5% complete and that took almost 1/2 an hour (bunch of books + six year old iMac = slow rebuild)!
Blessings to all at this time of Advent... who has, who is, who is to come. Amen.
0 -
I did a Rebuild Index command and it seems to be working now. Thanks guys!
Keith Pang, PhD Check out my blog @ https://keithkpang.wixsite.com/magnifyingjesus
0 -
Dave Hooton said:Erwin Stull, Sr. said:
Windows logs from laptop. I'm currently trying SinNomine's method on my desktop. Both machines are Windows 10.
Laptop logs are OK. Need logs from desktop, else you are working in the dark!
Hi Dave; Both machines had the same issue (stuck at 13%), so I posted the logs from the laptop which I had not played around with (I figured the logs would be more accurate). SinNomine's method of rebuilding the bible index worked on the desktop. The issue on the laptop disappeared. Not sure what happened, but it's gone. Both machines are as normal now. Thanks for the assistance.
0 -
FWIW, three Macs here in my home, (A MacBook (2018) and Two iMacs (2012 and 2018), Mojave, running L8 (8.1.0.0016) have all had the index hang. Needed to rebuild index for all three. No indexing issue with the Win10 PC.
0 -
Not to rain on the parade of everyone who has used my method successfully so far, but if the cause for all of us is the same... the problem will return. Soon. And repeatedly. My solution temporarily cures the symptom; it doesn't treat the disease. That's why I do not recommend Rebuild Index on the entire library. Rebuilding the index for any single specific resource (or subset thereof) will do the job just as well and much, much faster.
“The trouble is that everyone talks about reforming others and no one thinks about reforming himself.” St. Peter of Alcántara
0 -
If it happens again, what subset "rebuild" command should I use? Is there something like "Rebuild Bibles?" Thanks.
0 -
SineNomine said:
Rebuilding the index for any single specific resource (or subset thereof) will do the job just as well and much, much faster.
And how do you do that?
Myke Harbuck
Lead Pastor, www.ByronCity.Church
Adjunct Professor, Georgia Military College0 -
Myke Harbuck said:SineNomine said:
Rebuilding the index for any single specific resource (or subset thereof) will do the job just as well and much, much faster.
And how do you do that?
In the Command Box, type: Reindex {Abbreviated Title | Resource Id}
re-indexes a single resource e.g. reindex ESV; reindex LLS:1.0.710
0 -
It appears I am having the same problem on my MacBook Pro with Library Indexing stuck at 0%. I've never had this problem before but it started sometime in the last couple of days.
0 -
So if I buy some resources and the indexer hangs, and I type something like "Reindex ESV," what does this get me? I can see how it could stop the hung indexer, but I guess the new resources will be unindexed?
0 -
Leon, I called tech support today making sure they were going to make an official case out of this. They have seen this thread and the log files that have been captured.
0 -
I have a Macbook Pro and so I was glad that the solution was not Mac or Windows specific. I was able to use this link to learn more about how to rebuild the library books index and all other indexes with this link:
https://wiki.logos.com/Logos_8_Commands
I typed Option+Command+L for my Mac (Alt+D for PC) to get quick access to the Command Bar.
Then in the command line, I entered: Rebuild Index
Then clicked on the green GO button.
I hope this helps others who may run into the same problem, it was easy to fix, just need to patiently wait for the index rebuilds.
0 -
Steve Farson said:
So if I buy some resources and the indexer hangs, and I type something like "Reindex ESV," what does this get me? I can see how it could stop the hung indexer, but I guess the new resources will be unindexed?
Without logs, how do you know that the Indexer hung on a resource. How will you know which resource? So you are correct in thinking that reindexing a random resource will not get you anywhere (especially when indexing restarts and it hangs again!).
In the current context (indexer stuck at 0% on a Mac with Logos 8), the rebuild index command appears to provide a solution, and you could have a working system within a number of hours. If it doesn't work, then start a new thread and provide logs.
Dave
===Windows 11 & Android 13
0
