Crash: Indexer keeps crashing.
Moved here from the Logos4 forum.
Background: After getting several new resources, and not having rebuilt my indexes for a long time, I decided to rebuild my indexes by typing that command in the Logos4 command bar. Since then indexing starts, runs for a while and then quits, generating a report to Microsoft. This happens over and over again.
The only log being generated was the "Logos4IndexerCrash.txt" log.
After trial and error I was finally able to get an indexer log after using the enable logging java script, letting the indexer crash, and then restarting Logos4. This restarted the indexer and generated a log. (This is a bit strange because I had enabled logging last night but the indexer would not generate a log, even after restarting L4 and rebooting the system. Maybe I followed slightly different steps this morning.)
I'm including two distinct indexer crash logs which generate different Error ID's. The one I see most often is numbered "7703" and the other, seen infrequently (in the crash log at 17:32) is "152." There is only one difference between those two found on the 7th line from the beginning with "at" (with Word Wrap turned off in Notepad).
Here are those two lines:
- 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.SearchEngine.DocumentIndexer.AddPosting(String strText, LanguageName language, Int32 nOffset, Int32 nLength, Int32 nWordOffset, Int32 nWordLength, String strFields, Int32 nSubOffset, Int32 nSubLength, Int32 nSubWordOffset, Int32 nSubWordLength)
The first is from the indexercrash log, renamed "...Crash_532.txt" the second from the most recent crash. The indexer shows some warnings with several resources, but reports that it successuflly ignored them. Then it crashes.
Here are the log files (2 indexer crashes, the indexer log and the most recent L4 log:
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
Comments
-
Richard,
You've only got half a gig of free space on your drive C. I wouldn't be surprised if that's causing the problem.
Mark
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!
0 -
Mark Barnes said:
Richard,
You've only got half a gig of free space on your drive C. I wouldn't be surprised if that's causing the problem.
Mark
No, I have 429GB of free space on my HD. That's almost half a TB.
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
0 -
First, the Indexer was trying to do a full rebuild of your index when it crashed.
Second, both crashes occurred when the program was trying to post updated indexes to the correct database but before the indexing was complete.
My suggestion is to delete LibraryIndex.db and let the process restart.
BTW: Since the Indexer was trying to do a complete rebuild this may not work, but that's all I can see working at this point.
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
Mark A. Smith said:
My suggestion is to delete LibraryIndex.db and let the process restart.
I failed to report this morning that I did delete all the files in the Library index and Bible index folders, and because I saw it in another thread, deleted the reverse interlinear databases as well. I did this yesterday, before my first request for help.
Do you think it would help to do so again.
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
0 -
I edited my reply while you posted yours. I was unsure if that would work since you were already doing a complete rebuild. If you have already done that it probably won't work. However since you don't have a working index it can't hurt to delete it. It is just the LibraryIndex that is causing the crash. If you try anything, delete the entire LibraryIndex folder (not that I expect that to make much difference). I don't think you need to worry at this point about the Bible Index.
We know what is happening, but we don't know why nor what to do in the absence of that information. Hopefully someone will have some advise other than reinstall, though at this point doing a quick reinstall and transferring in your resources (backed up) won't take a lot longer than just the reindexing since that would be the bulk of what would be left to do after a quick reinstall.
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
I guess it is only fair to add that Rich is not the only person to have this problem. When I updated to the RC last night, I started seeing similar issues.
Blessings,
FloydPastor-Patrick.blogspot.com
0 -
Floyd Johnson said:
I guess it is only fair to add that Rich is not the only person to have this problem. When I updated to the RC last night, I started seeing similar issues.
You know, it's possible that the indexer was running when the upgrade came in. That stopped the index, installed the update and then continued.
Could that be the problem? and if so, how do we fix that?
Just checked the indexer file itself and it's dated 11/30/2010 and shows a vile version of 4.20.4.7882 - so updating/reinstalling isn't likely to solve the issue, unless there's a dll that didn't get updated. There is a file called "Logos4Indexer.exe.config" and another called "Logos4.exe.config) both dated 11/9/2010, but I don't expect config files to be updated every time a program is. There are also a few dll's with older dates, but they seem to be components like L4SmrtTg.dll, SQLite..., etc.
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
0 -
Richard DeRuiter said:
No, I have 429GB of free space on my HD. That's almost half a TB.
Doh, sorry. That's what too much time switching between UK/US and European number formats does for you.
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!
0 -
Richard ~ I'll submit your logs to development. Thanks.
0 -
Melissa Snyder said:
Richard ~ I'll submit your logs to development. Thanks.
Thanks Melissa. I look forward to a fix, or a suggested path to getting this working again (short of uninstall/reinstall, if at all possible).
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
0 -
Richard DeRuiter said:
I look forward to a fix, or a suggested path to getting this working again (short of uninstall/reinstall, if at all possible).
I hope this is possible, but if not, since you have to reindex anyway and since two of the quick install options on the wiki let you transfer your resource files instead of downloading them, there might not be that much of a time hit in going this route.
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
Richard DeRuiter said:Melissa Snyder said:
Richard ~ I'll submit your logs to development. Thanks.
Thanks Melissa. I look forward to a fix, or a suggested path to getting this working again (short of uninstall/reinstall, if at all possible).
You might also try deleting the files in your LibraryIndex folder as a workaround. When a similar error occurred in the past, and the 'rebuild index' command didn't resolve the problem, deleting those files did.
0 -
Melissa Snyder said:
When a similar error occurred in the past, and the 'rebuild index' command didn't resolve the problem, deleting those files did.
As the rebuild command now deletes the index files ("Doing a full re-index because the existing index seems to have been deleted.") I doubt there is any advantage doing that.
The recent solution is to ensure adequate cooling for the hard drive which generates these errors when stressed - use a household fan to direct cooling air in that direction!
Dave
===Windows 11 & Android 13
0 -
Melissa Snyder said:Richard DeRuiter said:Melissa Snyder said:
Richard ~ I'll submit your logs to development. Thanks.
Thanks Melissa. I look forward to a fix, or a suggested path to getting this working again (short of uninstall/reinstall, if at all possible).
You might also try deleting the files in your LibraryIndex folder as a workaround. When a similar error occurred in the past, and the 'rebuild index' command didn't resolve the problem, deleting those files did.
Okay, so I was going to delete my LibraryIndex folder, and accidentally deleted all the contents of my data folder. "Uh-oh" I thought to myself sheepishly. I must have had the focus in a different directory than what I thought. So I downloaded "Recuva" and restored all the files I could and restarted Logos. I got the "Preparing your library; This could take a while" message as Logos set up the indexes and began indexing. Several resources were missing, and I typed in the command Scan <external HD with a back up of my Logos directory> and restarted Logos, which pulled them in. I waited for everything to index, which it did without crashing. Yeah! Then I typed in "Update Resources" and downloaded 432.8MB (the backup directory was old - that backup is now on a regular schedule).
That finished and indexed without crashing the indexer.
Talk about a serendipitous discovery! I wonder which file was deleted that Logos fixed. At least, I'm good to go now.
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
0 -
Richard DeRuiter said:
Okay, so I was going to delete my LibraryIndex folder, and accidentally deleted all the contents of my data folder.
Is this going to be your recommendation from now on?[:D]
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:Richard DeRuiter said:
Okay, so I was going to delete my LibraryIndex folder, and accidentally deleted all the contents of my data folder.
Is this going to be your recommendation from now on?
Well, if it works . . . [;)]
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
0 -
Just in case this is helpful in figuring out why this worked I made a list of files that appear in my current Data subdirectories, but not in the directory of files recovered from my hard drive (by Recuva), and later copied back to where they belong. There were six directories that are not present in the recovered files, and several places where there are simply missing files, though the directory structure is in tact.
Missing Directories:(All files and directories are under Logos4\Data)
AudioPlayer (& subdirectories; but no files here)
DownloadManager (with 2 files: DownloadManager.db, DownloadManager.db-journal)
HistoryManager (with 2 files: history.db, history.db-journal)
KeyLinkManager (with 2 files: keylinkmanager.db, keylinkmanager.db-journal)
ReverseInterlinearManager (with 2 files: reverseinterlinearmanager.db, reverseinterlinearmanager.db-journal)
Updates (with two files: Matadata.db, Metadata.db-journal)
Directory present, but some files missing:
Note the recovery program did not recover 0 byte files. I note that most often these have the db-journal, or lck extension. I will not include those in the list below to save space (though I did above for completeness). But if someone wants me to check specifics, I will.BibleIndex files missing: index.dcm, index.fld, index.idx, index,lxn, libraryIndex.db.
LibraryCatalog files missing: catalog.db, catalog.dcm, catalog.lxn
LibraryIndex files missing: index.idx, index.lxn, supplemental.lxn, supplemental.dcm, index.dcm, supplemental.dcm, supplemental.fld
ResourceManager\ClauseVisualizer files missing: afsyntaxgraphs_2010_10_26T02_20_45Z.mstidx, CSGNT_2009_10_28T21_50_33Z.mstidx, LEXHAMSGNTGRAPH_2009_08_28T13_09_22Z.mstidx, LEXHAMSGNTGRAPH_2009_10_14T22_18_45Z.mstidx, OPENTEXTGRAPH_2009_10_27T19_04_54Z.mstidx
ResourceManager\LemmaLists files missing: Discovered.db
ResourceManager\logos files missing: 242 files with the mstidx extension (if you want I’ll try to find specifically which ones).
ResourceManager\Maps file missing: Discovered.db
ResourceManager\Resources files missing: 339 files missing (I can check specifics if you want, but don’t suspect this is significant information).I hope this helps someone who knows how the program runs can find something here that explains why my other attempts to resolve the indexer crash issue didn't work, but this did.
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
0 -
Richard,
We think the problem could be related to your Sermons resource, as both you and another user with the same crash had references to those files in your logs. Development is requesting copies of your Sermons and Illustrations resources, found in \Documents\Libronix Resources. If you don't want to post them here, you can send them to Logos4Feedback at logos.com.
Thanks,
Melissa0 -
Richard DeRuiter said:
ResourceManager\Resources files missing: 339 files missing (I can check specifics if you want, but don’t suspect this is significant information).
It's actually very likely that one of the resources (I suspect your personal sermons resource created by Sermon File) is causing the crash. I've been able to reproduce the problem with another user's file (http://community.logos.com/forums/p/26674/197229.aspx#197229) but if we can get yours too, we can ensure that the crash you're encountering is also fixed.
0 -
Bradley Grainger said:Richard DeRuiter said:
ResourceManager\Resources files missing: 339 files missing (I can check specifics if you want, but don’t suspect this is significant information).
It's actually very likely that one of the resources (I suspect your personal sermons resource created by Sermon File) is causing the crash. I've been able to reproduce the problem with another user's file (http://community.logos.com/forums/p/26674/197229.aspx#197229) but if we can get yours too, we can ensure that the crash you're encountering is also fixed.
I just sent them to the address Melissa mentioned above.
BTW, I just checked the resource folder for the recovered file and notice that the LogosUsersermons.lbxlls file is NOT in the list of recovered files. I might also note that that file was open in my layout at the time of the index crashing issue that started this thing.
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
0 -
Richard DeRuiter said:
I might also note that that file was open in my layout at the time of the index crashing issue that started this thing.
Rich, if this is what your sermons are doing to your computer, what are they doing to your congregation? [;)]
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
We've fixed the problem; the bug fix will be in the next RC.
0 -
Bradley Grainger said:
We've fixed the problem; the bug fix will be in the next RC.
Will this improve Rich's sermons, too? *wink*
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
Mark A. Smith said:Bradley Grainger said:
We've fixed the problem; the bug fix will be in the next RC.
Will this improve Rich's sermons, too? *wink*
I'll check and get back to you Mark. Some of those sermons do have weak endings. Maybe one just didn't really end at all, and that caused the whole mess.
Mark A. Smith said:Rich, if this is what your sermons are doing
to your computer, what are they doing to your congregation?
Just saw that quote, and couldn't help but respond. You see Mark, my sermons have a never-ending impact on my congregation [clears throat].
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
0 -
Bradley Grainger said:
We've fixed the problem; the bug fix will be in the next RC.
Thanks Bradley. I saw the same message in the other, similar thread. I'll bait my breath and look to it forwardly.
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
0 -
Richard DeRuiter said:
You see Mark, my sermons have a never-ending impact on my congregation [clears throat].
Better than mine. My folks just think my sermons never end.
Richard DeRuiter said:I'll check and get back to you Mark. Some of those sermons do have weak endings. Maybe one just didn't really end at all, and that caused the whole mess.
If it works many of us will want to know and get our sermons into Logos right away. Keep us posted.
Pastor, North Park Baptist Church
Bridgeport, CT USA
0
