BUG: Indexing problem now exacerbated by Logos Now.
I have posted this before and have called tech support and there has been no real solution, not (apparently) root cause analysis.
Indexing on both my desktop (Lenovo) and my tablet PC (not tablet device, this is s full Windows-Intel computer - ASUS) both running Windows 8.1 pro x64 with all latest patches.
The issue is that the indexer seems to just stop when doing the partial, adding resource indexing. I expect the indexer to run every time I get a new resource, and that is something that regularly happens for me. But since it never actually completes, I find that I have to either relaunch Logos over and over until it “takes”, or just skip it and bit the bullet to rebuild the index, causing a hit on performance for my computers for a couple days.
The problem has been escalated for the last few months and I didn’t make the connection till late last month. I have subscribed to Logos Now and so with the resources I choose to add and with the resources LN adds, along with all the L6 updates, my systems seem to always be in a state of indexing.
Since I have had no real answers for the indexing issue and even with tech support, always seem to have to just do a full rebuild, I feel that I am now being forced into having to unsubscribing from a paid service that I believe is a great asset (otherwise) to my Faithlife, Logos software.
I love my L6, but this is pretty frustrating that I have many tens of thousands of dollars invested in a tool, and can’t seem to get it to work the way it is supposed to (as I understand it).
Comments
- AV - Mcafee All Access - Total Protection. verified it wasn't doing a scan during indexing in any of the above described times. I have the free version of MalwareBytes also, and so it doesn't do anything unless I launch it, so not running.
- Real Time backup. not really. I have Dropbox, but it is a folder in My Documents - it is peer, but not part of the Logs data files structure. Same with OneDrive and iCloud; they are not even close to that directory structure. In fact, I am careful to not even backup that appdata folder since L6 will rebuild it if/when I need a reinstall.
- No desktop search or other indexing, except the built in indexing function. I just now excluded that directory structure from indexing. it is possible that was the culprit, though in my opinion, highly unlikely.
If you upload indexing logs, we might be able to get to the root of the problem. It's odd that it's happening on both machines, though. (I know you said you've posted about it before, but I looked through your recent posts, and couldn't find them.)
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!
If you upload indexing logs, we might be able to get to the root of the problem. It's odd that it's happening on both machines, though. (I know you said you've posted about it before, but I looked through your recent posts, and couldn't find them.)
here is the zip from the ASUS :3683.ASUS Index Crash.zip
the indexing from a recent purchase seems to be indexing on the Lenovo desktop (this time). it doesn't happen as often on the desktop - especially just after a full index rebuild. but it does the same thing after a time of resources being added. i can attach the logs for the desktop if it is needed, but again, it is not failing (this time). I will leave logging on in case other resources and it crashes the indexer later.
It's possible that these errors are caused by bad file security settings (permissions). If so, following the instructions to reset file permissions will hopefully clear it up: https://www.logos.com/support/logos5/windows/error-writing-to-file
thanks. Though I have not received any permissions issues, I will still follow the suggestions: I have done this so many times, I have it memorized. I purposely did not restart Logos again, yet on that computer. should I try again? any pointers in the logs?It's possible that these errors are caused by bad file security settings (permissions). If so, following the instructions to reset file permissions will hopefully clear it up: https://www.logos.com/support/logos5/windows/error-writing-to-file
well... I thought the Lenovo (desktop) completed. it appeared to count through 100%, though the last I actually saw it before doing something else was about 65% or so. so, I restarted Logos, just to be sure, and sure enough, it is reindexing again. (currently "preparing library"). will get logs for the desktop as soon as the status changes, and I shut it down...
the lenovo desktop logs, though the issue seems to be a bit different, i wonder if it is similar problems.. The Lenovo keeps trying to reimage (blue circle, with a one in it. screen shot clip included in the zip), and then goes away after a few minutes each time I restart L6.1122.Lenovo Logos Logs.zip
it doesn't seem to have the same number of log files as the ASUS has...
the lenovo desktop logs, though the issue seems to be a bit different, i wonder if it is similar problems.. The Lenovo keeps trying to reimage (blue circle, with a one in it. screen shot clip included in the zip), and then goes away after a few minutes each time I restart L6.1122.Lenovo Logos Logs.zip
Looks like indexing completed successfully on the desktop.
The blue circled (1) notification is a problem that's been noted by a couple of other users (on a different thread). This is a different problem that we're looking into.
Well, still broken this morning.
started up the computer, the Logos Indexer started (I had not yet launched L6). I just let the computer sit for a while, then checked back after about 15 minutes. as previously, when I checked the taskbar, and my mouse hit/hovered the indexer icon, it disappeared. At this point, I then went ahead and launched L6.
As has been the case recently, the blue circle with the (1) in it shows up, but initially when I hover it, it doesn't show any pop ups. as soon as the indexer starts in the taskbar (~5 minutes later):
The blue circle the starts to show percentage complete for indexing when mouse is hovered.
the index folder then looks like this:
though it seems to have started, the (1) and the taskbar indexer icon both show 0% complete for 15 minutes, then i noticed the (1) and the index icon disappeared. and the index folder (above) now only shows the regular files as previously provided.
While it is possible that it did a supplemental index when I launch L6, it does the same thing as above shows the (1), starts the indexer, then stops. - leaving me feel uneasy that it is in a normal state.
EDIT - adding logs again...1586.ASUS Index Crash.zip
also, since I noticed something about disk space, I have over 20 gig free on the volume and over 4 gig free on the OS/C: volume.
wow, thanks for the update. if there is anything else I can provide, please let me know.Thanks for all the helpful information, and thanks for your patience! The developer who has been looking at this problem is currently out of the office, but we've added some notes to the case so he can take a look when he gets back.
We aren't sure, but suspect it could be a conflict with another program on your system that is opening these files while Logos is using them (and causing a conflict). Do you have anti-virus, real-time backup, desktop search, or any other programs you can think of that might be watching for changes to files on your disks? If so, which ones?
We aren't sure, but suspect it could be a conflict with another program on your system that is opening these files while Logos is using them (and causing a conflict). Do you have anti-virus, real-time backup, desktop search, or any other programs you can think of that might be watching for changes to files on your disks? If so, which ones?
Frequency of indexing may be affected by Logos Now (once a month!) but it is not the root cause**. And you can regulate the frequency with the Automatically Download Updates setting = NO e.g. download every three days or whenever it is convenient - even moderate your buying sprees.
** I don't experience the issue as a subscriber. Faithlife still haven't been able to find the root cause, but frequency of indexing may be a factor.
Dave
===
Windows 11 & Android 13