4.2 Beta 7 indexing and warnings
It started at 22.59 last nite (2/15/2011) and at 6.07 (2/16/2011) it is at 99%- it is now 6.36 a.m. and it is still 99%.
This is the first time the indexing has really affected the performance of my Dell 1750- any idea how long it may sit at 99%.
File attached there are some warnings regarding Warfield if someone could take alook.
Comments
-
*****Update******
Indexing just quit- great.
Please still look at the warnings in the indexer log.
0 -
Whyndell,
I don't see anything unusual regarding the Warfield warnings they seem to consist of non-implemented tagging and such. Not a real concern.
Overall it looks like the indexing completed successfully at Line 15481 where the postings started being written at 77%. just before 4PM. It proceeds to 6am where the writing of postings increase to 99% And there the log terminates.
Do you still have the final log for when the indexer quit? I'd like to see that one. And a crash report.txt if one was generated.
Sarcasm is my love language. Obviously I love you. 0 -
Thomas Black said:
Do you still have the final log for when the indexer quit? I'd like to see that one. And a crash report.txt if one was generated.
Yes, please provide the full indexer log (and any crash file).
0 -
Here's the last log when it finally stopped at 6.40 a.m.
You will notice it states "canceling work" is this because it is done or has issues it cannot resolve?
0 -
Whyndell Grizzard said:
You will notice it states "canceling work" is this because it is done or has issues it cannot resolve?
It also declares that the main index is built and states just two lines up "all background tasks have been completed."
The termination looks completely normal to me. I think all we're seeing here is the program cleaning up after itself.
I await Bradley's response.
Sarcasm is my love language. Obviously I love you. 0 -
Thomas Black said:
The termination looks completely normal to me. I think all we're seeing here is the program cleaning up after itself.
Yes, this log file looks completely normal to me.
There appear to be some issues with the linearity of the progress measurement during this phase (particularly in the last 1%) which may be a problem we can fix. This phase is very disk-intensive though, so if some other program (backup, virus scan, update, etc.) started using the disk heavily at 6am it could cause the indexer to experience a great reduction in throughput and produce this problem; there's not much we can do to predict that (and scale the progress back accordingly).
0 -
Mine appears to be stuck at 99% too. How do I generate a log for you? Will it matter?
0 -
Ray,
Don't panic it can appear hung at 99% (or any %) for awhile before completing it's current task. How long has it actually been at 99%?
As it stands you can't really enable a log on the current activity unless logging is already on. I suggest you just let it run through to the finish.
For the future you might want to enable Logging (http://wiki.logos.com/Diagnostic_Logging) so that you can upload your logs (http://wiki.logos.com/Uploading_Logs) when you encounter a problem.
Thanks.
Sarcasm is my love language. Obviously I love you. 0 -
Thomas Black said:
Don't panic it can appear hung at 99% (or any %) for awhile before completing it's current task. How long has it actually been at 99%?
In all respects it has completed at 99% and it took nearly 1 minute to replace (my) indexes and exit. But we need an indication of the phase to back up the percentage eg all resource indexing was complete at 64%, but others report 74%.
Dave
===Windows 11 & Android 13
0 -
Unfortunately I didn't save my last indexerlog for the big reindex with beta 7, however I recall it sitting at 99% for over an hour on my machine before terminating.Dave Hooton said:In all respects it has completed at 99% and it took nearly 1 minute to replace (my) indexes and exit. But we need an indication of the phase to back up the percentage eg all resource indexing was complete at 64%, but others report 74%.
Sarcasm is my love language. Obviously I love you. 0 -
Thomas Black said:
Unfortunately I didn't save my last indexerlog for the big reindex with beta 7, however I recall it sitting at 99% for over an hour on my machine before terminating.
Mine finally resolved after about 2 hours. 8-)
0 -
Glad to hear it Ray. [y]
Too bad you didn't have a log for us to compare. :-)
Sarcasm is my love language. Obviously I love you. 0 -
Bradley Grainger said:
There appear to be some issues with the linearity of the progress measurement during this phase (particularly in the last 1%) which may be a problem we can fix.
Concur with progress measurement update variance ranging from 15 seconds to over 5 minutes (longest one was 10 minutes 45 seconds going from 4 % to 5 % complete). Rebooted PC - launched Logos 4.2a Beta 7 - rebuild index - let power management turn off screen. Attached zip file has worksheet showing notification messages and durations along with yellow highlighting ones over 2 minutes. Zip file also has log files: Logos4.log shows sync running while indexing being done plus Logos4Indexer.log has indexing along with notification messages. Looks like % complete for Bible Indexing and Final merging need some variance reduction.
Keep Smiling [:)]
0
