Description:
After setting up Enterprise Backup successfully, scheduling a backup, closing workbench, and then launching workbench again, Enterprise Backup will not be able to connect and gives an error "The existing 'mysqlbackup' MySQL user account will be used for backups once the correct password is provided."
This is misleading and incorrect.
After turning on debug3, I was able to see that the port and socket information are not being supplied in the command being executed.
If /etc/my.cnf does not contain port and socket under [client], enterprise backup will not connect.
This information is available in /etc/mebmanager.cnf and the connection information is extracted, but for some reason port and socket are missed.
-----------------------------------------------
18:31:38 [DB3][wb_server_management.pyc]: SSH:exec_cmd(): Done cmd="/usr/bin/sudo -u mysql -S -p EnterPasswordHere /bin/bash -c "/opt/mysql/meb-3.9/bin/mysqlbackup --user=mysqlbackup --password=password --port=3306 --no-history-logging backup --databases=mysql""
18:31:38 [DB1][wb_admin_meb_common.pyc]: MEB account validation output: MySQL Enterprise Backup version 3.9.0 [2013/08/23]
Copyright (c) 2003, 2013, Oracle and/or its affiliates. All Rights Reserved.
mysqlbackup: INFO: Starting with following command line ...
/opt/mysql/meb-3.9/bin/mysqlbackup --user=mysqlbackup
--password=xxxxxxxxxxxxxxxx --port=3306 --no-history-logging backup
--databases=mysql
140225 18:31:38 mysqlbackup: WARNING: Can not establish connection to mysql server.
Connection open fails with error "Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)"
mysqlbackup: ERROR: Connection initialization error.
mysqlbackup failed with errors!
-----------------------------------------------
-----------------------------------------------
poc-mysql3-ep:jduce/etc > sudo cat /etc/mebmanager.cnf
# Server wide settings for MySQL Workbench, Enterprise Backup
[meb_manager]
mysql_instance_1 = /var/lib/mysql/
[mysql_instance_1]
socket = /var/lib/mysql/mysql.sock
mysql_version = 5.6.15-enterprise-commercial-advanced-log
datadir = /var/lib/mysql/
innodb_data_home_dir =
datadir_owner = mysql
host = poc-mysql3-ep.tops.gdi
command = /opt/mysql/meb-3.9/bin/mysqlbackup
user = mysqlbackup
home = /opt/mysql_backup
password = password
port = 3306
-----------------------------------------------
After adding the port and socket information to the [client] section of /etc/my.cnf, a connection was able to be made and the Online Backup screen loads.
However, there is still another error in the logs stating that --backup-dir was missing.
-----------------------------------------------
20:29:12 [DB3][wb_server_management.pyc]: SSH:exec_cmd(): Done cmd="/usr/bin/sudo -u mysql -S -p EnterPasswordHere /bin/bash -c "/opt/mysql/meb-3.9/bin/mysqlbackup --user=mysqlbackup --password=v8GxVKj8uJakfrHs --port=3306 --no-history-logging backup --databases=mysql""
20:29:12 [DB1][wb_admin_meb_common.py]: MEB account validation output: MySQL Enterprise Backup version 3.9.0 [2013/08/23]
Copyright (c) 2003, 2013, Oracle and/or its affiliates. All Rights Reserved.
mysqlbackup: INFO: Starting with following command line ...
/opt/mysql/meb-3.9/bin/mysqlbackup --user=mysqlbackup
--password=xxxxxxxxxxxxxxxx --port=3306 --no-history-logging backup
--databases=mysql
mysqlbackup: INFO: MySQL server version is '5.6.15-enterprise-commercial-advanced-log'.
mysqlbackup: INFO: Got some server configuration information from running server.
mysqlbackup: ERROR: Missing or invalid option:
Missing or empty --backup-dir option specified.
Specified Operation:backup
Use --help option for usage description.
mysqlbackup failed with errors!
-----------------------------------------------
How to repeat:
Connect to MySQL instance running on linux that does not have anything set up for [client] in the /etc/my.cnf.
Setup Enterprise Backup in workbench under Online Backup.
Quit workbench.
Launch workbench.
Open Enterprise Backup.
Go back in to Online Backup.
Error should occur.
Suggested fix:
Pass all the appropriate variables.
Description: After setting up Enterprise Backup successfully, scheduling a backup, closing workbench, and then launching workbench again, Enterprise Backup will not be able to connect and gives an error "The existing 'mysqlbackup' MySQL user account will be used for backups once the correct password is provided." This is misleading and incorrect. After turning on debug3, I was able to see that the port and socket information are not being supplied in the command being executed. If /etc/my.cnf does not contain port and socket under [client], enterprise backup will not connect. This information is available in /etc/mebmanager.cnf and the connection information is extracted, but for some reason port and socket are missed. ----------------------------------------------- 18:31:38 [DB3][wb_server_management.pyc]: SSH:exec_cmd(): Done cmd="/usr/bin/sudo -u mysql -S -p EnterPasswordHere /bin/bash -c "/opt/mysql/meb-3.9/bin/mysqlbackup --user=mysqlbackup --password=password --port=3306 --no-history-logging backup --databases=mysql"" 18:31:38 [DB1][wb_admin_meb_common.pyc]: MEB account validation output: MySQL Enterprise Backup version 3.9.0 [2013/08/23] Copyright (c) 2003, 2013, Oracle and/or its affiliates. All Rights Reserved. mysqlbackup: INFO: Starting with following command line ... /opt/mysql/meb-3.9/bin/mysqlbackup --user=mysqlbackup --password=xxxxxxxxxxxxxxxx --port=3306 --no-history-logging backup --databases=mysql 140225 18:31:38 mysqlbackup: WARNING: Can not establish connection to mysql server. Connection open fails with error "Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)" mysqlbackup: ERROR: Connection initialization error. mysqlbackup failed with errors! ----------------------------------------------- ----------------------------------------------- poc-mysql3-ep:jduce/etc > sudo cat /etc/mebmanager.cnf # Server wide settings for MySQL Workbench, Enterprise Backup [meb_manager] mysql_instance_1 = /var/lib/mysql/ [mysql_instance_1] socket = /var/lib/mysql/mysql.sock mysql_version = 5.6.15-enterprise-commercial-advanced-log datadir = /var/lib/mysql/ innodb_data_home_dir = datadir_owner = mysql host = poc-mysql3-ep.tops.gdi command = /opt/mysql/meb-3.9/bin/mysqlbackup user = mysqlbackup home = /opt/mysql_backup password = password port = 3306 ----------------------------------------------- After adding the port and socket information to the [client] section of /etc/my.cnf, a connection was able to be made and the Online Backup screen loads. However, there is still another error in the logs stating that --backup-dir was missing. ----------------------------------------------- 20:29:12 [DB3][wb_server_management.pyc]: SSH:exec_cmd(): Done cmd="/usr/bin/sudo -u mysql -S -p EnterPasswordHere /bin/bash -c "/opt/mysql/meb-3.9/bin/mysqlbackup --user=mysqlbackup --password=v8GxVKj8uJakfrHs --port=3306 --no-history-logging backup --databases=mysql"" 20:29:12 [DB1][wb_admin_meb_common.py]: MEB account validation output: MySQL Enterprise Backup version 3.9.0 [2013/08/23] Copyright (c) 2003, 2013, Oracle and/or its affiliates. All Rights Reserved. mysqlbackup: INFO: Starting with following command line ... /opt/mysql/meb-3.9/bin/mysqlbackup --user=mysqlbackup --password=xxxxxxxxxxxxxxxx --port=3306 --no-history-logging backup --databases=mysql mysqlbackup: INFO: MySQL server version is '5.6.15-enterprise-commercial-advanced-log'. mysqlbackup: INFO: Got some server configuration information from running server. mysqlbackup: ERROR: Missing or invalid option: Missing or empty --backup-dir option specified. Specified Operation:backup Use --help option for usage description. mysqlbackup failed with errors! ----------------------------------------------- How to repeat: Connect to MySQL instance running on linux that does not have anything set up for [client] in the /etc/my.cnf. Setup Enterprise Backup in workbench under Online Backup. Quit workbench. Launch workbench. Open Enterprise Backup. Go back in to Online Backup. Error should occur. Suggested fix: Pass all the appropriate variables.