Another indexer problem
Howdy. I've been following various indexer problems and I think posting a log file is what you guys will want. I hope this is the one you want.
Hope you can help me. My indexer crashes everytime I use it. Thanks in advance.
Comments
-
William,
We'd need to see the Logos4Indexer.log file which should be in the same folder as the file you already uploaded. Please upload that.
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
There are no other files in the directory I just sent.
0 -
William Tarbush said:
There are no other files in the directory I just sent.
You'll need to turn on full logging before trying to index again:
http://wiki.logos.com/Diagnostic_Logging
Then it will generate the helpful log files when it runs.
MacBook Pro (2019), ThinkPad E540
0 -
I didn't get a Logo4Idexer.log file. Only a Logos4.log file out of my index after adding the java script to my registry. 0044.Logos4.log
0 -
Indexing may still be going if the Logos icon is in the Windows Task Bar?
If not running is everything OK?
Dave
===Windows 11 & Android 13
0 -
It says it is indexing on the home screen and the search screen. The indexer gave me two "not responding" Windows errors while it was running.
0 -
The KJV1900 caused a crash in this log. You can stop the indexer using Windows Task manager, close L4, and delete the files KJV1900OT.lbsrvi and KJV1900.logos4 from your resources folder: C:\Users\{User Name}\AppData\Local\Logos4\Data\{Random String}\ResourceManager\Resources
Restart Logos to have L4 redownload the files.
If the indexer starts kill it in Windows Task Manager. Then type Rebuild Bible Index in the Command Bar and hit enter. If this completes successfully you'll need to rebuild your library index. Type Rebuild Library Index in the Command Bar, hit enter and wait a long while. Any other issues upload the log files.
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
William Tarbush said:
The indexer gave me two "not responding" Windows errors while it was running.
It provided a familiar error with KJV1900 and spent 1.7 hrs spinning its wheel! You may as well kill Logos4Indexer.exe in Task Manager. We don't have a real solution for this and I think Technical Support will be the best to contact if a Logos technician does not intervene here before Monday.
Meanwhile, you look at the threads mentioned here for some suggestions.
EDIT: Also try what Mark suggested above.
Dave
===Windows 11 & Android 13
0 -
Any news to report?
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
Just got forwarded to a Level 2 Tech. On the phone right now.
Edit: after indexing and talking to a level 2 tech everything is working as usual.
0 -
William Tarbush said:
Edit: after indexing and talking to a level 2 tech everything is working as usual.
Other than talk to the tech did you or he do anything that explains why everything is back to normal?
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
remotely, she made sure kjv1900 and the nasb interlinear were recognized through an hour long process.
0 -
William Tarbush said:
an hour long process
Wow. This is helpful to hear. Thanks for following back up.
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
I'm assuming this is not uncommon? Here's my log.
[quote]Error ID: 6382
Error detail: IndexingException: Object reference not set to an instance of an object.
Libronix.DigitalLibrary.Logos.IndexingException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object.
at Libronix.SearchEngine.Lexicon.GetOrAddTermId(DataTypeReference objDataTypeReference)
at Libronix.SearchEngine.LexiconCache.DataTypeReferenceCache.AddNewItem(DataTypeReference key, BucketTermId& item)
at Libronix.SearchEngine.LexiconCache.RotatingCache`2.GetOrAdd(TKey key)
at Libronix.SearchEngine.DocumentIndexer.AddPosting(DataTypeReference objReference, Int32 nOffset, Int32 nLength, Int32 nWordOffset, Int32 nWordLength, String strFields, Int32 nSubOffset, Int32 nSubLength, Int32 nSubWordOffset, Int32 nSubWordLength)
at Libronix.DigitalLibrary.Logos.LogosResourceIndexer.ProcessReverseInterlinearIndexData(NativeLogosResourceIndexer* pNativeIndexer, Char* pszSourceId, ReverseInterlinearColumnIndexData* pData, Int32 nDataCount)
at Libronix.DigitalLibrary.Logos.Callback.ProcessReverseInterlinearIndexData(Callback* , NativeLogosResourceIndexer* pNativeIndexer, Char* pszSourceId, ReverseInterlinearColumnIndexData* pData, Int32 nDataCount)
--- End of inner exception stack trace ---
at Libronix.DigitalLibrary.Logos.Callback.{dtor}(Callback* )
at Libronix.DigitalLibrary.Logos.LogosResourceIndexer.DoIndexResource(IDocumentIndexer documentIndexer, IWorkState workState, TitleLoader* pTitleLoader, basic_string<wchar_t\,std::char_traits<wchar_t>\,std::allocator<wchar_t> >* strReverseInterlinearDataType, Boolean bCurrentTitleSupportsMorph)
at Libronix.DigitalLibrary.Logos.LogosResourceIndexer.IndexResource(auto_handle<Libronix::SearchEngine::IDocumentIndexer> documentIndexer, IWorkState workState, TitleLoader* pTitleLoader, Boolean bCurrentTitleSupportsMorph)
at Libronix.DigitalLibrary.Logos.LogosResource.IndexContent(IIndexer indexer, ResourceManager resourceManager, ReverseInterlinearManager reverseInterlinearManager, ResourceClassifier resourceClassifier, IWorkState state)
at Libronix.DigitalLibrary.LibraryIndex.IndexNextResource(ILibraryIndexWorkState state, Indexer indexer)
at Libronix.DigitalLibrary.LibraryIndex.SecondaryIndexThread(Object objState)
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart(Object obj)Win 7 x64 | Core i7 3770K | 32GB RAM | GTX 750 Ti 2GB | Crucial m4 256GB SSD (system) | Crucial m4 256GB SSD (Logos) | WD Black 1.5 TB (storage) | WD Red 3 TB x 3 (storage) | HP w2408h 24" | First F301GD Live 30"
0 -
Jonathan,
Without the Logos4Indexer.log file we can't be sure. Your problem does seem to have to do with Reverse Interlinears which have been the center of others' problems. You can upload that file if you have time. If it is the same issue, Melissa from Logos posted their solution to the problem others were having. Since not too many of us will be around today you may decide to try it:
- Delete the NASB95.logos4,
NASBOT.lbsrvi, NASBNT.lbsrvi, KJV1900.logos4, KJV1900NT.lbsrvi, and
KJV1900OT.lbsrvi files.
They are in
C:\Users\userfolder\AppData\Local\Logos4\Data\uniquefolder\ResourceManager\Resources.
deleted, restart Logos 4 and enter the command Update
Resources.
Allow the program
to download the updates and restart Logos 4 again.
After Logos 4 loads
check your library to make sure the Bibles have completely
re-downloaded:
Open the King James
Version (1900) and make sure the Interlinear Data is available in the Old and
New Testaments.
Repeat with the New
American Standard Bible (1995).
If the books do not
show up they may be still in the Downloaded folder.
Close Logos
4 and
go to the following location
C:\Users\userfolder\AppData\Local\Logos4\Data\ uniquefolder
\ResourceManager\
Delete the
ResourceManager.db file and restart Logos 4 to force
discovery.
After Logos 4
reopens repeat step 4, if the Bibles appear to confirm the interlinear
information is there as well.
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 - Delete the NASB95.logos4,
-
Oh right ok. I thought the actual crash log file would be the logical one to upload. Here you go. I'll do what you suggest as well.
Win 7 x64 | Core i7 3770K | 32GB RAM | GTX 750 Ti 2GB | Crucial m4 256GB SSD (system) | Crucial m4 256GB SSD (Logos) | WD Black 1.5 TB (storage) | WD Red 3 TB x 3 (storage) | HP w2408h 24" | First F301GD Live 30"
0 -
Jonathan Burke said:
Oh right ok. I thought the actual crash log file would be the logical one to upload. Here you go. I'll do what you suggest as well.
Okay, I'm not known for my prowess in deciphering these but it looks like it could be one of two problems. Here is the relevant info:
2010-12-25 21:15:11.2573 7 Info BibleIndex (Timed) Indexing LLS:1.0.171
2010-12-25 21:15:12.1504 11 Info WindowsIndexerProgress 117 of 225 resources indexed; total progress is 30.5%
2010-12-25 21:15:36.6808 12 Info WindowsIndexerProgress 0.0691 = 0.25 * (1.00 * 0.00 + 0.47 * 0.59 + 0.00 * 0.41 + 0.00 * 0.00) after 16.0m
2010-12-25 21:15:36.6808 1 Info Program Setting notification icon tool tip to: Logos Bible Software is indexing (3h 33m remaining)
2010-12-25 21:16:01.8562 10 Info WindowsIndexerProgress 118 of 225 resources indexed; total progress is 30.7%
2010-12-25 21:16:06.7005 12 Info WindowsIndexerProgress 0.0692 = 0.25 * (1.00 * 0.00 + 0.47 * 0.59 + 0.00 * 0.41 + 0.00 * 0.00) after 16.5m
2010-12-25 21:16:06.7005 1 Info Program Setting notification icon tool tip to: Logos Bible Software is indexing (3h 37m remaining)
2010-12-25 21:16:25.6396 7 Error Program Unhandled exception: Libronix.DigitalLibrary.Logos.IndexingException: The database disk image is malformed
database disk image is malformed ---> System.Data.SQLite.SQLiteException: The database disk image is malformed
database disk image is malformedResource LLS:1.0.171 is the NLT, which is also a reverse interlinear. RI's have been known to cause issues with indexing in 4.2. The crash report above, also looks consistent with RI indexing problems by others.
However the error message here points to a malformed database, suggesting that the issue could be there, even though the indexer was indexing the NLT on the same thread.
The error here is not the same error as in the error report, above, and makes me wonder whether there is more than one issue going on here.
Either way, if removing the KJV1900 and NASB lbsrvi files don't fix the problem, also remove the NLTNT.lbsrvi, restart and it should redownload and reindex.
If that doesn't do it, post the indexer logs again and we'll see if the database issue continues. If so, we'll need to rebuild your Bible indexes. This can be done by typing Rebuild Bible Index in the Logos command bar. Doing so, can take some time, so you may want it to run at a time when you're not using your computer.
[BTW, it would seem that the crash log would provide enough relevant data to solve the issue. But so far it only reports the type of error, not the specific cause.]
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
0 -
Thanks Richard. I went through the entire process suggested by Mark and I'm back where I started, with the indexer still crashing. I'll try removing the NLTNT.lbsrvi.
Win 7 x64 | Core i7 3770K | 32GB RAM | GTX 750 Ti 2GB | Crucial m4 256GB SSD (system) | Crucial m4 256GB SSD (Logos) | WD Black 1.5 TB (storage) | WD Red 3 TB x 3 (storage) | HP w2408h 24" | First F301GD Live 30"
0 -
I agree with Richard's analysis. The Indexer log is showing a different problem than the Crash log. The problem in the Indexer log is the NLT but the form of the error message suggests that the entire Bible index needs to be rebuilt.
If you seem to get nowhere by deleting the NLT try typing Rebuild Bible Index in the Command Bar, hit enter and see if you can rebuild the index successfully. Again upload log files any time there is a crash.
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
Thanks guys. Everything is cool now, looks like it was the NLTNT. Logos also downloaded 1.33GB of updates for some reason, and maybe that helped.
Win 7 x64 | Core i7 3770K | 32GB RAM | GTX 750 Ti 2GB | Crucial m4 256GB SSD (system) | Crucial m4 256GB SSD (Logos) | WD Black 1.5 TB (storage) | WD Red 3 TB x 3 (storage) | HP w2408h 24" | First F301GD Live 30"
0 -
I'm also having an index issue and was able to turn on the diagnostics, but I'm not sure what the issue is. I would appreciate if someone could help me figure out what I need to do in order to correct this. I've attached the log file I think you need.
0 -
The culprit is your KJV1900 Reverse Interlinear. Follow these instructions and let us know the outcome:
- Delete the NASB95.logos4,
NASBOT.lbsrvi, NASBNT.lbsrvi, KJV1900.logos4, KJV1900NT.lbsrvi, and
KJV1900OT.lbsrvi files.
They are in
C:\Users\userfolder\AppData\Local\Logos4\Data\uniquefolder\ResourceManager\Resources.
deleted, restart Logos 4 and enter the command Update
Resources.
Allow the program
to download the updates and restart Logos 4 again.
After Logos 4 loads
check your library to make sure the Bibles have completely
re-downloaded:
Open the King James
Version (1900) and make sure the Interlinear Data is available in the Old and
New Testaments.
Repeat with the New
American Standard Bible (1995).
If the books do not
show up they may be still in the Downloaded folder.
Close Logos
4 and
go to the following location
C:\Users\userfolder\AppData\Local\Logos4\Data\ uniquefolder
\ResourceManager\
Delete the
ResourceManager.db file and restart Logos 4 to force
discovery.
After Logos 4
reopens repeat step 4, if the Bibles appear to confirm the interlinear
information is there as well.
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 - Delete the NASB95.logos4,
-
Thanks! I had to go through the more extensive steps to get the index to build, but it worked! I really appreciate your help and patience!
Merry Christmas.
0
