AnsweredAssumed Answered

Filemaker Server Settings destroyed after complete system memory exhaustion

Question asked by VincentL on Jan 21, 2015
Latest reply on May 12, 2015 by TSGal


Filemaker Server Settings destroyed after complete system memory exhaustion


FileMaker Server



Operating system version

Mac OS X 10.9.5

Description of the issue

When the system memory is exhausted, to the point the system HD has 0 Kb left on it. After restart, you'll loose all schedules / programs and additional database folders.
You have to reload the settings (if you ave them before) and the script/schedule will get back.
Unfortunately the additional folder have to be restored by hand, as well as plugin settings.

This happened to me twice. And the first time, even the fmsadmin password was lost.

Of course the responsible of the memory exhausting is filemaker itself : it's fmased process,
maybe as depicted here

Howewer, in my today reports, there was no server side script connected anymore (there was 30 minute before), but contrary to the "memory leaks " report, where the server side script wasn't running anymore, in today's situation fmsadmin and web UAC, told no clients were connected to the database. But strangely, trying to close all file remained stuck in "closing..." state even though no connected clients appeared anywhere.

After all but some files were closed, I tried to stop fms, but even though fmseverd was not running anymoe (not showing in a man activity monitor), fmsased was still running and goblin ram.

Steps to reproduce the problem

Exhaust computer memory, perhaps with a rogue recursive server side script.
When memory is exhausted, try to disconnect all client, and to close all files. Then stop the server, if you can.
Resatrt or force restart

Maybe it also happens if the cause of memory exhaustion is not filemaker related.

Expected result

FMS Setting untouched

Actual result

Script schedules, backup schedules, additional folders, plugins settings and sometimes even fmsadmin credential are lost.

Exact text of any error message(s) that appear

No error message