Spurious? Library being updated message

Page 1 of 2 (40 items) 1 2 Next >
This post has 39 Replies | 0 Followers

Posts 22746
Forum MVP
Graham Criddle | Forum Activity | Posted: Thu, Jun 29 2017 10:52 AM

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?

Posts 3007
LogosEmployee
Philana R. Crouch | Forum Activity | Replied: Thu, Jun 29 2017 10:57 AM

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?

Posts 22746
Forum MVP
Graham Criddle | Forum Activity | Replied: Thu, Jun 29 2017 11:14 AM

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

Posts 3007
LogosEmployee
Philana R. Crouch | Forum Activity | Replied: Thu, Jun 29 2017 11:40 AM
Thanks Graham!
Posts 25661
Forum MVP
Dave Hooton | Forum Activity | Replied: Thu, Jun 29 2017 3:44 PM

Philana R. Crouch:
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).

Dave
===

Windows 10 & Android 8

Posts 2198
LogosEmployee

Dave Hooton:

Philana R. Crouch:
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.

Posts 13397
Mark Barnes | Forum Activity | Replied: Thu, Jun 29 2017 5:48 PM

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.

Posts 25661
Forum MVP
Dave Hooton | Forum Activity | Replied: Thu, Jun 29 2017 8:51 PM

Andrew Batishko (Faithlife):

Dave Hooton:
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.

  • Start download of 180 MB and get message in Search panel and Library
  • When download is complete, I'm notified that other resources need a restart.
  • But message in Search panel is removed until the Windows Indexing popup appears (when it is reinstated)
  • When popup appears the Library catalog message is removed
  • When indexing complete, message in Search panel is removed.

Then I restart Logos:-

  • No notifications, but get message in Search panel
  • Log shows processing of DB:PREACHINGTHEMES
  • Message remains long after the log shows all processing for discovery/update projects is complete
  • No notifications throughout and no Indexer log.

I have to restart Logos to remove the Search panel message:

  • But the Indexer is run for update of Auto Complete

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.

Dave
===

Windows 10 & Android 8

Posts 3007
LogosEmployee
Philana R. Crouch | Forum Activity | Replied: Mon, Jul 3 2017 8:56 AM

Dave and Mark,

Thank you for this additional information. I'll continue to investigate.

Posts 25661
Forum MVP
Dave Hooton | Forum Activity | Replied: Mon, Jul 10 2017 7:48 PM

Dave Hooton:

I have to restart Logos to remove the Search panel message:

  • But the Indexer is run for update of Auto Complete

This is annoying! Similar scenario to above, where the Search panel message came up after restarting Beta 4 and remained. When I (eventually) restarted the Indexer updated Auto Complete and indexed DB:BIBLICAL-PLACES-MAPS; not that it was updated (no download) but presumably because DB:Biblical-Places was updated.

2867.LogosIndexer.log

I would suggest an alternative message and/or a restart notification to clarify the situation.

Dave
===

Windows 10 & Android 8

Posts 13397
Mark Barnes | Forum Activity | Replied: Tue, Jul 11 2017 3:34 AM

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.

Posts 3007
LogosEmployee
Philana R. Crouch | Forum Activity | Replied: Tue, Jul 11 2017 3:13 PM

Dave and Mark,

We're still trying track things down. If you reproduce this again, could you upload your entire log folder? We've added some additional logging information that will provide more details to the dev team.

Thank you for your help!

Posts 13397
Mark Barnes | Forum Activity | Replied: Tue, Jul 11 2017 3:33 PM

Philana R. Crouch:
We're still trying track things down. If you reproduce this again, could you upload your entire log folder? We've added some additional logging information that will provide more details to the dev team.

There are two issues going on here. The issue with delayed indexing only seemed to affect me, and only once. If that ever repeats, I'll upload logs.

But the main issue (the stuck "library being updated" message) seems straightforward. This seems to be the logic that triggers the bug:

  1. Logos downloads a resource that it can't update yet, because it's in use. It prompts for the application to be restarted.
  2. Because Logos knows that a downloaded resource needs updating, it triggers the 'library being updated message'.
  3. However, because the indexer knows it can't update the file yet, it doesn't trigger until a restart.

Step (2) seems to be the problematic one — that the logic used to display the message is different from the logic used to determine whether an resource should be indexed now.

Posts 25661
Forum MVP
Dave Hooton | Forum Activity | Replied: Tue, Jul 11 2017 5:25 PM

Mark Barnes:
But the main issue (the stuck "library being updated" message) seems straightforward. ...

I agree, and I'm surprised it hasn't been replicated by the team. So I'll provide logs when it happens again.

Dave
===

Windows 10 & Android 8

Posts 25661
Forum MVP
Dave Hooton | Forum Activity | Replied: Tue, Jul 11 2017 7:33 PM

Dave Hooton:
I agree, and I'm surprised it hasn't been replicated by the team. So I'll provide logs when it happens again

I tried replicating but didn't get what I expected:

  1. Deleted datasets not updated in this Beta cycle:
    1. DB:Biographies 2017-04-13 ---> locked when Logos starts
    2. DB:Lexham-Cultural-Ontology 2017-04-26 --->  locked when Logos starts
    3. sesb-morph-arc-ot.lbslem ---> not locked when Logos starts
  2. Started Beta 5 and got Download message (ResAvl-msg.log):
    1. Noticed Indexer log with Pipe error message (Pipe-msg-Indexer.log & LogosIndexerCrash.txt)
  3. Shutdown Logos
  4. Restarted Logos and initiated the download (Download.log):
    1. Library Cat msg displayed, then
    2. Search panel msg displayed.
    3. Search panel msg removed after a while, then
    4. Library Cat msg removed.
    5. Noticed Indexer log (DwnldIndexer.log)
    6. No panel messages remain!
  5. Restarted Logos (Logos.log)  ---> FYI as nothing notable.

The first two datasets were restored but not sesb-morph-arc-ot.lbslem. No other resources were downloaded.

4452.Logos Logs.zip

Is this the expected behaviour, including the first Indexer run (irrespective of the Pipe error)?

Was the shutdown at  Step 3. significant to the behaviour?

Can I remove other unused lbslem datasets?

Dave
===

Windows 10 & Android 8

Posts 25661
Forum MVP
Dave Hooton | Forum Activity | Replied: Wed, Jul 12 2017 12:29 AM

Dave Hooton:
Was the shutdown at  Step 3. significant to the behaviour?

Tried without Step 3 above i.e. normal processing:

1. Deleted only DB:Biographies dataset

2. Started Beta 5 (Download-Biog.log)

  • Library Cat msg displayed, then
  • Search panel msg displayed
  • Library Cat msg removed
  • Initiated download
  • Library Cat msg displayed
  • Search panel msg remained from above
  • Library Cat msg removed
  • Search panel msg remained
  • Indexer not run

3. Restarted Logos (Logos.log)

  • No Search panel msg
  • Indexer not run

6840.Download-Biog.zip

Dave
===

Windows 10 & Android 8

Posts 25661
Forum MVP
Dave Hooton | Forum Activity | Replied: Wed, Jul 12 2017 1:14 AM

1. Deleted Biographies & LCO datasets (as above)

2. Started Beta 5 (Logos.log)

  • Library Cat msg displayed, then
  • Search panel msg displayed
  • Windows indexer notification flashed
  • Library Cat msg removed
  • Search panel msg removed
  • Indexer log has Pipe error  (Pipe-Indexer.log)
  • Initiated download
  • Library Cat msg displayed
  • Search panel msg displayed and then removed
  • Windows indexer notification flashed
  • Library Cat msg removed
  • Indexer log run for Auto complete (LogosIndexer.log)
  • No panel messages remain!

Note 1: the Windows Indexer notification (brief flash) occurred at other times, but not noted.

Note 2: in case it isn't clear, I do not auto-download.

0763.Logos Logs-2.zip

Pick your behaviour depending on datasets involved!

Dave
===

Windows 10 & Android 8

Posts 3007
LogosEmployee
Philana R. Crouch | Forum Activity | Replied: Wed, Jul 12 2017 8:18 AM

Dave Hooton:

Mark Barnes:
But the main issue (the stuck "library being updated" message) seems straightforward. ...

I agree, and I'm surprised it hasn't been replicated by the team. So I'll provide logs when it happens again.

Hi Dave,

Thanks for providing your logs, this gave us some additional information to track things down.

Posts 2198
LogosEmployee

Mark Barnes:

Philana R. Crouch:
We're still trying track things down. If you reproduce this again, could you upload your entire log folder? We've added some additional logging information that will provide more details to the dev team.

There are two issues going on here. The issue with delayed indexing only seemed to affect me, and only once. If that ever repeats, I'll upload logs.

But the main issue (the stuck "library being updated" message) seems straightforward. This seems to be the logic that triggers the bug:

  1. Logos downloads a resource that it can't update yet, because it's in use. It prompts for the application to be restarted.
  2. Because Logos knows that a downloaded resource needs updating, it triggers the 'library being updated message'.
  3. However, because the indexer knows it can't update the file yet, it doesn't trigger until a restart.

Step (2) seems to be the problematic one — that the logic used to display the message is different from the logic used to determine whether an resource should be indexed now.

We can't recreate this issue. Here's my test case:

  1. Make sure the application and all resources are up to date and indexed
  2. Turn off auto downloads and manually replace a resource file with an older version
  3. Open a search panel and the resource replaced above
  4. Start the update
  5. The yellow bar in the search panel never appears, but the prompt to restart the application does appear

My guess is that there were multiple resources updated in your case. Some were able to update (causing the message in the search panel) and other were not (causing the restart message). Of course, without log files, that's difficult to confirm.

Posts 13397
Mark Barnes | Forum Activity | Replied: Wed, Jul 12 2017 9:29 AM

Andrew Batishko (Faithlife):
My guess is that there were multiple resources updated in your case. Some were able to update (causing the message in the search panel) and other were not (causing the restart message).

Yes, that's possible. In that scenario, is the index supposed to reindex the updated resources, or wait until the restart and reindex all the updates at the same time.

Page 1 of 2 (40 items) 1 2 Next > | RSS