AnsweredAssumed Answered

Stopping FMS 17 Databaseserver from GUI fails and results in Memory Dump

Question asked by Jbsherry on Jun 27, 2018
Latest reply on Jul 11, 2018 by TSGal

Product and version: FMS 17v1

OS and version: Windows 2012R2 Standard

Browser and version: Chrome Version 67.0.3396.99 (Official Build) (64-bit)

Hardware: AWS T2Medium, SSD drives

Description: Clicking on Stop Database Server under Coniguration/General Settings appeared to fail to stop the DB server. UI did not update. Clicked a few times. No change. Switched to CLI and attempted to stop DB Server. CLI thought it was already stopped. Restarted the AdminServer to see if UI would sync up with what CLI was showing. Logged into UI, which reported 0 DBs found, when there are 7. General Settings still showed DB Server as running. Restarted OS. Memory Dump found in Logs folder.

How to replicate: Try stopping the DB server from the UI. This is presumably an intermittent issue, but I'm posting because this is the 2nd FMS17 server to dump. Both are installed on a standard AWS setup that I've run at least 20 servers on. Both dumped within 2 weeks of install.

Workaround (if any): Don't use GUI?

Outcomes