I've noticed as of late, that each time Logos is started, I get the "preparing your library - this might take a few minutes." This didn't open up like this before but now I notice it does. Is this a new normal?
It's can happen, but for how long (a few seconds)? Some logs may help.
Logos would open between 4-5 seconds. There's times right now I'm seeing it go high as twenty seconds.
I'm going to give you the logs and you can look and see if there's anything off kilter. Thanks Dave.
3034.LogosSetup.log
4718.Logos.log
2161.LogosError.log
3617.LogosIndexer.log
Looks similar to mine in Logos.log ie. "Startup window" followed by "main window" (blank) and then "finished startup" (showing Layout/home page). And this is similar to starting with CTRL key, when the proper Startup window appears.
For some reason, you application seems to be stuck trying to download what I suspect are resources that you have hidden. Try deleting this file and see if it helps.
E:\Logos\Data\rragwelx.av3\CloudResourceManager\CloudResources.db
Ok, before I go and do something totally stupid, is it the 'CloudResources db' only that I delete?
I deleted the above file after closing Logos but it doesn't change anything. I notice it recreates the same file again.
Ok, before I go and do something totally stupid, is it the 'CloudResources db' only that I delete? I deleted the above file after closing Logos but it doesn't change anything. I notice it recreates the same file again.
Correct, just that file. Another log file would be useful now that you've hopefully cleared up that one problem.
This is still happening for me too, and I still haven't gotten satisfaction after deleting files I was instructed to (including the abovementioned CloudResources.db) and reposting logs afterwards twice:
https://community.logos.com/forums/t/181099.aspx
Still waiting for a follow-up answer from Faithlife.
That you Rosie are experiencing the same thing implies this is a flaw in the programming but maybe I'd be wiser leaving that with the Techs.
Andrew, what particular log file would you be asking for? Did you see the ones I sent up earlier?
The logos.log files, same as before, but now that we've changed something it'll be good to get another log file to compare.
I didn't see anything that stood out in your logs. It's likely that something has happened that has generally slowed down startup, but it will require more investigation for us to track down.
I'm seeing the same issue. I don't know that my startup is taking any longer than before I saw the message start appearing, it's almost like something in the program changed that makes the dialog appear sooner than before so now it happens on every startup.
Andrew, what particular log file would you be asking for? Did you see the ones I sent up earlier? The logos.log files, same as before, but now that we've changed something it'll be good to get another log file to compare.
Take a look at these Andrew, but that others are experiencing the same issues, shows this to be originating in Logos itself. As stated earlier, this began right after the "Indexing" issue was fixed.
Here are my log files I think you'll want to look at. Let me know what you find.
4527.Logos.log
0871.LogosError.log
5277.LogosIndexer.log
4111.LogosSetup.log
Still waiting for a follow-up answer from Faithlife. I didn't see anything that stood out in your logs. It's likely that something has happened that has generally slowed down startup, but it will require more investigation for us to track down.
Here's another log now that I've updated to Logos 8.5. I made sure to shut down and restart Logos and let all the updates and indexing complete several times (at least 3 or 4) before it finally had nothing more to download or index, and then I restarted it again one more time just for good measure, and yet it is still saying "preparing your library" every time at startup.
1588.Logos.log
From "UpdatePipelineManager Initializing update pipeline stages" to "UpdatePipelineManager Finished checking for updates" takes from 22:27:13.8177 to 22:31:46.3653, over 4 and 1/2 minutes! That's the bottleneck.
The software isn't ready to use for real until this bottleneck is through. It's a pain in the butt. Every single time I start it up.
Oh wait. I just started it one more time and it didn't do that. This time it took only 26 seconds. See if you can tell what's the difference.
1526.Logos.log
And now it seems to finally be starting up in a reasonable amount of time. This was achieved only after restarting at least four times, though. This is still pretty troubling.
