Homestead ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2 "No such file or directory")

http://stackoverflow.com/questions/11990708/error-cant-connect-to-local-mysql-server-through-socket-var-run-mysqld-mysq

apparmor was the culprit. Despite the contents of /etc/apparmor.d/usr.sbin.mysqld being nothing but comments and claiming that it was there so that apparmor wouldn't choke on MariaDB, that's exactly what was happening.

AppArmor and MySQL on an Oracle blog provided what I needed to figure out what was going on.

sudo aa-status shows you what apparmor is doing; what actually has an enforced policy, versus what's just set to complain.

sudo apt-get install apparmor-utils adds a few commands that make the apparmor profiles easier to deal with, such as...

sudo aa-complain /usr/sbin/mysqld turns the profile from "enforce" to complain. (aa-enforce turns it back.)

Once that's done, sudo service apparmor reload restarts apparmor, and voila... sudo /etc/init.d/mysql start works, and the server stays up.

Reference: https://askubuntu.com/questions/750604/why-does-mariadb-keep-dying-how-do-i-stop-it

I'm having what seems to be the same issue, but your solution gets me the following error:

ERROR: /etc/apparmor.d/usr.sbin.mysqld contains no profile

Anyone have thoughts on this?

@eclev91 I had the same issue, when following https://stackoverflow.com/questions/40997257/mysql-service-fails-to-start-hangs-up-timeout-ubuntu-mariadb my usr.sbin.mysqld file contained only several lines of comments and no real body. I added this to the file:

/usr/sbin/mysqld { }

Then the aa-complain command could succeed. (but, my mariadb still fails to stay up :( )

@neekfenwick I am having the same issue you described, did you manage to resolve it?