Indexer Crash

The indexer has crashed again (blue icon goes with no warning or reason).

Looking at the logs, it seems to be when indexing LLS:6.60.19 ... which is a resource with a record, but in a beta, in another OS, and 18 months ago.

The log seems to indicate a 'mono crash' is also involved ...

I will delete the resource and hopefully it will re-download and the indexing will start again.

The issue is aggravated in that the indexer is so slow. It took 3 hours 20 to get to the crash, having done 822 resources of 6,2649. I am pretty sure that the window indexer would have been almost done by now ... on the same computer and running through a windows emulator (Parallels)! To get this stellar performance It took my i7 MBP with 8Gb of RAM starting at 2 in the morning ... there were no other tasks that I was asking it to do at the same time.

6153.Logging.zip

Find more posts tagged with

Comments

Martin Folley

I will delete the resource and hopefully it will re-download and the indexing will start again.

No ..iI will not ... I cannot find it!

Maybe I am misreading the log [:$] in my irritation:

06/10/2012 05:21:11 | INFO | 7 | LibraryIndex | (41.70s) Indexing LLS:6.60.17

06/10/2012 05:21:11 | INFO | 7 | LibraryIndex | (Timed) Indexing LLS:6.60.19

Stacktrace:

at (wrapper managed-to-native) Libronix.DigitalLibrary.Logos.CustomNativeMethods.TitleLoader_CloneWithNullDTO (Libronix.DigitalLibrary.Logos.SafeTitleLoaderHandle,Libronix.DigitalLibrary.Logos.SafeISinaiImageLoaderHandle,Libronix.DigitalLibrary.Logos.TitleLoadHint) <0xffffffff>

at Libronix.DigitalLibrary.Logos.LogosResource.IndexContent (Libronix.SearchEngine.IIndexer,Libronix.DigitalLibrary.ResourceManager,Libronix.DigitalLibrary.ReverseInterlinearManager,Libronix.DigitalLibrary.LibraryCatalog,Libronix.Utility.Threading.IWorkState) <0x00081>

at Libronix.DigitalLibrary.LibraryIndex.IndexNextResource (Libronix.DigitalLibrary.LibraryIndex/ILibraryIndexWorkState,Libronix.SearchEngine.Indexer) <0x003ac>

at Libronix.DigitalLibrary.LibraryIndex.IndexResources (Libronix.DigitalLibrary.LibraryIndex/ILibraryIndexWorkState,Libronix.SearchEngine.Indexer) <0x00019>

at Libronix.DigitalLibrary.LibraryIndex.DoBuildIndex (Libronix.DigitalLibrary.LibraryIndex/ILibraryIndexWorkState,int,string,int) <0x00579>

at Libronix.DigitalLibrary.LibraryIndex.BuildIndex (Libronix.DigitalLibrary.LibraryIndex/LibraryIndexWorkState,string) <0x0003d>

at Libronix.DigitalLibrary.LibraryIndex.IndexResources (Libronix.Utility.Threading.IPausableWorkState,Libronix.DigitalLibrary.LibraryIndex/LibraryIndexWorkState) <0x007d7>

at Libronix.Utility.Threading.WorkStateThreadOwner`1.ThreadProc (object) <0x00188>

at System.Threading.Thread.StartUnsafe () <0x0007d>

at (wrapper runtime-invoke) object.runtime_invoke_void__this__ (object,intptr,intptr,intptr) <0xffffffff>

Native stacktrace:

0 libmono-2.0.1.dylib 0x04de1d1d mono_handle_native_sigsegv + 376

1 libmono-2.0.1.dylib 0x04d1d398 mono_sigsegv_signal_handler + 322

2 libsystem_c.dylib 0x93fea59b _sigtramp + 43

3 ??? 0xffffffff 0x0 + 4294967295

4 libLDLS3Core.dylib 0x04310b4a _ZN8CryptoPP22AdditiveCipherTemplateINS_20AbstractPolicyHolderINS_28AdditiveCipherAbstractPolicyENS_15SymmetricCipherEEEE11ProcessDataEPhPKhm + 372

5 libLDLS3Core.dylib 0x042b710c _ZN7LbxUtil19EncryptedStreamImpl4ReadEPvjPj + 548

6 libLDLS3Core.dylib 0x042a68ec _ZN7ComUtil19SubstreamStreamImpl4ReadEPvjPj + 152

7 libLDLS3.dylib 0x04982958 _ZN12_GLOBAL__N_118CreateMemoryStreamEP7IStreamm + 112

8 libLDLS3.dylib 0x04982e8f _ZN8SinaiLib11TitleLoader14CreateCTitleAtEPKwRN7ComUtil13CInterfacePtrI7IStreamEES7_NS_13TitleLoadHintE + 241

9 libLDLS3.dylib 0x04985aa5 _ZN8SinaiLib11TitleLoader24InitializeLogos4ResourceEPKwP7IStreamNS_13TitleLoadHintE + 707

10 libLDLS3.dylib 0x0498639e _ZN8SinaiLib11TitleLoader9LoadTitleEPKwP7IStreamNS_13TitleLoadHintE + 370

11 libLDLS3.dylib 0x04986e98 _ZN8SinaiLib11TitleLoader5CloneEPKS0_P17ISinaiImageLoaderP29ISinaiDataTypeOptionsCallbackNS_13TitleLoadHintE + 2046

12 libLDLS3.dylib 0x0496f072 TitleLoader_CloneWithNullDTO + 39

13 ??? 0x18505788 0x0 + 407918472

14 ??? 0x1850537a 0x0 + 407917434

15 ??? 0x0f4a81e5 0x0 + 256541157

16 ??? 0x0f4a7e22 0x0 + 256540194

17 ??? 0x0f4a5e1a 0x0 + 256531994

18 ??? 0x0f4a5316 0x0 + 256529174

19 ??? 0x0f4a41f0 0x0 + 256524784

20 ??? 0x0aaab551 0x0 + 178959697

21 ??? 0x0aaab3a6 0x0 + 178959270

22 ??? 0x054f40af 0x0 + 89079983

23 libmono-2.0.1.dylib 0x04d1d153 mono_jit_runtime_invoke + 1332

24 libmono-2.0.1.dylib 0x04ef93d8 mono_runtime_invoke + 137

25 libmono-2.0.1.dylib 0x04efab9d mono_runtime_delegate_invoke + 111

26 libmono-2.0.1.dylib 0x04f37099 start_wrapper_internal + 692

27 libmono-2.0.1.dylib 0x04f370e7 start_wrapper + 17

28 libmono-2.0.1.dylib 0x04f765a8 thread_start_routine + 191

29 libmono-2.0.1.dylib 0x04fa9fcb GC_start_routine + 107

30 libsystem_c.dylib 0x93f92ed9 _pthread_start + 335

31 libsystem_c.dylib 0x93f966de thread_start + 34

Debug info from gdb:

=================================================================

Got a SIGSEGV while executing native code. This usually indicates

a fatal error in the mono runtime or one of the native libraries

used by your application.

=================================================================

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/374541#Comment_374541

Maybe I am misreading the log in my irritation:

Looking in Indexer.log file, noticed four resources were being indexed (in threads 7, 8, 9, and 10):

LLS:46.10.22 is resource file MWDICT11.logos4 - Merriam-Webster's Collegiate Dictionary (11th edition)

LLS:1.0.30 is the NKJV Bible, which has three resource files: NKJV.logos4, NKJVNT.lbsrvi, and KNJVOT.lbsrvi

LLS 6.60.18 is resource file NPNF18.logos4 - Nicene and Post-Nicene Fathers Second Series, Volume IV

LLS 6.60.19 is resource file NPNF19.logos4 - Nicene and Post-Nicene Fathers Second Series, Volume V

Looking in all_messages.log file, noticed couple lines:

10/06/2012 05:21:24.000 kernel disk0s2: I/O error.
10/06/2012 05:21:43.806 ReportCrash Saved crash report for Logos4Indexer[981] version ??? (61452.8.160) to /Users/Martin/Library/Logs/DiagnosticReports/Logos4Indexer_2012-06-10-052143_Martins-MacBook-Pro.crash

Likewise noticed Logos4.Error.log has a strange error when writing to a tmp file yesterday.

Wonder if Mac is hot to touch ? A physically hot drive can cause I/O error(s). One idea is booting to OS X Lion recovery, then use disk utility to check hard drive; not know if any repair(s) are needed. After using disk utility to verify your bootable partition, could restart Mac, which should restart indexing. Anticipating ~10 hours for library indexing that includes lots of disk activity so may want to consider a laptop cooler.

If indexer crash repeats with same resources, one option is moving resource files somewhere else, then try indexing again. The Indexer.log file would have errors about not finding files to index.

Since using stable Logos 4.5b SR-3, one option is contacting Logos Tech Support => http://www.logos.com/about/contact (email or call); personally not know if Logos would like a copy of the diagnostic crash report.

By the way, noticed Logging folder has nlog.config files, which are no longer being used, a remnant of Logos 4 Mac alpha pre-releases.

Keep Smiling [:)]

Hunter Clagett

https://community.logos.com/discussion/comment/374653#Comment_374653

I'd recommend you give us a call to sort out this issue. Would it be possible for you to give
us a call at 1(800)875-6467 to troubleshoot the problem?

If you are from outside North
America and cannot call, we may be able to arrange a Skype call. Just send me
your phone number (land lines only, please) and the best time
to call, including your time-zone.

Thanks,

Martin Folley

https://community.logos.com/discussion/comment/375033#Comment_375033

Thanks Hunter

I have moved back to L4 under Parallels for the moment (re-organising notes / highlighting / clippings etc. where l4Mac does no cut it).

I notice the new release of L4Mac which mentions 30% faster indexer ... so thinking that may be a different code updated and tried again ... still crashed though :-(

Logs attached:

1070.Logging.zip

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/377763#Comment_377763

I notice the new release of L4Mac which mentions 30% faster indexer ...

Logos 4.5c Release Candidate 1 has only been released to the Beta channel.

Indexer.log file shows Logos 4.5b SR-3 is encountering a number of malformed database files while indexing resources (attempting to add to lexicon cache), which is later followed by a crash while processing reverse interlinear.

Concur with suggestion to follow-up with Logos.

If want to try Logos 4.5c Release Candidate on Mac, one option is manually upgrading application; wiki has Update Error that has Current Beta release download link. Also, could use beta download link in thread => 4.5c Release Candidate 1 (4.53.0.2254) available

Apologies: Logos 4.5c is up to 30 % faster for indexing using Windows; currently running rebuild index on Mac OS X 10.6.8 to see if faster than 4.5c Beta 4 (had noticed CPU usage was bit less intense for indexing using Logos 4.5c Beta 4 on Mac OS X).

Keep Smiling [:)]