Indexer crash when new or updated resources are available for download

(Windows Vista). The indexer seems to crash periodically while it is doing (another) first time indexing.

The cause of the indexer crash seems to be that new resources are available for download.

As soon as windows reports that the indexer has stopped and the crash window is closed, then Logos 5 imediately starts to download the new resources / updates and then wants to be restarted. Indexing then resumes until additional resource updates are available for download.

Find more posts tagged with

Comments

Dave Hooton

David

We need to see some logs to understand what is happening (and to know what version of Logos you are running). Please enable logging so that we get the detailed logs (Logos.log and logosIndexer.log).

David Wilson

https://community.logos.com/discussion/comment/556990#Comment_556990

8867.Logos 20140101.log

Had to delete a significant amount of the "middle" of the Indexer Log as it covered about 2 and a half hours of indexing (to just over 30%) and at almost 8MB was too large to upload. Can send via DropBox if full Indexer Log is needed, but hope the attached contains all the needed information)
Deleted sections are indicated by blank lines and a comment marked by ** comment on what was deleted **

8535.LogosIndexer 20140101 beginning and end.log

After acknowledging the crash, the Indexer restarted with the following new Indexer Log:

5444.LogosIndexer 20140101_2.log

Logos (5.2 SR-3, version 5.2.0.0091 on Microsoft Windows NT 6.0.6002 Service Pack 2 (actually Windows Vista but that it how it gets identified)). Pid: 10120

There was no LogosError.log or LogosIndexerError.log produced today.

The new resources which seemed to stop/crash the indexer were some of today's Vyrso freebies.

David Wilson

https://community.logos.com/discussion/comment/557265#Comment_557265

Second Indexer Crash today, shortly after I picked up the remaining titles in a Noet bundle:

7534.LogosIndexer 2014Jan01 second crash re Noet.log

Dave Hooton

https://community.logos.com/discussion/comment/557301#Comment_557301

David,

Well done with the logs, but please note that there was no crash. A cycle of download -> index -> cancel index -> download is going on. I recommend

Set Logos to NOT Automatically Download Updates in Program Settings & ignore download requests whilst indexing is underway
delete C:\Users\DaveJ\AppData\Local\Temp\Logos-DownloadProgress-ahvpe21q.04s.db, or similar, provided Logos is not downloading.

So if indexing is currently underway ignore any download notification. If downloading resources then let them be indexed!

When indexing finishes you can let any further download proceed.

(Logos should examine these logs to see why this is happening).

Dave Hooton

https://community.logos.com/discussion/comment/557265#Comment_557265

Had to delete a significant amount of the "middle" of the Indexer Log as it covered about 2 and a half hours of indexing (to just over 30%) and at almost 8MB was too large to upload.

The wiki article from my first reply has a section on How to “zip” the log files or compress them (typically 10% of full size).

David Wilson

https://community.logos.com/discussion/comment/557325#Comment_557325

Thanks Dave:

The decision to stop the indexing is made by the software (Logos is currently set to automatically download updates):
Windows notifies me that the Logos5 Indexer has stopped.
I have to close that notification manually before Logos5 will advise that there are resources available to download.

As the "First Time" indexing is currenty 94% complete I will let it run its course on this occasion.

Normally it can index newly downloaded resources before anything else is available for download.

If it ever starts a "First Time" indexing agin I will change from Automatically download updates and ignore until indexing is complete, as suggested above.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/557420#Comment_557420

Windows notifies me that the Logos5 Indexer has stopped.

Without a dump file, I can't say for sure, but I think this is a bug we've already found and fixed for 5.2a.

David Wilson

https://community.logos.com/discussion/comment/557498#Comment_557498

This MIGHT help a little (or may just confuse things). My system just downloaded and Indexed the Journal of Biblical and Pneumatological Research (released today). The Indexer Log suggests everything went as might be expected. Nevertheless, Microsoft Windows reported that the "Logos Bible Software 5 Indexer has stopped working" A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available. There were no related crash logs. Attached are the Logos and LogosIndexer Logs.

It may be that there is some abnormal termination issue at the point that the Indexer is stopping by design. There does not seem to be anything in the log to suggest a problem, but Microsoft Windows thinks there is a problem.

4784.LogosIndexer 2014Jan02.log
5344.Logos 2014Jan02.log

Once I hit the "Close Program" button on the Microsoft Windows message, the Indexer icon disappears from the taskbar when the mouse cursor comes close to it, but the Indexing line at the top of the Logos software window still remains with the message the "Your library is indexing" until closed manually.

Dave Hooton

https://community.logos.com/discussion/comment/557575#Comment_557575

Is there a Windows event Log at roughly Jan 2nd, 6:19 pm?

David Wilson

https://community.logos.com/discussion/comment/557857#Comment_557857

Yes, indeed there is: what do you make of the Libronix.DigitalLibrary.Logos.dll reference ? (the system does have Libronix 3 installed still)

Have attached the referenced ".wer" file with ".txt" added to enable upload here
7701.Report.wer.txt

Log Name:      Application
Source:        Application Error
Date:          02/01/2014 6:19:30 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Aidan2
Description:
Faulting application LogosIndexer.exe, version 5.2.0.91, time stamp 0x5294f66a, faulting module Libronix.DigitalLibrary.Logos.dll, version 5.2.0.91, time stamp 0x5294f64e, exception code 0xc0000005, fault offset 0x00055e38, process id 0x%9, application start time 0x%10.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-01-02T22:19:30.000Z" />
    <EventRecordID>2320273</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Aidan2</Computer>
    <Security />
</System>
<EventData>
    <Data>LogosIndexer.exe</Data>
    <Data>5.2.0.91</Data>
    <Data>5294f66a</Data>
    <Data>Libronix.DigitalLibrary.Logos.dll</Data>
    <Data>5.2.0.91</Data>
    <Data>5294f64e</Data>
    <Data>c0000005</Data>
    <Data>00055e38</Data>
</EventData>
</Event>

Log Name: Application Source: Windows Error Reporting Date: 02/01/2014 6:33:45 PM Event ID: 1001 Task Category: None Level: Information Keywords: Classic User: N/A Computer: Aidan2 Description: Fault bucket 3986767566, type 1 Event Name: APPCRASH Response: None Cab Id: 0

Problem signature: P1: LogosIndexer.exe P2: 5.2.0.91 P3: 5294f66a P4: Libronix.DigitalLibrary.Logos.dll P5: 5.2.0.91 P6: 5294f64e P7: c0000005 P8: 00055e38 P9: P10:

Attached files: C:\Users\DaveJ\AppData\Local\Temp\WERD1DC.tmp.version.txt

These files may be available here: C:\Users\DaveJ\AppData\Local\Microsoft\Windows\WER\ReportArchive\Report2999db2f Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Windows Error Reporting" /> <EventID Qualifiers="0">1001</EventID> <Level>4</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2014-01-02T22:33:45.000Z" /> <EventRecordID>2320274</EventRecordID> <Channel>Application</Channel> <Computer>Aidan2</Computer> <Security /> </System> <EventData> <Data>3986767566</Data> <Data>1</Data> <Data>APPCRASH</Data> <Data>None</Data> <Data>0</Data> <Data>LogosIndexer.exe</Data> <Data>5.2.0.91</Data> <Data>5294f66a</Data> <Data>Libronix.DigitalLibrary.Logos.dll</Data> <Data>5.2.0.91</Data> <Data>5294f64e</Data> <Data>c0000005</Data> <Data>00055e38</Data> <Data> </Data> <Data> </Data> <Data> C:\Users\DaveJ\AppData\Local\Temp\WERD1DC.tmp.version.txt</Data> <Data>C:\Users\DaveJ\AppData\Local\Microsoft\Windows\WER\ReportArchive\Report2999db2f</Data> </EventData> </Event>

Problem signature: P1: LogosIndexer.exe P2: 5.2.0.91 P3: 5294f66a P4: Libronix.DigitalLibrary.Logos.dll P5: 5.2.0.91 P6: 5294f64e P7: c0000005 P8: 00055e38 P9: P10:

Attached files: C:\Users\DaveJ\AppData\Local\Temp\WERD1DC.tmp.version.txt

Dave Hooton

https://community.logos.com/discussion/comment/557951#Comment_557951

what do you make of the Libronix.DigitalLibrary.Logos.dll reference ?

The name lingers with all installations of Logos 4/5!

Logos may request a further log if they feel they haven't already fixed the problem.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/557575#Comment_557575

It may be that there is some abnormal termination issue at the point that the Indexer is stopping by design.

This appears to be the case, and (if so) is a bug that's already fixed in 5.2a. Since the Indexer was already shutting down, nothing "bad" is happening, other than the crash dialog appearing. I think you can ignore it for now and wait until 5.2a ships.

David Wilson

https://community.logos.com/discussion/comment/558128#Comment_558128

Thanks Bradley: Thanks Dave.