Bug #81218 MySQL Utilities should not depend on MySQL (login-paths)
Submitted: 28 Apr 2016 9:02 Modified: 10 Sep 2016 9:09
Reporter: Onno Steenbergen Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Utilities Severity:S3 (Non-critical)
Version:1.6.3, 1.6.4 OS:Any
Assigned to: CPU Architecture:Any

[28 Apr 2016 9:02] Onno Steenbergen
Description:
Similar problem as the closed bug #69197

To use login-paths with the MySQL utilities you need the mysqlclient development package (create login paths) and the mysql-community-server package (my_print_defaults executable).

# mysqlrplshow --master=manager-101 --discover-slaves-login=manager

Usage: mysqlrplshow --master=root@localhost:3306 

mysqlrplshow: error: Master connection values invalid: Unable to locate MySQL Client tools. Please confirm that the path to the MySQL client tools are included in the PATH. Error: Cannot find location of my_print_defaults. In addition, could not find a configuration file neither in the given path 'manager' nor the default path '/etc/mysql/manager'..

The setup I'm trying to achieve:
2+ MySQL Servers
1+ Server running mysqlfailover

How to repeat:
Install MySQL Utilities on a clean server
Try to manage a different server with MySQL using login-paths (mysqlreplicate, mysqlrplshow, mysqlfailover etc)

Suggested fix:
Include tool to create login paths in MySQL utilities (now in libmysqlclient-dev)
Utilities should not require my_print_defaults (in mysql-community-server)
[10 Sep 2016 9:09] Umesh Shastry
Hello Onno Steenbergen,

Thank you for the report.

Thanks,
Umesh