Indexer Crash - 4.6 B5

A Logos-driven devotional update came down the pipe, which I downloaded. (I'd left L4 with all resources closed, & that's how it still was.)

Went to install it, but icon in system tray disappeared as I was headed down to install it.

Instead, closed & reopened L4. (blank layout)

Indexing began, but icon in system tray ALSO offered to install 4.6 RC1.

I clicked install.

Indexer crashed.

All logs with tonight's date are attached.

2514.Logos4IndexerCrash.txt

7462.Logos4IndexerError.log

6521.Logos4Error.log

Find more posts tagged with

Comments

Tonya J Ross

The IndexCrash.txt file indicates a malformed database here:

C:\Users\Bill\AppData\Local\Logos4\Data\v0n4xkdf.03w\LibraryIndex\supplemental-build.lxn

You should try closing the app and deleting that file; it should automatically rebuild when you reopen. You will likely have to do some indexing at that point so it may be best to do it at a time when you are not busy (if you have any time like that). [;)]

EDIT: the file will likely be called 'index.lxn' and not actually 'supplemental-build.lxn'.

BillS

https://community.logos.com/discussion/comment/392250#Comment_392250

Hi Tonya,

When I restarted Logos after the crash, it automatically did start indexing. Now, it seems to be humming along just fine. Do I still need to reindex?

Is there any possibility that the crash is related to the fact that L4 offered AND I CLICKED on "Update" PRIOR to its finishing the indexing from the download? That this was an "ungraceful" exit from indexing in order to update the s/w?

Tonya J Ross

https://community.logos.com/discussion/comment/392253#Comment_392253

If it is indexing now, I'd leave it alone unless you encounter further issues. [:)]

BillS

https://community.logos.com/discussion/comment/392254#Comment_392254

If it is indexing now, I'd leave it alone unless you encounter further issues.

Tonya,

It finished indexing yesterday. (I didn't wait for a response but started L4 again immediately after posting--waited long enough to ensure that logs were in the same state they were in post-crash.) It's humming along fine as if it's happy with the index. No further issues.