2 Replies Latest reply on Feb 27, 2014 10:22 AM by DrewTenenholz

    FMServer 12 Admin Server Process Terminated abnormally

    DrewTenenholz

      Folks --

       

      Having some trouble with a FMS12 server that has generally behaved just fine. In the AM, IWP seems to go down, but the real problem now is that the Admin Server (and thus the Admin Console) will not start.

       

      Error logs are showing that the Admin Server process is trying to restart every five minutes without success.

       

      >2/26/14 1:57:59.527 PM com.filemaker.syslogger[146]: Starting Admin Server process...

      >2/26/14 2:01:45.282 PM com.filemaker.syslogger[146]: Admin Server process is not responding.

      >2/26/14 2:01:45.282 PM com.filemaker.syslogger[146]: Admin Server process will be restarted.

      >2/26/14 2:01:55.930 PM com.filemaker.syslogger[146]: Admin Server could not be stopped at this time. Try again later.

      >2/26/14 2:02:27.837 PM com.filemaker.syslogger[146]: Admin Server process has terminated abnormally.

      >2/26/14 2:02:29.888 PM com.filemaker.syslogger[146]: Starting Admin Server process...

       

       

      FMS 12.0.6, Mac OS X 10.9.2 (yes, the newest security update was applied, but the problem started before then)

       

      Any thoughts on where to look to get more detailed information on why this is happening?

       

       

      Thanks,

      Drew Tenenholz

        • 1. Re: FMServer 12 Admin Server Process Terminated abnormally
          Malcolm

          This is a Tomcat problem. Search Google for Admin Server process has terminated abnormally. You are looking for a support page on the FileMaker web site which includes a shell script that fixes this problem. You could try searching filemaker site but I didn’t find it there until I went to google.

           

          Malcolm

          • 2. Re: FMServer 12 Admin Server Process Terminated abnormally
            DrewTenenholz

            Malcolm --

             

            Thanks for the reply.  I think we've isolated this to a problem with conflicting DNS settings between the System Preferences > Network and OS X Server > DNS Server (which was running locally).

             

            Once the DNS system was able to resolve normally, everything (Admin Console, browser, etc.) seems to work much better.  Funny how being connected to the network properly makes all the difference, even if connection is over localhost.

             

            -- Drew Tenenholz