Index at startup

I'm not sure why, but Logos 4 indexes every time it starts up now. I've had it about two weeks and it's worked without a hitch until this started today. Any ideas?

I'm sure there are probably posts on this already, but I couldn't find any that were helpful.

Find more posts tagged with

Comments

Keep Smiling 4 Jesus :)

I'm not sure why, but Logos 4 indexes every time it starts up now. I've had it about two weeks and it's worked without a hitch until this started today. Any ideas?

I'm sure there are probably posts on this already, but I couldn't find any that were helpful.

Welcome [:D]

For ideas, would like to look at diagnostic logs.

Wiki Mac Troubleshooting => How to Report Bugs in Logos 4 Mac section has log posting steps.

Keep Smiling [:)]

Michael Durso

https://community.logos.com/discussion/comment/262697#Comment_262697

diagnostic logs? not familiar with that

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/262701#Comment_262701

diagnostic logs? not familiar with that

Couple years ago, likewise was not familiar with Logos diagnostic log files.

Thankful for Logos wiki web site, which has contributions primarily by volunteer Logos users.

Please read wiki Mac Troubleshooting => How to Report Bugs in Logos 4 Mac section, which log posting steps (can reply to this forum thread and attach zip file).

Keep Smiling [:)]

Richard Wardman

I'm not sure why, but Logos 4 indexes every time it starts up now. I've had it about two weeks and it's worked without a hitch until this started today. Any ideas?

I'm sure there are probably posts on this already, but I couldn't find any that were helpful.

Hi Michael. Welcome to the forums. Just a quick note to say that you can search the Logos Forums more effectively using Google with the syntax "[search query] site:community.logos.com."

Doing a quick search for "index at launch every time" I found this thread from last year which discusses the need for a certain amount of disk space in order for L4 to complete indexing. Check it out, it might help. Either way, the clever techie dudes (that's not me) over here would be able to help better if you posted your logs (You could always use Logos Log Scribe!)

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/262777#Comment_262777

I'm not sure why, but Logos 4 indexes every time it starts up now. I've had it about two weeks and it's worked without a hitch until this started today. Any ideas?

I'm sure there are probably posts on this already, but I couldn't find any that were helpful.

Hi Michael. Welcome to the forums. Just a quick note to say that you can search the Logos Forums more effectively using Google with the syntax "[search query] site:community.logos.com."

Doing a quick search for "index at launch every time" I found this thread from last year which discusses the need for a certain amount of disk space in order for L4 to complete indexing. Check it out, it might help. Either way, the clever techie dudes (that's not me) over here would be able to help better if you posted your logs (You could always use Logos Log Scribe!)

Every time Logos 4 starts, the Indexer is invoked to check if indexing needed (and other library maintenance). Have seen some resources crash Indexer along with cancel indexing for 4 hours (and an error during login about indexer last ran for a different user); can read Mac Diagnostic Logging files to see if normal or unexpected behavior occurring. Yesterday couple pre-publications shipped along with some resource updates, which Indexer downloads, needs Logos 4 to restart for indexing. Mac downloading has an issue with time outs during download so many restarts are needed.

Each time Logos 4 starts, the contents of diagnostic logs are overwritten.

Keep Smiling [:)]

Michael Durso

https://community.logos.com/discussion/comment/262810#Comment_262810

It actually hasn't done it yet today so it could have just been updates downloading or something...I didn't think it was because it just indexed. It didn't actually download anything that I saw. Oh well. I'll try to get logs if it happens again.

thanks