My Mac is being hijacked by Logos Indexing...

Every time I log into my account on my Mac (which is shared with other family members), the Logos indexer feels that it has to run for about 20 minutes, hogging CPU cycles, bogging things down with lots of disk I/O. This is without Logos being started, without any recent downloads, etc.

My questions:

Is anyone else having similar problems?
Is there something broken in this version of Logos?
Is there a way to disable the run-the-indexer-on-start-up feature and force the indexer to run only when Logos is running?

I'm using version 5.1.0.963.

Regards,

Paul

Find more posts tagged with

Comments

Thomas Ball

Hi Paul. Can you set up logging for me so that the next time this happens we get a recording of it? Can you leave it running until the small indexer icon goes away from your application menu? Here is al ink to obtain logs. http://www.logos.com/support/logos5/mac/problem

Paul Johnson

https://community.logos.com/discussion/comment/511654#Comment_511654

Hi Paul. Can you set up logging for me so that the next time this happens we get a recording of it? Can you leave it running until the small indexer icon goes away from your application menu? Here is al ink to obtain logs. http://www.logos.com/support/logos5/mac/problem

Hi Tommy,

Here are two log archives. The circumstances of the first:

I logged in to my user account on the computer. Predictably, the Logos Indexer started.
I downloaded the logging utility you pointed me to, and enabled logging.
I then started Logos. There happened to be some resource updates, so it downloaded them, restarted, and indexed the updated resources.
After indexing finished, I archived the logs. (NOTE: There was a fair bit of elapsed time between start and finish, because I had to leave the computer for other commitments that took quite some time.)

2235.LogosLogs.Paul.20130731-230605.zip

The circumstances of the second:

After I did the above, I logged out of my user account on the computer, and then logged back in.
Again, the Logos Indexer started.
I started the logging utility.
After the Indexer finished (20+ minutes), I archived the logs. (NOTE: I did NOT start Logos this time.)

2577.LogosLogs.Paul.20130731-233613.zip

Hopefully there is something of help in the log files. I really would like to get to the bottom of this, since it is rather annoying to have what seems to be very unnecessary indexing happening.

Regards,

Paul

Dave Hooton

https://community.logos.com/discussion/comment/511743#Comment_511743

Hopefully there is something of help in the log files. I really would like to get to the bottom of this, since it is rather annoying to have what seems to be very unnecessary indexing happening.

You will have to rebuild the Library Index which will take some time. To do so delete the folder /Users/Paul/Library/Application Support/Logos4/Data/g3va3h4s.p8v/LibraryIndex and restart Logos.

Thomas Ball

https://community.logos.com/discussion/comment/511770#Comment_511770

Hopefully there is something of help in the log files. I really would like to get to the bottom of this, since it is rather annoying to have what seems to be very unnecessary indexing happening.

You will have to rebuild the Library Index which will take some time. To do so delete the folder /Users/Paul/Library/Application Support/Logos4/Data/g3va3h4s.p8v/LibraryIndex and restart Logos.

Thank's, Dave. I agree with his assessment.

Paul Johnson

https://community.logos.com/discussion/comment/511928#Comment_511928

Hopefully there is something of help in the log files. I really would like to get to the bottom of this, since it is rather annoying to have what seems to be very unnecessary indexing happening.

You will have to rebuild the Library Index which will take some time. To do so delete the folder /Users/Paul/Library/Application Support/Logos4/Data/g3va3h4s.p8v/LibraryIndex and restart Logos.

Thank's, Dave. I agree with his assessment.

Thanks, Dave and Tommy. Rebuilding as you described seems to have worked.

Is there any way to build some smarts into the Indexer so that if it encounters this kind of error it informs the user of the need to do a complete rebuild? Since error messages are happening in the logs, it seems like the Indexer should be able to intercept them and deal with it.

(All spoken as a non-programmer, of course!)

Thanks again for your help.

Regards,

Paul

Dave Hooton

https://community.logos.com/discussion/comment/512218#Comment_512218

Is there any way to build some smarts into the Indexer so that if it encounters this kind of error it informs the user of the need to do a complete rebuild?

Computers can only tell you what they know and what they know and can report is constrained by factors outside the application (Logos 5) e.g. in .NET or Windows 7. Some apparently remedial/helpful messages are very misleading, so it is left to knowlegeable humans to decipher the cryptic error messages and recommend a remedy!

In this instance IF the app had said "rebuild the library index" you might have tried the command rebuild library index but it wouldn't have worked!