Beta 5 indexes everytime I start the program
Beta 5 starts indexing every time I start Logos 4. Anyone else having this problem? Thanks!
Comments
-
When you say it indexes everytime you start the program are you talking about the Logos icon that appears in the system tray for a second or two and then goes away? If that is what you are talking about, I think that is normal behavior since the release of L4. If not please post logs.
0 -
Michael Lyman said:
Anyone else having this problem? Thanks!
I am not, but it indicates a problem with the index file and the likelihood you are having a succession of Indexer crashes. Please turn on permanent diagnostic logging, open Logos and let the Indexer run until it stops, then look for the log files under My Documents/Logos Log Files, zip them up and attach them to a follow-up post (use the paperclip icon on the message composition page tool bar for this).
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
Michael Lyman said:
Beta 5 starts indexing every time I start Logos 4. Anyone else having this problem? Thanks!
Thankfully not, there were a 1GB update, maybe indexer hasnt finished yet..
Never Deprive Anyone of Hope.. It Might Be ALL They Have
0 -
-
The indexer is shutting down partway through the index process which explains the every-time-I-open-it issue.
Type Rebuild Bible Index in the Command bar and hit Enter. This will force L4 to dump the old Bible index and build a new one.
Once that is complete, zip up the logs again and let us take another look. It may be all you need to do.
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
Mark A. Smith said:
Type Rebuild Bible Index in the Command bar and hit Enter. This will force L4 to dump the old Bible index and build a new one.
Mark,
The log shows the problem occurs with the library index - the Bible Index is OK ie. should have tried Rebuild library index
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
The log shows the problem occurs with the library index - the Bible Index is OK ie. should have tried Rebuild library index
You're right. It is staring me in the face (all those Library Index and Resource Indexer lines) and I didn't see it. Well that can be readily fixed (and a Rebuild Bible Index is not too time consuming).
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
I did both and now I have no library index again. I haven't had this problem for months... Here's my logs.
0 -
Michael,
Sorry the problems are continuing. The new Indexer file shows a different termination error than your first one did. In addition, your latest Logos4.log file shows a bunch of 'Error VisualUtility' errors, whereas only two appear (I think I counted correctly) in your first log. That is a new one I haven't seen before.
I think considering how much effort you've put in in reindexing and our lack of progress, we ought to wait to see if we can hear from Logos on this issue.
Dave may come up with an idea. If not, someone from Logos may give us some help or you may have to call Tech Support tomorrow and refer to the thread here.
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
Mark A. Smith said:
I think considering how much effort you've put in in reindexing and our lack of progress, we ought to wait to see if we can hear from Logos on this issue.
I agree!
I would only suggest whilst waiting for Logos to enter rebuild library index and then close L4!
Dave
===Windows 11 & Android 13
0 -
The errors from your logs are both "should not happen" errors that indicate serious inconsistencies in the data being indexed. While we can't definitively rule out a Logos 4 bug, given that this is only happening on your computer*, it seems highly likely to me to be a hardware issue. (See also http://community.logos.com/forums/p/17747/133646.aspx#133646 and http://community.logos.com/forums/p/24540/185592.aspx#185592.)
* Do you have Logos 4 installed on just this one computer, or do you have it installed on another computer? If it's also installed on a different computer, is that installation indexing without errors?
0 -
Bradley, I ran the Prime 5 software the last time I had this problem and everything came back fine. Eventually the software reindexed correctly and I have not had the problem until the latest update of almost a gb. I have a cooling fan running on the PC. I just started the update on my other computer and will let you know the outcome. Thanks.
0 -
Michael Lyman said:
Bradley, I ran the Prime 5 software the last time I had this problem and everything came back fine.
Have you ever run Prime95 while indexing? If the indexer is causing the system to overheat, memory or CPU errors should be reported by Prime95 if it's running at the same time. (We've had reports that burn-in programs don't stress a system as much as the indexer does: http://community.logos.com/forums/p/24540/186102.aspx#186102).
However, it's still possible that these indexing errors could be caused by intermittent read errors from the hard drive caused by overheating (e.g., http://community.logos.com/forums/p/17747/133646.aspx#133646); Prime95 wouldn't be able to detect these kind of problems, but possibly a HDD burn-in program could.
0 -
Bradley Grainger said:
However, it's still possible that these indexing errors could be caused by intermittent read errors from the hard drive caused by overheating (e.g., http://community.logos.com/forums/p/17747/133646.aspx#133646);
Perhaps try http://www.ntfs.com/disk-monitor.htm?
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
It does run hot, I'm installing the program Mark suggested now. I guess I'll try putting it in the sunroom to index on a cold night with the windows open and see if that helps.
0 -
Mark, Bradley, Dave and everyone else who had helped my on this long journey to figure out my indexing woes from time to time:
I installed the Active Disk Monitor and turned the AC on with a big old fan blowing on the bottom of my laptop and I have a good index now. This AMD chipset is known for running hot, but since it would index fine for months at a time and other diagnostics came back fine I didn't realize that was the problem. I have a working index again. [Y] [Y]
Thanks for offering so much help to a person who had a very rare problem and solving it, I really appreciate it. The monitor convinced my that this was the issue and I bet that it's the answer for a lot of peoples indexing woes. Have a great weekend!
0
