AnsweredAssumed Answered

MacMini with FMS 12 or FMS13 drops client connections

Question asked by StephenWonfor_2 on Mar 24, 2014
Latest reply on May 29, 2014 by TSGal

Summary

MacMini with FMS 12 or FMS13 drops client connections

Product

FileMaker Server

Version

FMS 12 and FMS 13

Operating system version

10.9.2

Description of the issue

Original Server 27” iMac.  3.07 GHz Cpu 256 GB SSD.
OSX 10.7.5.  FMServer 11

…having some issue with admin console, downtime window very small, so we decided to replace with a MacMini and upgrade to FMP13.

Mac Mini  C07M608VDY3J
Dual 256 GB SSD. 8 GB Ram.

OSX 10.9.1  FMServer 13.0v1

Solution is a grandfathered 40 db solution - 5 main files.
Solution size is 800 MB plus a 12 GB images file.

Installed solution on new MacMini and deployed.

15 users - 5 local and 10 remote.
All Macs running 10.8.5 or 10.9.1.  All have at least 4 GB ram.  All are connected via Ethernet.  All clients - Sys Prefs = No Computer Sleep, No Hard Disk Sleep.

Users started reporting getting disconnected from the FMServer - both local and remote.  Intervals from 60 to 480 minutes.

So…

Wiped the iMac.
Installed 10.9.2 with FMS13.
No client issues at all.

Took MacMini home.

Wiped SSD#1 and reinstalled 10.9.2 and FMS13.0v1.  Sys Prefs = No Computer Sleep, No Hard Disk Sleep.
Hooked up 2 laptops - MacBookPro 15” 10.8.5 and MacBook 10.7.5.  Both have FMP 12 and FMP 13 available. All clients - Sys Prefs = No Computer Sleep, No Hard Disk Sleep.
At times I also connected my main MacBookPro 17” running 10.9.2.  Sys Prefs = No Computer Sleep, No Hard Disk Sleep.
All on Wifi.

Same results - clients disconnected by FMServer.

Wiped SSD#1 and reinstalled 10.9.2 and FMS13.0v1. Again.

Same results - clients disconnected by FMServer.

So, a new approach.

Wiped SSD#2 and reinstalled 10.9.2 and FMS12.0v6.

Same results - clients disconnected by FMServer.

2014-03-21 09:10:47     Server Events     Warning     Client "Stephen (Raine) [10.0.1.14]" no longer responding; connection closed. (51)     10.9.2FMS12 - SSD#2
2014-03-21 14:56:47     Server Events     Warning     Client "Stephen Wonfor (QuadBook) [10.0.1.10]" no longer responding; connection closed. (51)     10.9.2FMS12 - SSD#2
2014-03-22 05:54:07     Server Events     Warning     Client "Stephen Wonfor (QuadBook) [10.0.1.10]" no longer responding; connection closed. (51)     10.9.2FMS12 - SSD#2
2014-03-22 05:55:44     Server Events     Warning     Client "Stephen (Raine) [10.0.1.14]" no longer responding; connection closed. (51)     10.9.2FMS12 - SSD#2
2014-03-22 10:10:06     Server Events     Warning     Client "Stephen Wonfor (QuadBook) [10.0.1.10]" no longer responding; connection closed. (51)     10.9.2FMS12 - SSD#2
2014-03-22 13:25:54     Server Events     Warning     Client "Stephen (Raine) [10.0.1.14]" no longer responding; connection closed. (51)     10.9.2FMS12 - SSD#2
2014-03-22 17:06:39     Server Events     Warning     Client "Stephen (Raine) [10.0.1.14]" no longer responding; connection closed. (51)     10.9.2FMS12 - SSD#2
2014-03-22 17:09:24     Server Events     Warning     Client "Stephen Wonfor (QuadBook) [10.0.1.10]" no longer responding; connection closed. (51)     10.9.2FMS12 - SSD#2
2014-03-22 17:33:41     Server Events     Warning     Client "Stephen (Raine) [10.0.1.14]" no longer responding; connection closed. (51)     10.9.2FMS12 - SSD#2
2014-03-22 17:35:36     Server Events     Warning     Client "Stephen (Trilobyte) [10.0.1.19]” no longer responding; connection closed. (51)     10.9.2FMS12 - SSD#2
2014-03-22 18:18:23     Server Events     Warning     Client "Stephen Wonfor (QuadBook) [10.0.1.10]" no longer responding; connection closed. (51)     10.9.2FMS12 - SSD#2
2014-03-22 18:20:10     Server Events     Warning     Client "Stephen (Raine) [10.0.1.14]" no longer responding; connection closed. (51)     10.9.2FMS12 - SSD#2
2014-03-22 19:05:07     Server Events     Warning     Client "Stephen Wonfor (QuadBook) [10.0.1.10]" no longer responding; connection closed. (51)     10.9.2FMS12 - SSD#2
2014-03-22 19:40:03     Server Events     Warning     Client "Stephen (Raine) [10.0.1.14]" no longer responding; connection closed. (51)     10.9.2FMS12 - SSD#2
2014-03-20 18:01:03.212 -0600          Warning     Client "Stephen (Raine) [10.0.1.14]" no longer responding; connection closed. (51)     10.9.2FMS13 - SSD#1
2014-03-20 18:11:28.378 -0600          Warning     Client "Stephen Wonfor (QuadBook) [10.0.1.10]" no longer responding; connection closed. (51)     10.9.2FMS13 - SSD#1
2014-03-20 18:29:13.327 -0600          Warning     Client "Stephen (Raine) [10.0.1.14]" no longer responding; connection closed. (51)     10.9.2FMS13 - SSD#1
2014-03-20 19:02:13.237 -0600          Warning     Client "Stephen (Trilobyte) [10.0.1.19]” no longer responding; connection closed. (51)     10.9.2FMS13 - SSD#1
2014-03-21 00:02:06.440 -0600          Warning     Client "Stephen Wonfor (QuadBook) [10.0.1.10]" no longer responding; connection closed. (51)     10.9.2FMS13 - SSD#1
2014-03-21 00:02:07.444 -0600          Warning     Client "Stephen (Raine) [10.0.1.14]" no longer responding; connection closed. (51)     10.9.2FMS13 - SSD#1

Another approach, setup a small network and use ethernet connections for all machines.  Same results.

The (10) indicates that the 125 second timeout elapsed as described above. The (51) indicates that the TCP connection failed when Server tried to send something to the client. 

To summarize:

3 deploys of FMS13 in OSX 10.9.2 on SSD#1 show FMServer connection drops.
1 deploy of FMS12 in OSX 10.9.2 on SSD#2 show FMServer connection drops.

Steps to reproduce the problem

connect clients to server

Expected result

they stay connected

Actual result

FMServer disconnects clients

Exact text of any error message(s) that appear

2014-03-20 18:11:28.378 -0600          Warning     Client "Stephen Wonfor (QuadBook) [10.0.1.10]" no longer responding; connection closed. (51

Workaround

use a different computer

Outcomes