Logos 5 in a continual "First Time Indexing" Loop

First, enable indexing and try rebooting the computer.If indexing continues upload the logs after about 30 minutes.

https://community.logos.com/discussion/comment/580201#Comment_580201

I can't upload the logs. The file size is 5MB and I get a prompt that tells me that it can't upload the file at this time. What do I do now?

https://community.logos.com/discussion/comment/580291#Comment_580291

4073.logging.zip

I don't know if this is enough logs for this purpose. I could not load up all of the logs. I hope this helps...

https://community.logos.com/discussion/comment/580328#Comment_580328

I hope this helps...

Jim, those logs are from 2 days ago. If you are having indexing trouble we'd need to see the indexer log and indexererror log files as well as any crash logs and the logos log file. Be sure to sort your files by date and only zip together the most recent set. This last set was only about 730 KB, no where near 5 MB.

https://community.logos.com/discussion/comment/580328#Comment_580328

Logos appears to be in an indexing/downloading loop. To stop this

delete /var/folders/39/pbj6b34d7k59wspv_jdbxlpm0000gn/T/Logos-DownloadProgress-rdzein6t.n3r.db (if it exists)
In Program Settings set Automatically download Updates to NO.
restart computer (with logging still enabled)
start Logos
let indexing proceed but ignore download requests until indexing has finished

EDIT: Mark has noticed that the logs are old but still try the above. If there are problems I need logos.log and indexer.log.

https://community.logos.com/discussion/comment/580347#Comment_580347

8877.LogosLogs.jehserwin.20140328-195935 2.zip

I hope this helps you with more detailed information

https://community.logos.com/discussion/comment/580352#Comment_580352

If indexing is underway, let it go on but change Settings and ignore downloads as per my previous post.

https://community.logos.com/discussion/comment/580352#Comment_580352

Jim, you have quite a few resources, so it will take awhile to index everything. The log you last sent shows 13 resources indexed in about 5 minutes. You have 2,795 resources. I hope you can leave the computer on all night, or for however long this takes. (I also hope indexing speeds up for you.)

https://community.logos.com/discussion/comment/580354#Comment_580354

How do I tell it to ignore downloads?

https://community.logos.com/discussion/comment/580355#Comment_580355

I need to get rid of the Perseus Collection I guess...

https://community.logos.com/discussion/comment/580356#Comment_580356

How do I tell it to ignore downloads?

I believe what Dave wants you to do is to change the setting he indicated. Then should Logos prompt you to install anything, just ignore that request and let indexing proceed.

https://community.logos.com/discussion/comment/580358#Comment_580358

I need to get rid of the Perseus Collection I guess...

You have a pretty good computer. Do you have just an SSD or do you have a normal hard drive?

Indexing does like a lot of cores. You have 2. My PC laptop has 4 and indexing often uses all 4. If you have a regular HDD at 5400 RPM that might slow indexing a bit, too, though I can't remember when I moved from 5400-7200 RPMs if that affected indexing time.

Remember, full indexing is a pain to be endured only very infrequently.

https://community.logos.com/discussion/comment/580360#Comment_580360

I have a regular hard drive on a MacBook Pro (Mid-2009). 2.26GHz Intel Core 2 Duo. I hope you are right about indexing.

https://community.logos.com/discussion/comment/580362#Comment_580362

I have a regular hard drive on a MacBook Pro (Mid-2009). 2.26GHz Intel Core 2 Duo. I hope you are right about indexing.

Indexing is what tests our computer hardware! My now 3 year old laptop is a result of continual over-heating that crashed my old computer while indexing Logos. I, too, had a Core 2 Duo CPU. My newer machine has an i7 processor with 4 cores and 8 threads. It handles Logos indexing with aplomb.

Give the indexer time. I wouldn't be surprised if it takes 4-6 hours (or even longer) to complete.

https://community.logos.com/discussion/comment/580366#Comment_580366

With respect, Mark, if what the OP says is true, then this is an issue to be looked into, if not an outright bug. The indexer shouldn't be acting this way, unless there is a hardware fault.

https://community.logos.com/discussion/comment/580375#Comment_580375

I have been thinking about replacing my MacBookPro. However, I kept thinking that this should not be happening after I just upgraded to Bronze. I was beginning to think it was a bug in Logos. My next step was to download the latest Beta and see if it would be better.

https://community.logos.com/discussion/comment/580381#Comment_580381

My next step was to download the latest Beta and see if it would be better.

The log shows no faults, only that the Library index (2700 +) needs to be redone, so this step will only put you in the position of indexing FROM THE START yet again! Make the Auto Downloads change in Settings, let indexing continue and refuse any downloads until it is complete, whether it takes 4 hours or 20 hours.

https://community.logos.com/discussion/comment/580408#Comment_580408

Finally finished the rebuild index this morning. Thanks for all of the help.

https://community.logos.com/discussion/comment/580502#Comment_580502

Looks like 5.2a did its job.

https://community.logos.com/discussion/comment/580503#Comment_580503

Looks like 5.2a did its job.

From what I have seen, all 5.2a does that the previous version did not due is not let the program crash because of a defective database. They mark the database for deletion and when one restarts the program the database is rebuilt.

If there are other problems, they will still prevent Logos from operating properly. 5.2a addresses the problem of defective database repair.

https://community.logos.com/discussion/comment/580507#Comment_580507

Yes, I'm aware that it does not fix the underlying problem of defective databases (ungraceful exits? bad clusters?) but it's a great start (pardon the pun).

At least, no infinite loops or service calls! [:D]

https://community.logos.com/discussion/comment/580516#Comment_580516

At least, no infinite loops or service calls!

Loops might still occur. Jim's problem (and he was not on 5.2a, rather 5.2 SR-6) seems not to have to do with a corrupted database so 5.2a would not have helped. It might be he was exiting Logos before the indexing was completed and it just kept starting back up each time he opened Logos. We don't have any logs to prove or disprove this, however.

I am grateful for any way Logos can make the program more resilient on it's own, as you are. And I'm glad that it seems Jim's problem is solved.