Indexer has stopped working
Has anyone else got this today - Logos downloaded a 160 plus file and when it goes to index it, the program keeps asking to close. Why am I expecting there to be another file to fix this like last time? :-)
Comments
-
Yes, same here. Looks like it is being reported on some other threads also.
0 -
Downloaded the resources and it added them, started indexing, and then the message comes up indexer stopped working. I am using the Beta.
Mission: To serve God as He desires.
0 -
It would be helpful if everyone reporting a crash would at least share the version of Logos you're using and whether it's Mac or PC.
The Indexer log would be nice too, if you have it.
MacBook Pro (2019), ThinkPad E540
0 -
Same here!
EDIT: PC, Logos 4.2a SR-3.
0 -
Experiencing same problem after downloading a 170 MB update on Mac side; using 4.2a SR-4 (4.21.5.0947).
__________
15" rMBP 2.6 GHz i7 | 16 GB RAM | 1.0 TB Flash Drive | OS X 10.12.3 | Logos 7.0 (7.3.0.0062)
0 -
Todd - Logos 4 is the version. I typed in *rebuild Indexer* --- I'm going to be out for a bit but I might have the Fire Department on speed dial - the cpu is reving up to the point where this Laptop might tear right out into orbit.
0 -
Please follow the steps here to work around the problem: http://community.logos.com/forums/p/32065/238705.aspx#238705
0 -
This doesn't work - at least for me. It got to about 26% and stopped working again.
0 -
Bootjack said:
This doesn't work - at least for me. It got to about 26% and stopped working again.
I think Logos will want to see a log file. Do you have one? If not it would be good to enable diagnostic logging permanently, close and reopen Logos to trigger a new indexing session, then zip up the Indexer log file and the crash log file together if a crash occurs, and attach them to another post.
Here's how: http://wiki.logos.com/Diagnostic_Logging
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
Hi Mark,
I did the *rebuild Index* and when I rumbled back into my Study just now, I see that everything seems to be ok. The Indexing has obviously completed (no more messages that the Indexing wants to close down). Would you then assume also that everything, including the latest update file, should be properly indexed? And if you wish, I do have two logs (Logos4crash / Logos4indexercrash) that I can post to a new topic. I'll appreciate any furthered advice. Thanks Mark.
0 -
Sorry for the delay in getting back to you. The answer is in the log files. If you have diagnostic logging enabled, the Logos4Indexer.log file will show that you successfully completed the indexing process (look at the end of the file to see if there was a successful completion of the process). If so there will also be no Logos4IndexerCrash.txt file that is dated after indexing began.
Alternately, if you try to do a search and get a warning that indexing hasn't been completed so results may not be complete, that is another way to know indexing did not finish correctly. If you can search, don't get the warning, and find results in the resources you think were indexed, the indexing was completed.
Pastor, North Park Baptist Church
Bridgeport, CT USA
0
