I would advise checking permissions and account privileges in macOS. Error 255 is not in the list but surely FM support should know what it is. Maybe contact support or see if TSGal has any info on this one.
Take a look at the event.log in the logs folder within the server installation. Can you parse out what it says about startup failure there?
Are you installing under an alternate user? And lastly, just to clarify one is a master installation and the other is a WebDirect worker installation. Is that correct?
Thanks for the idea. Admin account used for all installation. I could not find Error 255 either.
FMS logs show nothing until I start FMS from the command line.
Yes this is a single master with a single worker.
Thanks for the ideas guys.
Installed the FMS 184.108.40.206 update released in the last couple of days. FMS now started once on its own.
Working on why.
So far I can only get FMS to auto-start properly when the worker machine is not available.
So it works properly when the worker is not available but does not when the workee is available? Sounds like a bug. I'll have some testing effort put into reproducing this. If we can't get it reproduced, I'll have support work with you to replicate your environment. Once we get to where we can reproduce from a scratch machine Isolating the bug shouldn't be an issue.
Due to our company size and lack of spare hardware I run tests during down time on separate startup drives in our FileMaker (FMS master) and Web (FMS worker) servers.
Yes - the FMS16 master seems to come up fully when the FMS16 worker machine is not available. Bringing up the worker seems fine as long as the master is running already. Rebooting both simultaneously or just the master with the worker already running, leads to the master not starting FMS. I cannot be sure on the worker's ability to start properly because I have not looked at it closely since I can't really do anything with it until I know I have the master working as expected.