This is with Logos 7.8 beta 2 on Windows 10
Opening search windows indicate that my library is being updated but there is no indication of that and the indexer is not running
Any thoughts on this?
Anything I can do to help track it down further?
Hi Graham,
I'm sorry, at first I did see it, but after restarting it disappeared. Does this reproduce every time? Do you have logs?
Hi Philana - thanks for responding.
It was reproducible, but I started Logos and restarted to get some clean logs, and it started indexing!
So its now reasonable that I get the message.
I'll keep an eye on it and flag it again if it continues after indexing is complete
Graham
In my case it also disappeared after a restart, but I would expect it to be removed immediately after processing DB:PREACHINGTHEMES.(but I doubt that the message is warranted for a database update).
I'm sorry, at first I did see it, but after restarting it disappeared. Does this reproduce every time? Do you have logs? In my case it also disappeared after a restart, but I would expect it to be removed immediately after processing DB:PREACHINGTHEMES.(but I doubt that the message is warranted for a database update).
Updates to database resources can cause the indexer to need to run, since the indexer generates the auto-completer database, which contains various information from a variety of database resources.
This happened to me, too. Immediately after restarting Logos to update to beta 2, I received this message, which appears to be stuck. There's no corresponding blue numerical icon, and LogosIndexer.exe is not running.
Here are my logs
The indexer log is dated 22 June, though my library reports updates on 23, 26 and 29 June.
When I restarted Logos, the message had gone away. Then after a minute or two, the message came back, I got the blue numeric icon, and logosindexer.exe appeared in the taskbar. My library shows only one new resource for today (the NLT), but the indexer log shows 28 resources being indexed. That's the right number (I've 28 resources updated since my indexer log was last updated).
Before that indexing finished, I ran a quick search on some of the resources that were updated yesterday, and I can see that the indexes are definitely out of sync with the resource. (See the screenshot below.) This suggests that beta 1 failed to index some of my updated resources, despite me starting and restarting Logos several times during the last week. Beta 2 has indexed those resources, but it only did it after restarting, not first time.
Here are a second batch of logs (after the restart):
I might be able to dig out old versions of logos.log for the days when I got updates, if that would help.
In my case it also disappeared after a restart, but I would expect it to be removed immediately after processing DB:PREACHINGTHEMES.(but I doubt that the message is warranted for a database update). Updates to database resources can cause the indexer to need to run, since the indexer generates the auto-completer database, which contains various information from a variety of database resources.
Behaviour confirmed on another machine i.e.
Then I restart Logos:-
I have to restart Logos to remove the Search panel message:
Is it necessary for a Search panel message to appear in this case? Even if it may be valid until an update of Auto Complete, the user will consider the message to be spurious as currently implemented. So I suggest it be removed when the immediate processing for the database is complete.
The "some search results may be missing" stuck message occurred after updating to beta 4.
When I restarted Logos, the "Preparing Your Library" message flashed up briefly, and then the DB:BIBLICAL-PLACES-MAPS resource indexed.
This is with Logos 7.8 beta 2 on Windows 10 Opening search windows indicate that my library is being updated but there is no indication of that and the indexer is not running Any thoughts on this? Anything I can do to help track it down further?
This should be fixed in 7.8 RC 2 (7.8.0.0026). If everyone who reported problems with the indexer could retest and let us know if it's working now, and if not please post new logs.
