Twice now my L4 has tried to reindex- and both times it has stopped working- anyone else have this issue?
Log files7041.Logos4Indexer.log
Has been stopping at 2 hr 54 mns
There have been several users reporting crashes with indexing. However, the log you have sent through doesn't show any errors. This could be because the indexer completed the previous time it ran. How do you know indexing hasn't worked?
Whyndell,
There does not appear to be a problem..
How exactly has it tried to reindex...?
It goes thru the 1,2,3 downloaded the update, then starts indexing- but always errors out at 2 hrs and 50 mins- "Logos Bible sofwar Indexr Has sopped working
Rindex was the wrong word to use- it hs ben tying to index sice I updated he latst beta today.
sorry for the typo's just replaced the batteries in my keyboard
It trys to index everytime I open L4
I also installed latest beta on machine #2 went without a hitch, the problem is with my primary, #1
Whyndell -- I am also experiencing errors with the update to L4a. I did notice that I was running out of disk space and am now in the process (for the fourth or fifth time) of reindexing with a great deal of free disk space. I will report if it finishes or not.
Floyd
New log
1325.Logos4Indexer.log
Stopped working with 1 hr 34 mins to go
7737.Logos4Indexer.log
And mine has stopped again saying I need at least 1 GB of free space. I started with 6+ GB, when it stopped the drive said I had 3.08 GB free. This is getting tiring.
I have over 120 gb of hd and plenty of RAm- so I'm good there, according to the log I have some type of error.
If one of the techies can let me know what to do- I'll do it in the a.m. going to bed - good night.
How do you create the log?
I had a similar issue. I killed the Logos4indexer.exe process in task manager, and then did Rebuild Index from the command box to do it from scratch, completed with no problems...
Go to this page: http://wiki.logos.com/Diagnostic_Logging
There are definitely some indexing problems with this version. I'd firstly try again. If it fails with the same error at the same place (compare the two logs), then John's suggest will probably be best. I think an earlier crash has given you a buggy index, and the indexer is now crashing on merge.
Jon
Followed your advise and just re-index fully, it completed this time with no issues thanks.
