After updating search and rebuild index don't work...
I updated to the latest Beta and purchased the American History Collection. Now search is not working and everytime I start Logos 4 it indexes for a while and then the indexer crashes I have tried the rebuild index command twice and it hasn't helped either. There is nothing in the log file about the crash either.
Comments
-
There should be a crash.txt file, but we need some logs to help diagnose the issue.
Dave
===Windows 11 & Android 13
0 -
Also the indexing time just keeps increasing and increasing....
0 -
-
indexer crashed again w/o leaving a log, Here is a shot of what appears on my homepage and indexing isn't even running...
0 -
I don't think we will get a developer to diagnose the log now! But it appears to be crashing at the end of main Library indexing when it writes the postings. Try deleting the LibraryIndex folder and starting L4.
If you check the BibleIndex folder the files should have current date and time to indicate it indexed OK.
Dave
===Windows 11 & Android 13
0 -
Michael Lyman said:
This crash file file indicates a bug in the indexer when processing a specific resource, but it doesn't identify which one. Can you enable logging and post the full Logos4Indexer.log file from a time when it crashes? If we can identify the file and get a copy from you, we should be able to reproduce the problem here and fix it. (That being said, the code that would cause this problem hasn't changed in a very long time, so it's a little strange to me that it only started happening now.)
0 -
I think this is what you need. Does it have anything to do with my last purchase of the American History Collection? Dave I deleted the file as you suggested and it didn't help.
0 -
To diagnose the crash, I'll need to see a Logos4Indexer.log file that ends with the crash. The crash occurred at 10:54am; the log file that was posted shows indexing being paused at 10:44am and then nothing further. The missing 10 minutes would contain the data necessary to identify the problem.
0 -
-
It indexed all night long and now it's at 13 hours!!!
0 -
Indexing must be stuck in a loop. It fluctuates between 10-13 hours left now. The only new software I have installed is Audacity (stable version and beta for Windows 7) and the update for spelling dictionaries in Adobe 9.
0 -
Michael, can you check the indexer log as that will tell you what is going on! You should see entries like
2010-03-20 18:39:42.4898 11 Info BibleIndex (7208ms) Indexing LLS:1.0.60
2010-03-20 18:39:42.4898 11 Info BibleIndex (Timed) Indexing LLS:BRENTONLXXEN
2010-03-20 18:39:42.6458 11 Info DataTypeManager Creating data type bible+brenton (Libronix.DataTypes.Bible.BibleDataType).
2010-03-20 18:39:42.6458 11 Info StandardDataType (Timed) Initializing data type bible+brenton.
2010-03-20 18:39:42.6838 11 Info StandardDataType (34ms) Initializing data type bible+brenton.
2010-03-20 18:39:44.9389 11 Info WindowsIndexerProgress 2 of 140 resources indexed; total progress is 0.8%and
2010-03-20 19:23:16.9773 15 Info LibraryIndex (432ms) Indexing LLS:53.20.22
2010-03-20 19:23:16.9773 15 Info LibraryIndex (Timed) Indexing LLS:53.10.20
2010-03-20 19:23:17.2063 15 Info WindowsIndexerProgress 836 of 883 resources indexed; total progress is 55.5%
2010-03-20 19:23:17.3183 15 Info LibraryIndex (337ms) Indexing LLS:53.10.20
2010-03-20 19:23:17.3183 15 Info LibraryIndex (Timed) Indexing LLS:53.10.4
2010-03-20 19:23:17.5293 15 Info WindowsIndexerProgress 837 of 883 resources indexed; total progress is 55.6%That failing you might also look at the timestamps of the files in your \BibleIndex and \LibraryIndex folders ie. if complete the 7 files will have the same (recent) date/time modified. If not being indexed the 7 files will have an older date/time. If being built there will be extra files (about 14 in total) with a mixture of older and more recent timestamps.
Dave
===Windows 11 & Android 13
0 -
Here are the results of the Bibleindex and the libraryindex with about 10-13 hours left... I re-checked my timeline. I had no problems until after I downloaded the American History Collection, it wouldn't search the new collection and I did a rebuild index command. Friday I had 4.0c installed as well as the Audacity software and I did a lengthy demonstration of the program at school for my instructor who then decided to purchase the software.
0 -
The bible Index is re-built but the library index is still going.
I'm puzzled why there are no logs?
Dave
===Windows 11 & Android 13
0 -
Indexing never stops, it gets as low as 2 hours and 44 minutes and then ramps back up, it's at 5 hours now. I eventually have to kill the process since it slows my computer so much and I have other things to do.
0 -
Michael Lyman said:
Indexing never stops, it gets as low as 2 hours and 44 minutes and then ramps back up, it's at 5 hours now. I eventually have to kill the process since it slows my computer so much and I have other things to do.
The logs should show why. You should post those instead of the screenshots.
MacBook Pro (2019), ThinkPad E540
0 -
Yesterday I ran ccleaner, restarted the computer and deleted the BibleIndex and LibraryIndex files. I let the indexer run and it appeared to be doing the same thing. I woke up, decided to look at the program and saw that the indexer had stopped again, so I looked at the log file folders and saw that nothing had changed so I started the program and... the indexer had done it's job!!! Seems to be working fine now. Thanks for checking into it everyone.
0 -
I have added more books and tried to do a rebuild index command. I have ended up with the indexer screwing up over and over again. It would stop on it's own time after time but left no crash file until today. At the moment I cannot search for ANYTHING. I think all of your developers need to stop everything else and figure out the indexing problems, it seems to be an incessant problem for many users. Here's the file:
0 -
Michael Lyman said:
I have added more books and tried to do a rebuild index command.
Michael, why are you manually rebuilding the index? When books are added L4 will index as necessary.
Michael Lyman said:Here's the file:
The log is from 4 days ago but it points to a possible error with KJV1900.logos4. Remove this file from your Resources folder, ensure permanent logging is ON and start L4. Upload all logs if there is a crash (and before restarting L4).
Dave
===Windows 11 & Android 13
0 -
Thanks AGAIN Dave,
I deleted the file and have restarted Logos 4. I guess I wasn't going to be home for a while and thought if I set it to rebuilt the index it would do the same thing as merging them is supposed to. I won't try it again though if it's a problem.
0 -
The indexer ran all night and was at 5 hours when I went to bed and is at five hours now. I stopped indexing this morning when I looked it up in task manager and saw that it wasn't doing anything.
0 -
Where are the logs?
Your Bible Index is being rebuilt but we need logs to see why it is misbehaving.
Dave
===Windows 11 & Android 13
0 -
-
The indexer quit again on it's own and I can't search a single book in my collection. It says first time indexing is underway and the indexer is not running in task manager. There is NO new log file either. I just looked. Why doesn't the Rebuild Index command work????? Thanks.
0 -
The crash error is the same as the previous one you posted but the indexer log was 4 days old and only shows the error with KJV1900:-
Error LogosResourceIndexer Exception indexing 'C:\Users\Michael Lyman\...Resources\KJV1900.logos4': External component has thrown an exception.
I think you will have to step through this with Technical Support unless Bradley has some more ideas.
Dave
===Windows 11 & Android 13
0 -
"Yesterday I ran ccleaner, restarted the computer and deleted the
BibleIndex and LibraryIndex files. I let the indexer run and it appeared
to be doing the same thing. I woke up, decided to look at the program
and saw that the indexer had stopped again, so I looked at the log file
folders and saw that nothing had changed so I started the program and...
the indexer had done it's job!!! "I finally followed the procedure above from an earlier post of mine and it worked again. I recommend not using the rebuild index command. Next time I add new books or Logos updates books I will wait for the program to decide to re-index when it is ready to. Thanks again Dave and Bradley.
0
