[chef] RE: mysql cookbook flushes /etc/my.cnf, breaks local socket access

[Kevin Keane Subscription < >]

Title: RE: [chef] mysql cookbook flushes /etc/my.cnf, breaks local socket access

Yet another alternative fix is to create a symbolic link for the socket file, from /var/run/mysql-default/mysql.sock to the default location /var/lib/mysql/mysql.sock (CentOS location - might be different in other distros). This, too, will only work with a single instance. I don't consider this a problem, since that's the nature of default values.

Kevin Keane

The NetTech

http://www.4nettech.com

Our values: Privacy, Liberty, Justice

See https://www.4nettech.com/corp/the-nettech-values.html

-----Original message-----
From: Nico Kadel-Garcia < >
Sent: Thursday 19th March 2015 9:41
To:
Subject: [chef] mysql cookbook flushes /etc/my.cnf, breaks local socket access

I was just working with the latest 'mysql' cookbook, and note that it is now insisting on creating individual mysql instances. That's fine, but it's relatively new behavior for those of us who used older major revisions of the cookbook. And one notable result is that it now deletes, and insists on deleting, /etc/my.cnf.

That it breaks local access is documented in the README.md, but how to restore or use socket based access is not. I've done a pull request some suggested updates to the README.md at https://github.com/chef-cookbooks/mysql/issues/314, and put in a ticket there. Basically, you have to read /etc/mysql-default/my.cnf or whatever new config file and use the socket setting from there.

The alternative fix, which I hesitate to put in a README.md, is to put a symlink from the single instance "/etc/mysql-default/my.cnf" to "/etc/my.cnf". That's a bit nasty, and I'd only use it on hosts with only one MySQL instance. But it works quite well.

Nico Kadel-Garcia
Lead DevOps Engineer