Bug

Since my last update, Logos no longer indexes the library. It says that it is indexing but it never goes beyond 0% complete.

I hope the log report worked. I had Logos completely shut off when I began logging but the archiving utility said I had to restart Logos. So I did that and saved that log. 8664.LogosLogs.gordonwiebe.20151223-162744.zip

NEW INFO: As a point of interest, I have updated Logos on my Windows computer and have had no issues at all. It indexed perfectly. So, I am wondering if this is strinctly an issue with my MAC?

Find more posts tagged with

Comments

JT (alabama24)

Have you tried restarting your computer?

Gordon Wiebe

https://community.logos.com/discussion/comment/791557#Comment_791557

Hello. Yes I have. There is something in one of the updated books, or in the process of updating, that has affected the indexing function.

JT (alabama24)

the archiving utility said I had to restart Logos

The warning there is telling you that changes made (i.e. turning logging ON or OFF will take place only after the app has restarted.

I had Logos completely shut off when I began logging

My guess is that even though you closed Logos, some processes were still running.

JT (alabama24)

https://community.logos.com/discussion/comment/791564#Comment_791564

I took a quick look at your logs, but I think a "full fledge" techie will need to advise. I saw a number of warnings about some resources, but don't know how to advise.

Gordon Wiebe

https://community.logos.com/discussion/comment/791567#Comment_791567

Thanks very much. I appreciate your interest and the time you have dedicated to my problem. Blessings!

Dave Hooton

https://community.logos.com/discussion/comment/791570#Comment_791570

The latest logs for Dec 23 indicate that indexing is not needed, but earlier logs show crashes because "Main index 'index.idx' had size 4,207,860,499 but merged index 'index-build.idx' had size 599,457,792; aborting merge."

Ensure logging is enabled, run Logos and upload logs if it wants to index but it gets stuck at some percentage.

Myke Harbuck

Since my last update, Logos no longer indexes the library. It says that it is indexing but it never goes beyond 0% complete.

NEW INFO: As a point of interest, I have updated Logos on my Windows computer and have had no issues at all. It indexed perfectly. So, I am wondering if this is strinctly an issue with my MAC?

Maybe things are different now, but I used to have this problem ALL THE TIME (got so frustrated that I wrote in to Bob about it). A software update eventually fixed the issue for me, after more than a year of the problem. I would have to open my Activity Monitor (go to Launch Pad then your Other folder), then look for Logos Indexer process (under the Logos process ) and Force Quit it. Once I did that, then restarted Logos, the indexing would begin normally. It was the Logos Indexer that was hung up and would not shut down when I restarted the software.

This may not be your issue, or even a possible solution any more, but as simple as it is to do, it's worth a shot.

Gordon Wiebe

https://community.logos.com/discussion/comment/792018#Comment_792018

Hi Myke,

Thanks for helping me with this. I'm sorry for taking so long to reply but, Christmas and all. I honestly couldn't see how your solution would work because it just seemed like you really aren't doing anything other than shutting down and restarting. But I gave it a whirl and, low and behold, it worked! I don't know how you came up with that, but I'm sure glad you did. I realize it's a bit of a band aid solution but I'll take a band aid over no solution at all any day. Thanks very much for your help. Now I'll see if I can figure out how to raise this issue with Logos as they don't seem to monitor their own forums.

Jack Caviness

https://community.logos.com/discussion/comment/793579#Comment_793579

Now I'll see if I can figure out how to raise this issue with Logos as they don't seem to monitor their own forums.

But they do monitor this forum, but—like you said‚Christmas and all

Did the problem reappear after you forced the Indexer to quit? This may have been a one-time failure.

Gordon Wiebe

https://community.logos.com/discussion/comment/793874#Comment_793874

I don't thnk Christmas slows them down at all. They had multiple twitter accounts running, emails firing off pushing upgrades, and staff on hand to get those upgrades through. As to the problem, it's been on-going for months. I hoped it was the result of one of the software adjustments, that would be corrected in a future adjustment. Then I thought it may have been a book installation that affected the system, which is why I finally went online for some help. Dealing with the indexer seems to have worked, although I am not sure. I have since added more books to the program and it ran a complete index. I also upgraded to another base package. The indexer is running now and, after several hours, it is at 35% although it hasn't moved from that for quite a while now so, the jury is out.