Logos opened fine on my computer before, but now it takes forever to open. Can someone take a look at the log files and tell me if they see something amiss?
Thank you.
4718.Logos Log Files.zip
Hello Timothy, and welcome.
The error logs you have uploaded say that Logos recovered from file corruption on 15 February. That appears to be the same day you updated to Logos 7. There are also a few errors from earlier that day, when you were still running Logos 6.
With that in mind, I would suggest two things:
If that doesn't work, come back to us.
Please note I made an error in my earlier message, and have now corrected it.
Deleting the ResourceManager files did help - thank you for your input!
With Logos closed, delete the file E:\Users\Tim\AppData\Local\Logos\Data\crnzdf0o.3tg\ResourceManager\ResourceManager.db and ResourceManager.db-journal then load Logos.
Can these two files also be safely deleted on a Mac?
It would be better to know your problem, before assuming this is a fix-all. Please start a new thread and upload log files.
Hi Dave,
I have a few issues and am working with FL to hopefully find a solution.
Recently, I read here about the Web Cache. When I checked mine, it had 50GB. Deleting this cache helped quite a bit with my performance.
One other thing that I noticed is that whenever I start Logos, the Library window shows the message "Updating library catalogue. List may be incomplete." for up to 5 or 10 min, even though no indexing is going on. During this time, Logos is prone to become non-responsive and eventually hang. My hope is that by deleting the DB mentioned here, this might improve. However, before I delete it, I wanted to make sure this can also be done on a Mac without messing things up.
Armin
whenever I start Logos, the Library window shows the message "Updating library catalogue. List may be incomplete." for up to 5 or 10 min, even though no indexing is going on. During this time, Logos is prone to become non-responsive and eventually hang. My hope is that by deleting the DB mentioned here, this might improve.
It's the wrong one in this situation. Updating the library catalogue can occur independently of resource indexing, so please start a new thread with logs as requested.
