New answers tagged server.app
Just removing the Server.app (3.2.2) for 10.9 Mavericks isn't enough. You also have to unload several launch daemons. By comparing all "System LaunchDaemons" in a basic Server.app install and an LDAP/VPN environment in two different VMs I assume that the following system launch daemons have to be unloaded permanently: org.openldap.slapd ...
"Network Accounts unavailable" is an indication that the device is unable to communicate with Directory Services (Open Directory). You need to make sure that you are on the same subnet as the server (the subnet that was used when the Open Directory was created as this seems to be a MacBook and mobile). You also need to make sure DNS is setup correctly ...
I was just going to comment on the accepted answer (but don't have the reputation for that yet.) As a user of Caskroom.io, I would also recommend adding: sudo chown -R admin /opt/homebrew-cask sudo chmod -R g+w /opt/homebrew-cask since cask, an extremely useful extension to homebrew, puts all its files in /opt/homebrew-cask
Preface: It's no problem to install MAMP, MAMP Pro or Bitnami MAMP Stack on OS X Server (Yosemite or older). All of them are self-containing stacks and get installed to the /Applications folder. They don't interfere with any original software like Oracle MySQL/PostgreSQL/OS X Server postgres provided you don't use their distinctive ports. All the MAMP ...
I found the homebrew version of mysql worked perfectly on OS X 10.10.3 and 10.10. running Server. brew install mysql and all was good - mysql.server start starts it and mysql.server stop does the reverse.
For what it's worth, I have OSX 10.10.4 and my installation of MySQL 5.6.26 for OSX 10.9 worked fine and I can start/stop it successfully through System Preferences. What didn't work well: the default connection method is to localhost via socket and all attempts to enable connections via TCP to 127.0.0.1 proved futile.
Top 50 recent answers are included