EVERY time I start up Logos4 it starts indexing for a while, then indexing dies later on.
5481.A12-indexer-fail-on-doc318.zip
Mike,
I had the same issue in both A11 and A12. Check out Tom's reply to me with these three command bar commands related to fixing the index:
http://community.logos.com/forums/p/9941/84414.aspx#84414
I was able to fix my indexing problem with a clean install (i.e. remove the whole program and start over with a fresh install), but I'd recommend giving the three commands a try first.
How do I follow these steps? I can find anywhere in Logos how to Rebuild Index, Merge or Rebuild Bible index.
I'm having the same issues as Mike S. and I have reinstalled and nothing fixes the problem.
Go to the command bar (by the magnifying glass) and type the commands without quotes. Don't hit enter. Wait for the dropdown list to populate and select the appropriate command from the tools section of the drop down menu.
Note that this process will take many hours to complete, and your computer will run REALLY slow.
I looked at your log, and the problem is that you are running out of disk space.
So that's pretty scary, because I have 135GB free space when I start (I left it as the only open app when indexing).
Either it's not reading free disc space correctly, looking for a specific kind of "free", or the indexing processes is using up 135GB temp space.
Sound right?
Thanks, I found it. But it does nothing when I click on it.
Sorry, I took another look and I'll have to retract my statement. I think I was fooled by the CR-LF translation so I didn't see the whole log file. Rebuilding your index should fix this. It's trying to merge with a corrupted index, which will never work.
Matt,
The current Mac Alphas do not provide any indication that the commands are actually doing stuff. (I'm told the Windows version does.) So, you have to let it cook in the background for a bit--even up to 5-10 min, in my experience, before the little blue tray icon will pop up indicating that indexing is happening....
Cf. http://community.logos.com/forums/p/8791/72611.aspx#72611
While Mac Alphas not show indexing information on screen, log files do - including indexing progress status and when complete, elapsed time.
By the way, remember seeing yellow bar above Logos 4 home page in Windows with message about initial library indexing.
Have Fun
Clicking on the indexer icon in the menu bar will give you status and approximate time remaining
Cool, that is an update that I have not noticed. Nice job team! [Y]
Thanks LO
Gosh, gosh, gosh. I've tried using A12 for the first time (given that program is so unusable - sorry for beating the same "I'm so upset and am complaining" drum - BUT I AM!!!!!!!!). I'm experiencing the same problem mentioned here, that is, it keeps 'indexing'. WHY? WHY? Someone said the index file is corrupt? How? I don't even use the program? I still use the other (broken) Mac version.
Hands in the air (and mumbling/grumbling) needing help.
-----
By the way, each time I try and enter "Rebuild" and then choose the "Tools > Rebuild Index", the program crashes.
Thanks in advance.
Wonder what logs show for Indexing ? (other log posts lead to resource identification and corrupt index issue)
Observation: signatures for Tom Philpot and Joe Miller includes links for enabling logging and how to post logs along with associated console messages.
Personally Thankful for Logos development team - Alpha software can be frustrating and rewarding - like Ecclesiastes 3.
Keep Smiling [:)]
Someone said the index file is corrupt? How? I don't even use the program?
I believe the corruption was in code that was building/modifying the index. It happens. My suggestion is to calmly remove your hands from the air onto the keyboard and type rebuild index into the command box. After this process is complete type rebuild bible index. Do not hit enter in either case, but wait for the list of suggestions to appear and select the appropriate command. NOTE: running the rebuild index command at night should reduce the occurrence of sudden outbursts of grumbling due to a slow and unresponsive machine. [:D]
Hope this Helps
Michael Kares
When you find a reproducible crash, the best thing you can do for yourself and us is to submit your logs immediately after the crash (don't restart the app; that'll clear the app logs). If you're not familiar with the log submission process, there are instructions in my signature.
Okay.
The problem, in this case, is that I don't know that there is a crash. Well, in fact, there is no crash. I think I'm done indexing so I restart the app and then it starts over. It completes, no crash, and I think it might be fixed. I restart and it starts indexing all over again.
As for the steps to Rebuild, Merge, Rebuild..., can you provide more instruction. Do you "Rebuild"; wait for it to finish (how will you know?) then "Merge", etc.?
Enter the commands in the order listed in Tom Philpot's post near the top of this thread. Wait for the previous command to finish before executing the next one. When the Logos icon disappears you will know that that particular process is finished. Also, if you have the indexer.log file open while the indexer is running, this will give you more information about what is going on. If you see any errors popping up in the log, leave the indexer running, make a copy of the log file and post it to the forum. Note: you may want to zip the log file before posting it.
When Indexer process running, blue logos icon appears in menu bar. When icon disappears, background stuff done or crash happened, last few lines of indexer.log do tell story.
For example, stuff done:
02/02/2010 20:16:59 | INFO | 3 | LogosIndexerWorker | 0 resources in the Bible index need updating
02/02/2010 20:16:59 | INFO | 3 | LogosIndexerWorker | Setting status to NotRunning
02/02/2010 20:16:59 | INFO | 3 | LogosIndexerWorker | All background tasks have completed; exiting application.
02/02/2010 20:16:59 | INFO | 1 | LogosIndexerWorker | Canceling work.
02/02/2010 20:16:59 | INFO | 1 | LogosIndexerWorker | Shutting down services.
Okay. I checked my index.log. I know this is not the prescribed way to post log but I'd like to see if I can get a quick answer. I've yet execute any of the REBUILD, MERGE, REBUILD...commands for two reasons: 1) each time I start Logos and its starts indexing, I don't have an option to cancel it so I can start rebuilding index and 2) I'm not patient enough to finish the indexing to rebuild it.
So, I restarted and it started indexing. I'm letting it finish (though I'd LOVE to know how to cancel it - when I click on the icon at the top right, I only get "info" and "pause" options). In any event, I check the index log; here is the results (granted, I still have approx 55 min of indexing left):
02/02/2010 20:44:39 | ERROR | 5 | LogosResourceIndexer | No lemma found for '????????'; word number = 'wn.hot/92206:2' in bible+kjv.7.4.11.
02/02/2010 20:45:01 | ERROR | 5 | LogosResourceIndexer | No lemma found for '???'; word number = 'wn.hot/99367:1' in bible+kjv.7.19.25.
02/02/2010 20:48:59 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05d4 0x05dc 0x0307 0x05d0 0x0307 0x05dc 0x0307 0x05d4 0x0307 0x05d0 0x0307
02/02/2010 20:48:59 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05dc 0x0307 0x05d0 0x0307 0x05dc 0x05d4 0x05d0
02/02/2010 20:48:59 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05d0 0x0307 0x05dc 0x05d4 0x05d0
02/02/2010 20:49:00 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05dc 0x05de 0x05e9 0x0307 0x05d0 0x0307 0x05dc 0x0307
02/02/2010 20:49:01 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05d5 0x0307 0x05d0 0x0307 0x05e9 0x0307 0x05d0 0x0307 0x05dc 0x0307 0x05e0 0x0307 0x05da 0x0307
02/02/2010 20:49:01 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05de 0x05d0 0x0307 0x05dc 0x0307 0x05d4 0x0307
02/02/2010 20:49:03 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05d9 0x0307 0x05e9 0x0307 0x05e8 0x0307 0x05d0 0x0307 0x05dc 0x0307
02/02/2010 20:49:05 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05d0 0x0307 0x05dc 0x0307 0x05d4 0x05db 0x05d5 0x05df
02/02/2010 20:49:05 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05d0 0x0307 0x05dc 0x0307 0x05d4 0x0307 0x05db 0x0307 0x05d5 0x0307 0x05df 0x0307
02/02/2010 20:49:09 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05d4 0x0307 0x05d0 0x0307 0x05dc 0x05d9 0x05df
02/02/2010 20:49:10 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05d5 0x05e2 0x0307 0x05d0 0x0307 0x05dc 0x0307
02/02/2010 20:49:10 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05d0 0x0307 0x05dc 0x0307 0x05d0 0x0307
02/02/2010 20:49:11 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05d1 0x0307 0x05e9 0x0307 0x05de 0x0307 0x05d0 0x0307 0x05dc 0x0307 0x05d9 0x0307 0x05d4 0x0307
02/02/2010 20:49:11 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05d3 0x0307 0x05d9 0x0307 0x05e9 0x0307 0x05e8 0x0307 0x05d0 0x0307 0x05dc
02/02/2010 20:49:11 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05d9 0x0307 0x05e9 0x0307 0x05e8 0x0307 0x05d0 0x0307 0x05dc 0x0307
02/02/2010 20:49:11 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05d1 0x05b5 0x0307 0x05d0 0x05b0 0x0307 0x05dc 0x05b8 0x0307 0x05d4 0x0307
02/02/2010 20:49:11 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05d9 0x0307 0x05e9 0x0307 0x05e8 0x0307 0x05d0 0x0307 0x05dc
02/02/2010 20:49:11 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05dc 0x05d0 0x05b5 0x0307 0x05dc 0x05b8 0x05d4 0x0307
02/02/2010 20:49:12 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05d0 0x0307 0x05dc 0x0307 0x05d4 0x0307 0x05df 0x0307
02/02/2010 20:49:12 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05d0 0x0307 0x05dc 0x0307 0x05d4 0x0307 0x05db 0x0307 0x05d5 0x0307 0x05df 0x0307
02/02/2010 20:49:12 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05d0 0x0307 0x05dc 0x0307 0x05d4 0x05b0 0x05db 0x05d5 0x05b9 0x05df
02/02/2010 20:49:12 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05d0 0x0307 0x05dc 0x05b8 0x05d4 0x05b0 0x05db 0x05d5 0x05b9 0x05df
02/02/2010 20:49:12 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05d0 0x05b0 0x0307 0x05dc 0x05b8 0x0307 0x05d4 0x05b2 0x0307 0x05db 0x05d5 0x05b9 0x05df
02/02/2010 20:49:12 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05d0 0x0307 0x05dc 0x05d9 0x05df
02/02/2010 20:49:13 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05d0 0x0307 0x05dc 0x05d4
02/02/2010 20:49:19 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05d9 0x0307 0x05e9 0x0307 0x05e8 0x0307 0x05d0 0x0307 0x05dc 0x0307
02/02/2010 20:49:20 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05d9 0x0307 0x05e9 0x0307 0x05e8 0x0307 0x05d0 0x0307 0x05dc
02/02/2010 20:49:21 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05d0 0x0307 0x05dc 0x0307
02/02/2010 20:49:21 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05d0 0x0307 0x05dc 0x05d4 0x05d0
02/02/2010 20:49:22 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05d0 0x0307 0x05dc 0x0307 0x05b8 0x05d0
02/02/2010 20:49:22 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05d9 0x05e9 0x05c2 0x05e8 0x05d0 0x0307 0x05dc
02/02/2010 20:49:22 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05d9 0x05e9 0x05e8 0x05d0 0x0307 0x05dc 0x0307
02/02/2010 20:49:24 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05d9 0x0307 0x05e9 0x0307 0x05e8 0x0307 0x05d0 0x0307 0x05dc 0x0307
02/02/2010 20:49:24 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05d9 0x05e9 0x0307 0x05e8 0x0307 0x05d0 0x0307 0x05dc
02/02/2010 20:49:25 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05d0 0x0307 0x05dc 0x05d3 0x05ea
02/02/2010 20:49:28 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05d0 0x0307 0x05dc 0x05d9 0x05d9 0x05df
02/02/2010 20:49:28 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05d4 0x05d0 0x0307 0x05dc 0x0307 0x05d9 0x0307 0x05df 0x0307
02/02/2010 20:49:30 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05d9 0x05e9 0x05e8 0x05d0 0x0307 0x05dc 0x0307
02/02/2010 20:49:30 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05d9 0x05e9 0x05de 0x05e2 0x0307 0x05d0 0x0307 0x05dc 0x0307
02/02/2010 20:49:45 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05d9 0x05e9 0x05e8 0x05d0 0x0307 0x05dc 0x0307
02/02/2010 20:50:38 | ERROR | 5 | LogosResourceIndexer | No lemma found for '?????????'; word number = 'wn.hot/227118.1' in bible+kjv.19.30.3.
02/02/2010 20:56:44 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05d0 0x0307 0x05dc 0x0307 0x05d9 0x0307 0x05df 0x0307
02/02/2010 21:01:01 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05d3 0x05d9 0x05e9 0x05e8 0x0307 0x05d0 0x0307 0x05dc 0x0307
02/02/2010 21:01:01 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05d3 0x05d9 0x05e9 0x05e8 0x05d0 0x0307 0x05dc 0x0307
02/02/2010 21:01:02 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05d9 0x05e9 0x05e8 0x05d0 0x0307 0x05dc 0x0307
02/02/2010 21:01:02 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05d3 0x05d9 0x05e9 0x05e8 0x05d0 0x0307 0x05dc 0x0307
02/02/2010 21:01:03 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05d3 0x05d9 0x05e9 0x05e8 0x05d0 0x0307 0x05dc 0x0307
02/02/2010 21:01:03 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05d1 0x05d9 0x05e9 0x05e8 0x05d0 0x0307 0x05dc 0x0307
02/02/2010 21:01:03 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05d9 0x05e9 0x05e8 0x05d0 0x0307 0x05dc 0x0307
02/02/2010 21:01:11 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05d9 0x05e9 0x05e8 0x0307 0x05d0 0x0307 0x05dc 0x0307
02/02/2010 21:01:17 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05dc 0x0307 0x05d9 0x0307 0x05e9 0x05c2 0x0307 0x05e8 0x0307 0x05d0 0x0307 0x05dc 0x0307
02/02/2010 21:01:17 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05d9 0x0307 0x05e9 0x05c2 0x0307 0x05e8 0x0307 0x05d0 0x0307 0x05dc 0x0307
02/02/2010 21:01:29 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05dc 0x0307 0x05d0 0x0307 0x05dc 0x0307 0x05e4 0x0307 0x05d0 0x0307
02/02/2010 21:01:31 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05e9 0x0307 0x05de 0x0307 0x05d5 0x0307 0x05d0 0x0307 0x05dc 0x0307
Above messages look familiar - for grins, choose "Rebuild Indexes" tool => crashed A12 - attached zip file has relevant console messages, logos4.log file, and Apple crash report - console messages show crash about 3 seconds after looking for Indexer.plist file (and Logos4Indexer did not launch):
1881.A12-Rebuild-Crash-Archive.zip
Next Logos 4 application launch did start Logos4Indexer process: blue icon appeared - click - shows estimated time left for indexing
My indexer.log file also has some warnings:
2010-02-02 22:05:08.3927 5 Warn LogosResourceIndexer Ignored 8 invalid references for 'biblio' in LLS:1.0.13 (out of 16 total; 50%).
2010-02-02 22:05:08.3933 5 Warn LogosResourceIndexer Ignored 4 invalid references for 'josw' in LLS:1.0.13 (out of 79 total; 5%).
2010-02-02 22:05:08.3933 5 Warn LogosResourceIndexer Ignored 3 invalid references for 'phil' in LLS:1.0.13 (out of 3 total; 100%).
The problem, in this case, is that I don't know that there is a crash.
You wouldn't know by the status of the indexer icon. It will go away if the indexing completes successfully or if the indexer crashes. The only way to know is to look at the Indexer.log file which is generated, or the Logos4.log, or maybe even the Console Messages.log. The FAQ link in my signature will get you to information on how to find your logs and how to post them in the forum. From there, we can take a look and see how exactly to proceed.
Again, Nice crash report. Looks like a bug that we haven't seen before.
2010-02-02 22:05:08.3927 5 Warn LogosResourceIndexer Ignored 8 invalid references for 'biblio' in LLS:1.0.13 (out of 16 total; 50%). 2010-02-02 22:05:08.3933 5 Warn LogosResourceIndexer Ignored 4 invalid references for 'josw' in LLS:1.0.13 (out of 79 total; 5%). 2010-02-02 22:05:08.3933 5 Warn LogosResourceIndexer Ignored 3 invalid references for 'phil' in LLS:1.0.13 (out of 3 total; 100%)
2010-02-02 22:05:08.3933 5 Warn LogosResourceIndexer Ignored 3 invalid references for 'phil' in LLS:1.0.13 (out of 3 total; 100%)
These warnings are generally for metadata that is tagged in the resource that is invalid. Not fatal, just a warning that some of the "references" that the book contains aren't valid. Windows generates these too (since that's in the shared code).
Indexing all night. The icon was gone this morning. I restarted and the icon did not appear. I looked at the log (though I'm not sure I know what I'm looking for) and notices something about "libronix" not responding. I've attached. Does everything look alright?
0116.Archive.zip
Short Answer: Have Fun with A12
Understand overnight indexing:
02/03/2010 05:02:16 | INFO | 12 | LibraryIndex | Library indexing completed in 05:05:59.2700190.
02/03/2010 05:02:16 | INFO | 12 | LibraryIndex | Main index is built; deleting supplemental index.
02/03/2010 05:02:16 | INFO | 3 | LogosIndexerWorker | (7h 16m 37s) Indexing.
Observation: application restart overwrote Logos.log and Indexer.log files with overnight indexing information - saw a good message in Indexer.log:
02/03/2010 06:55:48 | INFO | 10 | LogosIndexerWorker | All background tasks have completed; exiting application.
Hence, A12 should be ready for use.
Also noticed some error messages in Console Messages.log:
2/2/10 10:56:07 PM [0x0-0x3e1ae17].com.logos.Logos_Bible_Software_4[21015] 02/02/2010 22:56:07 | DEBUG | 16 | MediaResourcesSection | Getting resource images for %GospelOfLuke_Writing
2/2/10 10:56:08 PM [0x0-0x3e1ae17].com.logos.Logos_Bible_Software_4[21015] 02/02/2010 22:56:08 | ERROR | 16 | Libronix.DigitalLibrary.Logos.LogosResource | Unparsed reference: popup.pos=ABBRC|res=LLS:14.0.29|type=jump
2/2/10 10:56:09 PM [0x0-0x3e1ae17].com.logos.Logos_Bible_Software_4[21015] 02/02/2010 22:56:09 | DEBUG | 16 | MediaResourcesSection | Getting resource images for %Peter_Person
2/2/10 10:56:10 PM [0x0-0x3e1ae17].com.logos.Logos_Bible_Software_4[21015] 02/02/2010 22:56:10 | ERROR | 16 | Libronix.DigitalLibrary.Logos.LogosResource | Unparsed reference: popup.pos=a309|res=LLS:14.0.3|type=jump
02/02/2010 20:48:59 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05d0 0x0307 0x05dc 0x05d4 0x05d0 02/02/2010 20:49:00 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05dc 0x05de 0x05e9 0x0307 0x05d0 0x0307 0x05dc 0x0307 02/02/2010 20:49:01 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05d5 0x0307 0x05d0 0x0307 0x05e9 0x0307 0x05d0 0x030
02/02/2010 20:49:01 | ERROR | 4 | DocumentIndexer | Error while normalizing bytes: 0x05d5 0x0307 0x05d0 0x0307 0x05e9 0x0307 0x05d0 0x030
These are places where we have to fall back to another means of normalization. These should really be DEBUG messages.