Spurious? Library being updated message

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?

«1

Comments

  • Philana R. Crouch
    Philana R. Crouch Member, Logos Employee Posts: 4,597

    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?

  • Graham Criddle
    Graham Criddle MVP Posts: 32,636

    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

  • Dave Hooton
    Dave Hooton MVP Posts: 35,770

    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 11 & Android 13

  • Andrew Batishko
    Andrew Batishko Member, Administrator, Community Manager, Logos Employee Posts: 5,395

    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.

    Andrew Batishko | Logos software developer

  • Mark Barnes
    Mark Barnes Member Posts: 15,432 ✭✭✭

    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.

    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!

  • Dave Hooton
    Dave Hooton MVP Posts: 35,770

    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 11 & Android 13

  • Philana R. Crouch
    Philana R. Crouch Member, Logos Employee Posts: 4,597

    Dave and Mark,

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

  • Dave Hooton
    Dave Hooton MVP Posts: 35,770

    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 11 & Android 13

  • Mark Barnes
    Mark Barnes Member Posts: 15,432 ✭✭✭

    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 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!

  • Philana R. Crouch
    Philana R. Crouch Member, Logos Employee Posts: 4,597

    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!

  • Mark Barnes
    Mark Barnes Member Posts: 15,432 ✭✭✭

    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.

    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!

  • Dave Hooton
    Dave Hooton MVP Posts: 35,770

    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 11 & Android 13

  • Dave Hooton
    Dave Hooton MVP Posts: 35,770

    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 11 & Android 13

  • Dave Hooton
    Dave Hooton MVP Posts: 35,770

    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 11 & Android 13

  • Dave Hooton
    Dave Hooton MVP Posts: 35,770

    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 11 & Android 13

  • Philana R. Crouch
    Philana R. Crouch Member, Logos Employee Posts: 4,597

    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.

  • Andrew Batishko
    Andrew Batishko Member, Administrator, Community Manager, Logos Employee Posts: 5,395

    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.

    Andrew Batishko | Logos software developer

  • Mark Barnes
    Mark Barnes Member Posts: 15,432 ✭✭✭

    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.

    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!

  • Andrew Batishko
    Andrew Batishko Member, Administrator, Community Manager, Logos Employee Posts: 5,395

    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.

    It's supposed to reindex the updated stuff immediately, since we don't know how long it will be until the user chooses to restart the application. However, there's a problem we're trying to track down that can prevent the application from trying to start up the indexer. That's a different and (probably?) unrelated issue from the pipe errors Dave reported that we're also concerned about.

    Andrew Batishko | Logos software developer

  • Andrew Batishko
    Andrew Batishko Member, Administrator, Community Manager, Logos Employee Posts: 5,395

    With 7.8 RC 1 we've made a change that should allow the indexer to run correctly during startup. However, the underlying problem caused by some other work that was never completing is still unresolved. We've added some logging that will hopefully help us determine what's going on here.

    We would appreciate it if everyone here could retest this situation with the new version, and regardless of whether or not the indexer correctly starts up, please post your log file. If you needed to restart the application in order to complete the update, please include both log files.

    Andrew Batishko | Logos software developer

  • Dave Hooton
    Dave Hooton MVP Posts: 35,770

    However, the underlying problem caused by some other work that was never completing is still unresolved.

    What issue is this? It would be helpful if Release Notes would state/clarify known issues.

    Dave
    ===

    Windows 11 & Android 13

  • Andrew Batishko
    Andrew Batishko Member, Administrator, Community Manager, Logos Employee Posts: 5,395

    However, the underlying problem caused by some other work that was never completing is still unresolved.

    What issue is this? It would be helpful if Release Notes would state/clarify known issues.

    We didn't go into detail because the details are internal to the application and not pertinent to the normal user experience. This is a normal state of affairs for release notes (they never include literally all the changes that are made to the application). And usually this gets commented on every time there's a release where the only changes made are ones that are not normally listed in the release notes.

    We posted in this thread with some additional details beyond the release notes because this thread is the exception to "not pertinent to the normal user experience".

    Your experience will most likely be that everything seems to behave normally. The application might not automatically start it's initial sync, although that's usually not really a problem since it'll automatically happen at some point soon anyway. There could be one or two other quirks as well, but we aren't positive on the details.

    Andrew Batishko | Logos software developer

  • Dave Hooton
    Dave Hooton MVP Posts: 35,770

    We would appreciate it if everyone here could retest this situation with the new version,

    In relation to the test cases ran in Beta 5:

    1. Where I deleted two datasets, there was no Pipe error message and the 2x panel messages appeared and disappeared as I expected.

    1777.Two-Datasets.zip

    2. Where I deleted only the Biographies dataset, the Indexer ran twice. But there was no Search panel message?

    6076.One-Dataset.zip

    EDIT 1: In both cases there was no Indexing Notification for Auto Complete which took abt. 1.3 - 1.5 min.

    EDIT 2: When the Search panel message disappeared (two datasets) the Auto Complete indexing was still underway.

    EDIT 3: If I deleted only the LCO dataset there was also no Search panel message?

    Dave
    ===

    Windows 11 & Android 13

  • Dave Hooton
    Dave Hooton MVP Posts: 35,770

    1. Deleted LCO dataset and SBLGNT

    2. Started Logos (Download.log)

    • Library Cat msg displayed,but
    • NO Search panel msg
    • Initial Indexing (no log)
    • Library Cat msg removed
    • Initiated download
    • Library Cat msg displayed
    • Search panel msg displayed
    • Search panel msg removed whilst Indexer was running? (LogosIndexer.log)
    • Library Cat msg removed & Indexer completed
    • No Indexing Notification**...

    2577.Resource.zip

    ** Admittedly, no actual Indexing took place (SBLGNT wasn't updated), but Windows user would be aware that the Indexer was running for a couple of minutes.

    Dave
    ===

    Windows 11 & Android 13

  • Mark Barnes
    Mark Barnes Member Posts: 15,432 ✭✭✭

    Here's what happened during the install of 7.8 RC1:

    • I typed "Update Now" in the command box.
      • Logos downloaded some metadata updates and the application update.
      • No resources were downloaded.
      • The indexer didn't fire (indexing log wasn't updated)
    • I then went to bed, but left the download running.
    • Around 4am, I received a resource update (AR151 MobileEd course). This is a brand new resource, so wasn't replacing locked files.
    • Everything seems fine from the log file, except
      • Some resources couldn't be discovered. They seemed to be resources I've returned/sold, and after later running delete unlicensed resources all the files referred to had disappeared.
      • The indexer didn't seem to trigger (no mention of it in the logs, and the indexer log file was not updated)
    • In the morning, 
      • There's only one blue circle, which refers to the application update.
      • Nonetheless, search is reporting that "some search results may be missing…"
    • 546841.Logos.log

    After the restart:

    • Indexing triggered straight away. I got the blue circle, and the search message, too.
    • Neither logos.log nor LogosIndexer.log were updated. I didn't have those files open/locked AFAIK. I've no idea why I have no new logs.
    • Using resmon to monitor disk activity, only LibraryIndex/index.idx was being accessed by LogosIndexer.exe (and read, not written). I realised later that the 'system' process was writing to some indexing files, but I wasn't monitoring that process to see what was going on.
    • After the indexing finished the blue circle and the search message disappeared, as you would expect.

    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!

  • Dave Hooton
    Dave Hooton MVP Posts: 35,770

    Updated to RC1 on another machine.

    1. Started Logos (Logos-1.log)

    • Notification of 472 MB Download
    • Initiated download
    • Library Cat msg displayed
    • Search panel msg displayed
    • Cancelled Download at 46% (409.6 MB left)
    • Library Cat msg removed
    • "Resources ready to be added" Notification
    • Indexer Started, then
    • Indexer Completed after a while (LogosIndexer-1.log)
    • Search panel msg removed

    2. Restarted Logos ((Logos.log)

    • 2x Panel msg displayed & quickly removed, then
    • Library Cat msg displayed
    • Indexer Started
    • Search panel msg displayed
    • Library Cat msg removed
    • Indexer Completed after a while (LogosIndexer.log)
    • Search panel msg removed

    2063.LogosIndexer.zip

    3. Restarted Logos (Logos-2.log)

    • Notification of 409.6 MB Download
    • Initiated download
    • Library Cat msg displayed
    • Search panel msg displayed when download complete; and also got
    • "Resources ready to be added" Notification.
    • Indexer Started, then
    • Library Cat msg removed
    • Indexer Completed after a while (LogosIndexer-2.log)
    • Search panel msg removed

    Differences (where messages appeared) to 1. above have been highlighted

    4. Restart Logos (Logos.log)

    • 2x Panel msg displayed & quickly removed
    • Similar to 2. above thereafter but Library Cat msg was not displayed

    1172.LogosIndexer (2).zip

    Dave
    ===

    Windows 11 & Android 13

  • Ryan Gano (Logos)
    Ryan Gano (Logos) Community Manager, Logos Employee Posts: 409

    Thank you for these reports. We are investigating.

    Ryan

  • Mark Barnes
    Mark Barnes Member Posts: 15,432 ✭✭✭

    I don't know if it's related, but I'm getting frequent "Some search results may be missing…", in the "My Content" section of searches, l don't often look in this section, so I don't know what's normal behaviour, but what seems to be happening is:

    1. I make a change to a document (e.g. by adding highlighting). In the attached log that happens at 06:57:23.
    2. The "Some search results may be missing…" is added, but document indexing doesn't take place.
    3. In the attached log, document indexing didn't occur until 07:40:59. Just before this happened, I'd actually just ran logosindexer.exe manually to see if that would trigger anything. I don't know whether this document indexing was as a result, or was just coincidence.

    1185.Logos.log

    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!

  • Dave Hooton
    Dave Hooton MVP Posts: 35,770

    l don't often look in this section, so I don't know what's normal behaviour, but what seems to be happening is:

    1. I make a change to a document (e.g. by adding highlighting). In the attached log that happens at 06:57:23.
    2. The "Some search results may be missing…" is added, but document indexing doesn't take place.

    The message is new to 7.8, but the indexing has always been delayed.

    3. In the attached log, document indexing didn't occur until 07:40:59.

    It happened within 2 min for the three cases I tried, similar to v7.7. When complete the message was removed.

    Dave
    ===

    Windows 11 & Android 13