Logos 5 No Longer Indexing
I started this reply at https://community.logos.com/forums/p/176250/1018137.aspx#1018137
Because I have invested more on Logos than on computers in the last several years, I'm still running a version of Windows that only supports Logos 5 (and have invested in Logos 8). About a week ago, my the Logos Indexer started crashing, and when looking at the Log Dumps (in Documents/Logos Log Files folder), the problem seems to be that it goes to parts of the Logos Website for indexing, and these areas are no longer responding. One may imagine this is part of the phase-out program, now that Logos 8 is up and running, hope this helps others having the same problem. So basically, anything new we purchase (or files Logos updates) can still be downloaded, but will not be indexed and may not appear (correctly) in searches.
Comments
-
Hi Anthony
Please post log files
Graham
0 -
Ok, here... thank you if you can discover anything helpful.Graham Criddle said:Please post log files
3250.Logos Log Files.zip0 -
I'm not sure there is much we are going to be able to do.
With similar reports of the same crash the advice was to upgrade to the latest version of Logos 6 - https://community.logos.com/forums/t/115637.aspx
But from what you've said that's not possible for you.
Are you able to enable full diagnostic logging and post the logos.log file after a crash? The one have included here is very old.
0 -
Anthony Grubb said:
So basically, anything new we purchase (or files Logos updates) can still be downloaded, but will not be indexed and may not appear (correctly) in searches.
Due to server security changes on 7 Nov 2018 => https://www.logos.com/logos-7-update Logos, Verbum, and Noet application releases prior to 7.18 cannot establish a secure connection with Faithlife servers (so every network connection attempt will have a timeout error). Hence, resource purchase(s)/update(s), sync, ... cannot be done so older releases can only be used offline: manual possibility for resource update(s) is using an application release that can securely connect & download them followed by using scan command in older installation to copy updated resource files and index them.
Anthony Grubb said:
Ok, here... thank you if you can discover anything helpful.Graham Criddle said:Please post log files
3250.Logos Log Files.zipLogosIndexerError.log has many device I/O errors in 2016 & 2017. Earlier in 2018, noted database disk image is malformed. The "key was not found in collection" error began appearing on 27 Nov 2018. Appears last successful Indexing happened using Logos 5.2b Beta 6 on 11 Aug 2014 while LogosIndexerCrash.txt and LogosIndexerError.log show Logos 5.2b SR-11 crashing (along with history of device I/O errors so have doubts about older storage device reliability).
LogosError.log is showing network connection errors with Faithlife, which is expected for older application release due to server security changes. Suggest changing Program Settings for Use Internet to No
Keep Smiling [:)]
0 -
Due to server security changes on 7 Nov 2018 => https://www.logos.com/logos-7-update Logos, Verbum, and Noet application releases prior to 7.18 cannot establish a secure connection with Faithlife servers (so every network connection attempt will have a timeout error). Hence, resource purchase(s)/update(s), sync, ... cannot be done so older releases can only be used offline...
Suggest changing Program Settings for Use Internet to No
Keep Smiling
Thank you, although I did a completely new installation of Logos 5 about a year ago and it seemed to work really well--it wouldn't surprise me if there were a storage read error before that. It also went through the indexing sequence fine just fine until about a week ago, going through the whole 0-100%. You mention in there a date of Nov 27th, and that would be about the time this really started crashing for me. I've set the Program Setting per your suggestion, that should work until can get things updated, thank you! [:)]
0 -
Anthony Grubb said:
It also went through the indexing sequence fine just fine until about a week ago, going through the whole 0-100%.
When diagnostic logging is disabled, then LogosIndexer.log is not updated. An idea for Indexer context of crash is enabling => Diagnostic Logging followed by restart of indexing: launch application OR restart Windows. If Indexer crash repeats, then could upload zip file that has LogosIndexer.log with today's date.
Keep Smiling [:)]
0 -
Anthony Grubb said:
About a week ago, my the Logos Indexer started crashing, and when looking at the Log Dumps (in Documents/Logos Log Files folder), the problem seems to be that it goes to parts of the Logos Website for indexing, and these areas are no longer responding.
This is an incorrect diagnosis. The indexer does not retrieve any information from Logos servers when building the index; it can function entirely offline.
It's been a long time since I posted the reply at https://community.logos.com/forums/p/115637/764746.aspx#764746, but I think the cause was attempting to index a reverse interlinear resource that Logos 5 can't actually process. (Normally we don't distribute resource files to applications that can't read them; however, a configuration error caused this to be downloaded by Logos 4 and 5. The only way to truly fix the problem would have been shipping a new update for Logos 4 and 5, but they were unsupported so that wasn't going to happen.)
Your LogosIndexer.log file is very old, so it doesn't show the problem. If you're able to upload LogosIndexer.log from a session where the indexer crashes, we may be able to pinpoint the reverse interlinear that's causing the problem so you can delete it.
0
said:
