The fastest (but least gratifying) solution is going to be:
- do a complete uninstall of FMS
- manually removing any stray folders
- repair permissions
- reinstall FMS
So each time OSX updates I need to reinstall filemaker server? seems rather poor delpyment on Apple and Apple Filemaker.
So i have to undo evertything, reinstall everything and redeply my databases? WOW.....
I agree with Wim on this, having had to do it a couple times recently myself.
Alternatlively, don't do server upgrades unless critical. No need to poke the beehive with a stick unless you're prepared to get stung.
Since FMS is hijacking the OS it makes sense that when an OS update happens the OS "repairs" itself - hosing FMS.
Sometimes, a re-deploy will fix things but as Wim said - uninstall and reinstall.
One would think with the link between Apple and FileMaker it would seem appropriate that the two would talk when doing an update.
this was a reason I trashed windows as their updates broke things, and not updating leaves you vulnerable.
I am really disapointed in Apple/FileMaker now.
Is there a good, better, best way to do this uninstall, reinstall?
This is interesting, because I've executed two OS patches on my home development box and haven't had this problem. Can you post a bit more information about your exact setup? Do you shut down Server before executing the patch?
OSX 10.9.4 was the update, installed it yesterday the 16th.
running on Mac Mini's as servers. Filemaker 13 server.
the auto update did the update and rebooting.
shouldn't have been any different than any other update, but it got me.
You don't have to reinstall FMS.
Basically what is going on is that the OSX instance of Apache is running before FMS's instance. What you have to do is stop apache and then start FMS's Apache.
to do so, use this two commands in terminal:
- sudo apachectl stop
- sudo /Library/Filemaker\ Server/HTTPServer/bin/httpdctl graceful
After the second command you should be working normally.
Tony, do you also have the OS X Server app installed as well? You made some reference to seeing those pages, and I wonder if that's where the conflict is, as opposed to OS X without the server components installed.
In my case this did not do the job, but it is a good thing to try first.
So each time OSX updates I need to reinstall filemaker server?
No, not what I said.
99 times out of 100 these OS updates go without any problem. But if it does give you trouble and you spend say more than hour troubleshooting it, it is going to be much faster to do the reinstall.
yes i do, but up till now it wasn't causing any issues, just this last update. kinka scary actually
yes understood, problem is this is the one time out of 100, and not at a good time because i just had a windows server crash as well, so now i have double issues. just not having a good week with servers. couldn't have happend at a worse time, and the only reason i did this update was to get that stupid osx message off the server lol. just very upset with the fact that the same vendor (Apple in this case) can crash their own applications with an update, they are better than that.