- From: Nico Kadel-Garcia <
>
- To: "
" <
>
- Subject: [chef] RE: Re: Re: Re: Unable to connect to the mysql database server
- Date: Tue, 17 Feb 2015 11:24:12 -0600
- Accept-language: en-US
- Acceptlanguage: en-US
The approach of using command line passwords for mysql access causes problems
with MySQL 5.6, or at least that from Percona. It whinges unpreventably about
passwords in the command line, and obscures other more relevant error
messages.
I've worked around it by setting "MYSQL_PWD" environment variables for
relevant users to contain the relevant password, or setting a relevant
$HOME/.my.cnf and relying on that managed with a local cookbook with more
protected password data, instead. This can also help prevent including
plain-text MySQL passwords in monitoring and backup configurations for MySQL,
or in git managed central environments where passwords are sensitive. The
default use of plain text passwords by the mysql cookbook is actually a
security issue for setting up new servers.
Nico Kadel-Garcia
Lead DevOps Engineer
>
-----Original Message-----
>
From: Sean OMeara
>
[mailto:
>
Sent: Sunday, February 15, 2015 3:28 PM
>
To:
>
>
Subject: [chef] Re: Re: Re: Unable to connect to the mysql database server
>
>
It works, you just need to specify the path to the socket, or connect over
>
the
>
network.
>
>
From the README faq section:
>
>
mysql -h 127.0.0.1 -Ppassword
>
>
-s
Archive powered by MHonArc 2.6.16.