xtrabackup doesn't read the socket information from the server configuration
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB | Status tracked in 2.4 | |||||
2.3 |
Fix Released
|
High
|
EvgeniyPatlan | |||
2.4 |
Fix Released
|
High
|
EvgeniyPatlan |
Bug Description
xtrabackup doesn't read the socket information from the server configuration even if it's there:
cat /etc/my.cnf
[mysqld]
datadir=
socket=
user=mysql
# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0
This requires socket to be specified either in the client config or on the command line, otherwise backup fails:
xtrabackup --backup --target-
170216 10:32:53 version_check Connecting to MySQL server with DSN 'dbi:mysql:
170216 10:32:53 version_check Connected to MySQL server
170216 10:32:53 version_check Executing a version check against the server...
170216 10:32:53 version_check Done.
170216 10:32:53 Connecting to MySQL server host: localhost, user: root, password: not set, port: not set, socket: not set
Failed to connect to MySQL server: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2).
xtrabackup will no longer read socket from server config, instead it will replicate behaviour of mysql cli. socket will be read from [client] section or from [xtrabackup] section. Default value will be set at the build time in packaging scripts as it is done for MySQL and PS.