MySQL Bugs: #69197: MySQL Utilities should not depend on MySQL

Bug #69197	MySQL Utilities should not depend on MySQL
Submitted:	10 May 2013 13:05	Modified:	11 Jul 2013 5:43
Reporter:	Daniël van Eeden (OCA)	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Utilities	Severity:	S3 (Non-critical)
Version:	1.3.1	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
As the MySQL Utilities should be installed on a separate server for mysqlfailover it should not depend on the MySQL server and/or client. It should only depend on MySQL Connector/Python.

How to repeat:
root@dbmgt:~# mysqlserverinfo --server=ruser:rpass@192.168.1.5
# Source on 192.168.1.5: ... connected.
ERROR: Cannot find location of my_print_defaults.

Suggested fix:
If the MySQL client package is required then it the error message should clearly indicate this. Otherwise all commands should be able to run without the MySQL client package.

Even with the server and client package installed it gives an error.

root@db1mgt:~# mysqlserverinfo --server=ruser:rpass@192.168.1.5
# Source on 192.168.1.5: ... connected.
ERROR: Cannot find location of my_print_defaults.
root@db1mgt:~# which my_print_defaults
/usr/bin/my_print_defaults
root@db1mgt:~# mysqlserverinfo --version
MySQL Utilities mysqlserverinfo version 1.3.1 (part of MySQL Workbench Distribution 5.2.47)
Copyright (c) 2010, 2013 Oracle and/or its affiliates. All rights reserved.
This is a release of dual licensed MySQL Utilities. For the avoidance of
doubt, this particular copy of the software is released
under the version 2 of the GNU General Public License.
MySQL Utilities is brought to you by Oracle.

root@db1mgt:~# /usr/bin/my_print_defaults --version
/usr/bin/my_print_defaults  Ver 1.6 for debian-linux-gnu at x86_64

Hello Daniel,

Thank you for the report.
Verified as described.

Thanks,
Umesh

## Observed only when connecting remote server, for local host it works and doesn't complain

[root@cluster-repo tmp]# mysqlserverinfo  --server=ushastry:123@10.178.59.121:3306 -d --format=vertical
# Source on 10.178.59.121: ... connected.
ERROR: Cannot find location of my_print_defaults.
[root@cluster-repo tmp]#
[root@cluster-repo tmp]#
[root@cluster-repo tmp]# rpm -qa|grep -i mysql
mysql-connector-python-1.0.10-1.el6.noarch
mysql-utilities-1.3.1-1.el6.noarch
perl-DBD-MySQL-4.013-3.el6.x86_64
[root@cluster-repo tmp]# which my_print_defaults
/usr/bin/which: no my_print_defaults in (/usr/lib64/qt-3.3/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/data/ushastry/bin)
[root@cluster-repo tmp]# which mysql
/usr/bin/which: no mysql in (/usr/lib64/qt-3.3/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/data/ushastry/bin)
[root@cluster-repo tmp]#

// localhost

[root@cluster-repo tmp]# mysqlserverinfo  --server=ushastry:123@localhost:3307 -d --format=vertical
# Source on localhost: ... connected.
*************************       1. row *************************
         server: localhost:3307
        version: 5.6.10-log
        datadir: /tmp/slavedata/
        basedir: /data/ushastry/server/mysql-5.6.10
     plugin_dir: /data/ushastry/server/mysql-5.6.10/lib/plugin/
    config_file: /data/ushastry/server/mysql-5.6.10/my.cnf
     binary_log: cluster-repo-bin.000001
 binary_log_pos: 541
      relay_log: None
  relay_log_pos: None
1 rows.

Defaults for server localhost:3307
#...done.

Fixed as of MySQL Utilities 1.2.4/1.3.3, and two changelog entries were added.

First,

The "mysqlserverinfo" utility displayed misleading error information when
accessing a remote MySQL server. The utility would attempt to retrieve the
configuration defaults of the specified remote MySQL server, but they can
only be retrieved locally. A proper warning is now emitted.

Second,

The "--start-timeout" option was added to the "mysqlserverinfo" utility.
It determines the number of seconds to wait for the server to be online
when started in read-only mode using the "--start" option. The default
value is 10 seconds.

And the documentation was also updated.

Thank you for the bug report.