I am still having this problem. Here is a set of logs and a sampling from the tool posted previously. Specifically I took the sampling after I told Logos to close after the UI had gone but was left with the never ending "Synchronizing" window and the processors still running about 390% which they have been running at much of the day for me. Hope this helps! 1754.LogosLogs.a3w275.20130502-131906a.zip
7536.LogosLogs.a3w275.20130502-131919.zip
I'm having this issue as well. Anything that can be done about it?
My work around is to stop using that layout. It is either corrupted or there are too many windows open. I've found that making a new layout or returning to a simpler one resolves this constant syncing.
Okay, Thanks!
Sorry Im having the same issue...
6014.Indexer.log
Chris Booth: 6014.Indexer.log
Looks like Library Index rebuild took 1 hour 24 minutes to complete, which is CPU intensive while resource files are being indexed.
Noticed log had some Bible Index errors; not know if bible index needs to be rebuilt. If want to manually rebuild, can use command:
rebuild bible index
Keep Smiling
Logos Wiki Logos 7 Beta Free Support
Keep Smiling 4 Jesus :): Chris Booth: 6014.Indexer.log Looks like Library Index rebuild took 1 hour 24 minutes to complete, which is CPU intensive while resource files are being indexed. Noticed log had some Bible Index errors; not know if bible index needs to be rebuilt. If want to manually rebuild, can use command: rebuild bible index Keep Smiling
I'll ask Martin this week what "ERROR | 28 | ApplicationUtility | SQLite Error 28: multiple links to file" means. Can you paste the support info for the NRSV Aprocrypha?
This fix has worked for all my overheating and cpu issues.
Go into Logos 5 "preferences". Turn off Internet Access.
Once a month turn it on and you'll see the same amount of downloads that you'll see everyday if you leave it on. (avg 600+ MB) The updates are worse the MS Word. LOL well not as bad, but close enough. Why in the world do we want to have an update every day? Once a month is plenty unless something is broke.
If any Mac App downloads an update outside of the App Store, this is normal CPU and Overheating issues. I think also Logos 5 is calling home to much for system checks. I have yet to prove this. And I don't know why indexing has to happen all the time, once things are index that should be good until the next download. I've noticed indexing does not work as hard when the Internet is off. :-)My Logos 5 now works great and to be honest I don't need an upgrade ever... In fact today I turned the Internet back on, first time in 3 months.
Something's broken. It's not designed to work this way.
DeWayne Whitaker:Go into Logos 5 "preferences". Turn off Internet Access.
The most effective way to manage downloads & indexing is to set Automatically Download Updates to NO. You still have internet access for sync'ing your documents and resource metadata, but you can choose to download or not download an update when you receive a notification. If you wish software updates only then use the supplied link in the thread that advises a new version is available.
Dave===
Windows & Android
Im having the same problem
Patrick Fontaine: Im having the same problem
Please describe your problem - exactly what happens and also include logs as per http://wiki.logos.com/Diagnostic_Logging.
Are you on Mac or Windows? What is your computer? What version of Logos?
This problem persists. I have not been updating this thread mostly because of time constraints. However here are some log files including samplings that I have been collecting when the problem occurs, using the tool previously linked. I have thrown in a couple flagged as "good" to provide a contrast. The problem does seem to be directly related to synch though. I can't remember this ever coming up when the synchronization isn't running.
3122.LogosLogs.a3w275.20131014-155958.zip
0081.LogosLogs.a3w275.20130813-152529.zip
7002.LogosLogs.a3w275.20130521-155701.bad.zip
4666.LogosLogs.a3w275.20130516-151449.bad.zip
3108.LogosLogs.a3w275.20131024-102401.zip
6165.LogosLogs.a3w275.20130516-151850.good.zip
7608.LogosLogs.a3w275.20130516-111624.good.zip
Tim: I have not been updating this thread mostly because of time constraints. However here are some log files including samplings that I have been collecting when the problem occurs, using the tool previously linked. I have thrown in a couple flagged as "good" to provide a contrast.
The logs are inconclusive e.g. one of your "good" logs had sync errors whilst two "bad" ones did not! Frequency of syncing appears similar between "good" and "bad" logs. Also, none of the logs relate to the current Logos version 5.2 where Sync v1 is phased out.
The same issue is being reported in numerous threads. Here is another thread on the same issue:
http://community.logos.com/forums/t/68738.aspx?PageIndex=1
I hope that the logs will eventually help Logos track down the problem as it is pretty annoying.
Armin