I Just noticed a few days ago the Vebrum Indexer crashed 4 times. I don't have regular logs any more as I restarted, but at least is the error log for the indexer...
5811.VerbumError.log
We need the VebumIndexerError.log
Yeah, that got overwritten I guess on a restart or new index. I'll keep an eye out for new crashes .
Actually, hold the line! It crashed again last night, 7:35 PM Feb 9 local time according to the Mac console:
Here are all the logs, hope it helps!
0842.Archive.zip
Sorry for the issue, do you have any other details on what you were doing in the application before the crash? We can use that information to help try and replicate the issue, but like stated above, the logs will point to something similar as well.
I probably had a pre-pub that downloaded and it was indexing - Usually leave it alone and do something else when that happens. I tried doing a rebuild index today, first wipinng out all the index files so it did a complete rebuild, but that finished fine with no issues.
A VerbumIndexerCrash.log would exist if a 'normal' crash had occurred. The Console log makes interesting reading (for the Developers) because the Verbum Indexer apparently restarted 2 seconds later (19:35:14) and terminated OK without indexing any books. The log created from the crash at 19:35:12 would have been overwritten. All this occurred whilst Verbum (started at 19:35:03) was running, and it only started the Indexer once at 19:35:09!!
The Console crash is a mystery to me.
