6 Replies Latest reply on Mar 25, 2015 2:01 PM by TSGal

    Filemaker Server Crash



      Filemaker Server Crash


      FileMaker Server



      Operating system version

      Mac OS 10.7.5

      Description of the issue

      My server keeps crashing with the following result:

      I would love to understand what this means and how to fix it.  It is causing indexing issues such that I have to recover my database to fix the problem. 

      Date/Time:       2015-03-01 13:37:45.296 -0500
      OS Version:      Mac OS X Server 10.7.5 (11G63)
      Report Version:  9

      Interval Since Last Report:          15142 sec
      Crashes Since Last Report:           2
      Per-App Crashes Since Last Report:   1
      Anonymous UUID:                      67883811-9A76-4BB6-B134-965223F5706D

      Crashed Thread:  0  Dispatch queue: com.apple.main-thread

      Exception Type:  EXC_CRASH (SIGABRT)
      Exception Codes: 0x0000000000000000, 0x0000000000000000

      Application Specific Information:
      objc[452]: garbage collection is OFF
      *** Terminating app due to uncaught exception 'NSArchiverArchiveInconsistency', reason: '*** End of archive encountered prematurely at 551741'
      *** First throw call stack:
           0   CoreFoundation                      0x00007fff8c5aff56 __exceptionPreprocess + 198
           1   libobjc.A.dylib                     0x00007fff8b7c8d5e objc_exception_throw + 43
           2   CoreFoundation                      0x00007fff8c5afd8a +[NSException raise:format:arguments:] + 106
           3   CoreFoundation                      0x00007fff8c5afd14 +[NSException raise:format:] + 116
           4   Foundation                          0x00007fff91ee7217 -[NSUnarchiver decodeBytesWithReturnedLength:] + 416
           5   Foundation                          0x00007fff91ecbb56 -[NSString initWithCoder:] + 93
           6   Foundation                          0x00007fff91ea2d75 _decodeObject_old + 331
           7   Foundation                          0x00007fff91ea3bbe _decodeValueOfObjCType + 1328
           8   Foundation                          0x00007fff91ea3643 -[NSUnarchiver decodeValueOfObjCType:at:] + 96
           9   Foundation                          0x00007fff91ea4ac8 -[NSDictionary(NSDictionary) initWithCoder:] + 381
           10  Foundation                          0x00007fff91ea2d75 _decodeObject_old + 331
           11  Foundation                          0x00007fff91ea3bbe _decodeValueOfObjCType + 1328
           12  Foundation                          0x00007fff91ea3643 -[NSUnarchiver decodeValueOfObjCType:at:] + 96
           13  Foundation                          0x00007fff91ea4adf -[NSDictionary(NSDictionary) initWithCoder:] + 404
           14  Foundation                          0x00007fff91ea2d75 _decodeObject_old + 331
           15  Foundation                          0x00007fff91ea211c +[NSUnarchiver unarchiveObjectWithData:] + 65
           16  Foundation                          0x00007fff91f26c40 +[NSUnarchiver unarchiveObjectWithFile:] + 58
           17  hiutil                              0x00000001033da038 hiutil + 8248
           18  hiutil                              0x00000001033dab31 hiutil + 11057
           19  hiutil                              0x00000001033d9c7e hiutil + 7294
           20  hiutil                              0x00000001033d9570 hiutil + 5488
           21  ???                                 0x000000000000000b 0x0 + 11

      terminate called throwing an exception
      abort() called

        • 1. Re: Filemaker Server Crash

          I don't see anything in the crash report that indicates FMS has crashed.

          • 2. Re: Filemaker Server Crash

            I am going by the diagnostic report notation (hiutil_ DATE_FreedomCar-filemaker-server.crash) in Console.  The fact is that I have a periodic (about every 7 days) "crash" of this type and indexing issues (or an indexing issue that causes a "crash").  I am trying to figure out how to solve whatever bug is causing it as it drives me crazy (causing me to pull my database offline and recover it to a clone).  There is is also a crash on the same day but at a different time (I don't know if these two things are related):

            Process:         fmserverd [212]
            Path:            /Library/FileMaker Server/*/fmserverd
            Identifier:      fmserverd
            Version:         ??? (???)
            Code Type:       X86-64 (Native)
            Parent Process:  launchd [1]

            Date/Time:       2015-03-01 12:42:41.573 -0500
            OS Version:      Mac OS X Server 10.7.5 (11G63)
            Report Version:  9

            Anonymous UUID:                      67883811-9A76-4BB6-B134-965223F5706D

            Crashed Thread:  18

            Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
            Exception Codes: KERN_INVALID_ADDRESS at 0x00000000000107e8

            VM Regions Near 0x107e8:
                __TEXT                 0000000100000000-000000010001d000 [  116K] r-x/rwx SM=COW  /Library/FileMaker Server/*

            Application Specific Information:
            objc[212]: garbage collection is OFF

            Thread 18 Crashed:
            0   com.filemaker.dbengine.framework    0x00000001003ea910 Draco::EngineEventSender::Send(int, unsigned int) + 32
            1   com.filemaker.dbengine.framework    0x000000010077d6f4 Draco::RCConnection::Send(unsigned int, unsigned char*&, unsigned int&, bool) + 3492
            2   com.filemaker.dbengine.framework    0x000000010077db4a Draco::RCNetworkStack::SendingThread::Main() + 74
            3   com.filemaker.support.framework    0x00000001016fb034 Draco::RepThread::RunThread() + 52
            4   com.filemaker.support.framework    0x00000001016fa7f9 Draco::Thread::ThreadUnixProc(void*) + 57
            5   libsystem_c.dylib                 0x00007fff863388bf _pthread_start + 335
            6   libsystem_c.dylib                 0x00007fff8633bb75 thread_start + 13



            • 3. Re: Filemaker Server Crash


              Thank you for your posts.

              The first post is system related.  Doing a web search for "NSArchiverArchiveInconsistency" has not been helpful.

              The second post is definitely from FileMaker Server, and it appears to be network related.  I'm not 100% certain, so I have forwarded your second crash report to Development and Testing for review.  When I receive any feedback, I will let you know.

              FileMaker, Inc.

              • 4. Re: Filemaker Server Crash

                Thank you.  I too spent time trying to find out more about the "NSArchiverArchiveInconsistency" but to no avail.  I guess it makes me feel slightly better that it's a system issue and not a FM issue.


                • 5. Re: Filemaker Server Crash


                  Testing would like the entire crash log, as it looks like the server is being stopped when the crash occurs, but they cannot determine with certainty.  Also, it would be helpful to include the Event.log.

                  Check your Inbox at the top of this page for instructions where to send the files.

                  FileMaker, Inc.

                  • 6. Re: Filemaker Server Crash


                    The full crash log shows that the Server is far into shutting down.  Any information being sent to FileMaker Server during this time is safe since the databases have been closed long before the crash.  There is no information why the server was shutting down.

                    Development does not understand how the indexing of the records could have been affected during this time along with the reason for recovery.  Is there a previous crash log or another crash log available?  If so, please send the file(s) to the same address provided in the earlier private message.

                    FileMaker, Inc.