AnsweredAssumed Answered

Random FM Server crash when a scheduled script start executing

Question asked by DanielOuimet on May 7, 2010
Latest reply on May 7, 2010 by TSGal

Summary

Random FM Server crash when a scheduled script start executing

Description of the issue

Hi, We have a daily FM script that executes every night at the same time, and when it tries to execute, it crashes the databases (FM process) randomly (about 1 or 2 times a week).  I know it crashes the second the script is scheduled because I have a small programs that monitors the databases and it tells me the second it crashes.  And I know that the first line of the script is not executed since it does sets a field in the database (which is not set after the crash). FM Advanced Server 10.0v2 on MacOS 10.5.8 with the more recent patches in MarchJava was also updated in March At the end of the message, the log file of the crash. Someone can help me PLEASE!!! Daniel===========================In /Library/Logs/CrashReporter/  I have log files for each crash.  Here is an example:Process:         fmserverd [53681]Path:            /Library/FileMaker Server/Database Server/bin/fmserverdIdentifier:      fmserverdVersion:         ??? (???)Code Type:       X86 (Native)Parent Process:  launchd [1]Date/Time:       2010-05-07 02:10:00.908 -0400OS Version:      Mac OS X 10.5.8 (9L31a)Report Version:  6Anonymous UUID:  04F53FC0-7485-42E4-A227-DCC0B84E0A42Exception Type:  EXC_BAD_ACCESS (SIGBUS)Exception Codes: KERN_PROTECTION_FAILURE at 0x00000000ffff0000Crashed Thread:  39===================And the Thread 39 reads like this:Thread 39 Crashed:0   ???                                 0x28034298 0 + 671302296Thread 39 crashed with X86 Thread State (32-bit):  eax: 0xffff0000  ebx: 0x0000000c  ecx: 0x28000123  edx: 0x284af66b  edi: 0xffff0004  esi: 0x284d677b  ebp: 0x284d6490  esp: 0xffff0004   ss: 0x0000001f  efl: 0x00010287  eip: 0x28034298   cs: 0x00000017   ds: 0x0000001f   es: 0x0000001f   fs: 0x0000001f   gs: 0x00000037  cr2: 0xffff0000Binary Images:    0x1000 -    0x1cfef +fmserverd ??? (???) /Library/FileMaker Server/Database Server/bin/fmserverd   0x39000 -    0x67ff7 +com.filemaker.AdminMgr.framework AdminMgr version 10.0v1 (10.0.1)  /Library/FileMaker Server/Database Server/Frameworks/AdminMgr.framework/Versions/A/AdminMgr   0x80000 -    0x88ffb +com.filemaker.DirServiceMgr.framework DirServiceMgr version 10.0v1 (10.0.1)  /Library/FileMaker Server/Database Server/Frameworks/DirServiceMgr.framework/Versions/A/DirServiceMgr   0x93000 -    0xfbfff +com.filemaker.EngineMgr.framework EngineMgr version 10.0v2 (10.0.2)  /Library/FileMaker Server/Database Server/Frameworks/EngineMgr.framework/Versions/A/EngineMgr  0x139000 -   0x13efe3 +com.filemaker.EventLogMgr.framework EventLogMgr version 10.0v1 (10.0.1)  /Library/FileMaker Server/Database Server/Frameworks/EventLogMgr.framework/Versions/A/EventLogMgr  0x147000 -   0x152fe3 +com.filemaker.EventLogWriter.framework EventLogWriter version 10.0v1 (10.0.1)  /Library/FileMaker Server/Database Server/Frameworks/EventLogWriter.framework/Versions/A/EventLogWriter  0x15e000 -   0x197ffb +com.filemaker.FAL.framework FAL version 10.0v1 (10.0.1) /Library/FileMaker Server/Database Server/Frameworks/FAL.framework/Versions/A/FAL  0x1c4000 -   0x1ccff3 +com.filemaker.StatsLogWriter.framework StatsLogWriter version 10.0v1 (10.0.1)  /Library/FileMaker Server/Database Server/Frameworks/StatsLogWriter.framework/Versions/A/StatsLogWriter  0x362000 -   0x53afd3 +com.filemaker.xalan.framework Xalan version 1.3.0E (1.3.0E) /Library/FileMaker Server/Database Server/Frameworks/Xalan.framework/Versions/A/Xalan etc.  do you need the rest of the log????

Outcomes