Closed guriandoro closed 7 years ago
Hi Jervin!
I'll try to propose a fix for this after reviewing the code. I'll keep you updated :)
Sent PR over https://github.com/dotmanila/pyxbackup/pull/37.
I think it makes more sense to not use any hardcoded default (like /tmp/mysql.sock), and fall back to using localhost:3306
. Let me know what you think about it!
Agustín.
PR merged.
Using the following command:
/usr/bin/python /root/bin/pyxbackup full
with the following cnf file:
Contents of the named mysql cnf file are as follows:
This results in the tool using the following command:
xtrabackup --defaults-file=/root/.my.cnf --socket=/tmp/mysql.sock --host=localhost --no-timestamp --backup --parallel=4 --rsync --binlog-info=on --target-dir /backup/dbbackup/data04/backups/full/2017_10_09-19_31_45
As seen there, it is explicitly using
--socket=...
set to a socket that is not the correct one, making it fail with the following messages:Fix: pyxbackup should not try to explicitly set a socket that is not proven to work, and/or override the one defined in the named my.cnf file.