Error the server quit without updating pid file

Rated 3.95/5 based on 767 customer reviews

I successfully installed Python and My SQL via Home Brew. After My SQL Installation, I followed the first 2 steps - unset and the November, 2014: If you're getting this error on My SQL 5.6.x on Mac OS X Mavericks or Yosemite and want to use My SQL with PHP locally (/tmp/is where PHP PDO expects to find the sock file), here is what fixed it for me:1) Uncomment the default homebrew config file lines and edit as below Network as the unique id for your computer on the network.2) Set permissions on all the files in the mysql datadir. My SQL is very picky about this and refuses to create the pid file unless it (the user _mysql) owns the directory.--basedir=/usr/local/Cellar/mysql/5.6.21 --datadir=/usr/local/var/mysql --plugin-dir=/usr/local/Cellar/mysql/5.6.21/lib/plugin --verbose --log-error=/usr/local/var/mysql/BOXNAME.--pid-file=/usr/local/var/mysql/BOXNAME.I'm not sure why that worked for me but it shows you where I got the config file options from.

I had to remove that file and restart the server: I've got a similar problem with My SQL on a Mac (Mac Os X Could not startup My SQL Server.

(/data/mysql/err) #If that all happens to you, than most probably the issue is caused by SELinux. If you see output below: shell sestatus SELinux status: enabled SELinuxfs mount: /selinux Current mode: enforcing Mode from config file: enforcing Policy version: 24 Policy from config file: targeted #then you have SELinux on.

#(If you see that SELinux is disabled, then probably you have some other root cause and the rest of the post will not be a solution for you.) #You can turn SELinux off by editing file (/etc/selinux/config - update - SELINUX=disabled , save, reboot) #but this will reduce the security of your system and generally not recommended.

This means Read Write Execute, or full rights to all users to that folder and (-R) all files and folders under that folder.

For detailed explanation, please take a look at the following link: linux.com/learn/understanding-linux-file-permissions My issue was that I started server as sudo once and then tried to restart as a local user.

Leave a Reply