Bug #57683 mysqlbackup can not connect to mysqld if socket specified
Submitted: 23 Oct 2010 12:38 Modified: 26 Oct 2010 0:51
Reporter: Sveta Smirnova Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Enterprise Backup Severity:S3 (Non-critical)
Version:3.5.2 OS:Any
Assigned to: CPU Architecture:Any

[23 Oct 2010 12:38] Sveta Smirnova
Description:
mysqlbackup can not connect to mysqld if option --socket specified

How to repeat:
$$MYSQLBACKUP   --user=root  --socket=/tmp/mysql_ssmirnova.sock  ~/blade12/backup.cnf ./BACKUPDIR
mysqlbackup: Starting mysqlbackup with following arguments:
/users/ssmirnova/blade12/src/meb-3.5.next/meb-innobackup-c/mysqlbackup --user=root --socket=/tmp/mysql_ssmirnova.sock /users/ssmirnova/blade12/backup.cnf ./BACKUPDIR  

mysqlbackup: Unique backup id generated for the current backup operation is 12878373939899910 

mysqlbackup: Error: Can't connect to MySQL server on '127.0.0.1' (111)
mysqlbackup: Warning: Connection to MySQL Server failed for Backup Logging
mysqlbackup: IMPORTANT: Please check that backup run completes successfully.
            At the end of a successful 'backup' run mysqlbackup
            prints "mysqlbackup completed OK!".

mysqlbackup: Created backup directory './BACKUPDIR/2010-10-23_14-36-33'
mysqlbackup: Using ibbackup version 3.5.2 MySQL Enterprise Backup 3.5.2
mysqlbackup: Using MySQL client version: 5.1.47
mysqlbackup: Error: Can't connect to MySQL server on '127.0.0.1' (111)
mysqlbackup: Error: Connection to MySQL Server failed
mysqlbackup: Unique backup id generated for the current backup operation is 12878373940031260 

mysqlbackup: Error: Can't connect to MySQL server on '127.0.0.1' (111)
mysqlbackup: Warning: Connection to MySQL Server failed for Backup Logging
[25 Oct 2010 13:08] Ritheesh Vedire
Duplication of BUG#56894
This was already fixed.