AnsweredAssumed Answered

Server Admin Console freezes then crashes

Question asked by kdoronzio on Jul 5, 2010
Latest reply on Jul 31, 2010 by hschlossberg

Summary

Server Admin Console freezes then crashes

Product

FileMaker Server

Version

FMSA 11

Operating system version

Windows 2003 Server R2

Description of the issue

This issue was reported on the old forums, but I can't find it here. We've had this same problem on FMS10, and was hoping it would go away on FMS11. But it hasn't.

The symptoms are:
After FileMaker Server is running for about 3 weeks, the admin console stops updating its information, and shows non-current information. It seems to occur during a scheduled backup, as one of the schedules displays "running".

This screen remains in this "altered" state for about a week, then a message comes up that the admin console can no longer be accessed.

During this time, the Command Line Interface works OK, and shows current information. After the admin console can no longer be accessed, the CLI no longer works either.

Also during the time the console appears frozen, backups continue to work properly, but email notifications are not sent out. After the week is up, backups no longer occur.

Clients can continue accessing files throughout. Even after the console is completely inaccessible.

When we were using FMS10, we were able to run the "catalina" restart script, which got the console running again for the week, but still crashed after the week was up. In FMS11, we had the same experience with the CLI "restart adminserver" command. It got the console back when it appeared frozen, the server still crashed after the week was up.

At that point, rebooting the entire server seems to be the only sure-fire way to get back control of the server.

We have also checked for corruption in our databases using both FileMaker's recover command, consistency check, and FMDiff. There were small problems that FMDiff reported, that FM Recover did not. Recovering the file fixed the errors in FMDiff, but did not seem to change the problem with FileMaker Server.

Configuration information

FM Server Advanced  11.0.1.99
Windows Server 2003 R2 SP2
Java 1.6.0_20
IBM Xseries_3400
Intel Xeon 1.6GHz (x2)
2 GB RAM

Workaround

We reboot the machine at night. We can check that no clients are logged on by first running a "get(usercount)" on the main files.

Outcomes