We've been gradually updating our FMS 12 Servers to FMS 13. All has gone well except one of them (in production) 'crashed' Saturday.
Mac OS X Mavericks (up to date) with FMS Server 13. 'Crash' is in parenthesis because there is no crash log but the database went down and the Admin Console was not accessible (the customer intervened before we could example Activity Monitor and see the processes.
Nothing between normal entries in the FMS log and the reboot (done by the customer). But in the Mac OS X console log are several entries around the time of the 'crash' concerning log entries. The logs being removed are older logs from February when an FMS 12 crash occurred. When FMS 13 was installed it was against a clean install of Mavericks. A backup was not in process.
|2014-03-15 11:00:30.355 AM||SubmitDiagInfo||Removed expired file file:///Users/dvs/Library/Logs/DiagnosticReports/FileMaker%20Pro_2014-02-13-012016_DVS-VetFM-Server.crash|
|2014-03-15 11:00:30.356 AM||SubmitDiagInfo||Removed expired plist file file:///Users/dvs/Library/Logs/DiagnosticReports/.FileMaker%20Pro_2014-02-13-012016_DVS-VetFM-Server.crash.plist|
|2014-03-15 11:00:30.444 AM||SubmitDiagInfo||Removed expired file file:///Users/dvs/Library/Logs/DiagnosticReports/QuickLookUIHelper_2014-02-13-011330_DVS-VetFM-Server.crash|
|2014-03-15 11:00:30.445 AM||SubmitDiagInfo||Removed expired plist file file:///Users/dvs/Library/Logs/DiagnosticReports/.QuickLookUIHelper_2014-02-13-011330_DVS-VetFM-Server.crash.plist|
|2014-03-15 11:00:30.446 AM||SubmitDiagInfo||Removed expired file file:///Users/dvs/Library/Logs/DiagnosticReports/QuickLookUIHelper_2014-02-13-011527_DVS-VetFM-Server.crash|
|2014-03-15 11:00:30.447 AM||SubmitDiagInfo||Removed expired plist file file:///Users/dvs/Library/Logs/DiagnosticReports/.QuickLookUIHelper_2014-02-13-011527_DVS-VetFM-Server.crash.plist|
Basically nothing else reported. Any thoughts out there?