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:

5557.Logos4IndexerCrash.zip.

Find more posts tagged with

Comments

Mark Barnes

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

Rich DeRuiter

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.

Mark Smith

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.

Rich DeRuiter

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.

Mark Smith

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.

Floyd Johnson

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.

Mark Barnes

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.