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.
If I'm following you correctly, mine is opening different. It starts with the Logos Startup Window then the 'preparing library' which sometimes takes 20 seconds before the blank page shows up followed by the layout page.
That this is happening on two computers here, apparently the programmers written something different into the program for it to open this way. This began right after the Indexing problem was fixed.
If I'm following you correctly, mine is opening different. It starts with the Logos Startup Window then the 'preparing library'
Your initial description is the same as mine (with "Prep Library") and your log doesn't show anything different to my log. I only see the Startup (Sign-in) window when CTRL is held.
So am I correct Dave in assuming this is something new written into the program?
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
I don't see anything obviously wrong in your logs. I think what has happened is that some things during startup got rearranging, causing the message to display earlier in the process than it used to. I believe the overall time to startup has not significantly changed, but the message will show up earlier.
I had a very slow start today with no obvious reason as to why this should occur. I had purchased two books since the previous restart, but that's all.
StartupUtility Startup step: StartServices was timed at 2m 18.1s. DoFirstSync took an additional 46.80s, which contributed to:
Finished startup at 3m 14.6s.
5164.Logos.log
This is on an i7 with buckets of RAM and a decent SSD.
According to those logs, the main window was shown after 5.7s. That seems pretty reasonable to me.
And that's the way it will work Mark, at times. There's been times "preparing your library" has shown close to 20 seconds.The near 20 second thing is not normal for this computer. And I think the reason it was showing faster in the logs you read, is that I had started it up several times without rebooting the machine, after having deleted the file mentioned earlier on in this thread.
But whatever, this "preparing the library" is a new thing on the block having started showing about two weeks back. There might have been a once in a blue moon this would show but not every single time as it is now. And that others are noticing this has it not singled down to just myself.
Do you feel there has been something added to the programming or is it a glitch or do you feel this is going to be the norm?
Despite the text of this log message, it's not really a useful measure of how quick the application is starting up.
However, this is:
Showing main window at 194.294 seconds.
It looks like your preferences are set to restore your last layout from any installation. This forces the application to wait until sync completes before starting up. Set this preference to last local layout to eliminate this wait.
Unfortunately, there's not enough information in the log to determine exactly what is causing the additional time. I assume that subsequent restarts don't exhibit the same slow startup times?
I assume that subsequent restarts don't exhibit the same slow startup times?
Nowhere near as bad. But with most recent layout still set to any, a restart just now took 35.483s by your metric (the most recent layout was blank). There's a lot of general slowness (e.g. in caching collections), too, even though there's no disk activity and minimal CPU activity from other apps. I long suspected that metadata updates cause collections to keep caching because caching isn't paused during the update. If so, that might account for some of the issue.
2476.Logos.log
Changing to a local layout reduced that to 12.898s and then to 11.54s, which still feels fairly slow, especially when all the files should be cached in RAM because I closed and restarted immediately, and there's nothing to sync with. I checked some old logs at random. 7s or 8s is normal for me, although it's not difficult to find occasions where Logos has taken 30s or longer to start. One took 275s (4½ minutes) because of a massive sync! 0211.Logos (2019_02_06 11_53_20 UTC).log
That's helpful to now. It was set to "Most recent layout - any". I've changed it now.
Unfortunately, there's not enough information in the log to determine exactly what is causing the additional time.
I don't know whether it's relevant, but I did notice that one of the books I purchased didn't show up in the notification menu, and there were some errors about that book in the logs (though they didn't seem relevant to the slowness). This is happened during the original 194s log I first reported.
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.
