Bug #81637 Fabric - Invalid database connection
Submitted: 30 May 2016 7:29 Modified: 3 Jun 2016 5:20
Reporter: Philippe Florent Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Fabric Severity:S2 (Serious)
Version:1.5.6 OS:Debian (2.4)
Assigned to: CPU Architecture:Any
Tags: fabric debian

[30 May 2016 7:29] Philippe Florent
Description:
Cannot start mysql fabric

installed :

mysql-connector-python_2.1.3-1debian8.2_all.deb  
mysql-server_5.7.12-1debian8_amd64.deb-bundle.tar  
mysql-utilities_1.5.6-1debian8_all.deb

followed :

https://dev.mysql.com/doc/mysql-utilities/1.5/en/fabric-create-user.html
https://dev.mysql.com/doc/mysql-utilities/1.5/en/fabric-configuration-file.html

error: 

fabric python script cannot access/create database => "Invalid database connection"

but if I do it manualy, fabric_store has access and can create the db

How to repeat:
mysqlfabric manage start
[INFO] 1464592921.549109 - MainThread - Initializing persister: user (fabric_store), server (localhost:3306), database (mysql_fabric).
Error: Invalid database connection.

mysql -u fabric_store -p*********
mysql: [Warning] Using a password on the command line interface can be insecure.
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 58
Server version: 5.7.12 MySQL Community Server (GPL)

Copyright (c) 2000, 2016, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql> create database mysql_fabric;
Query OK, 1 row affected (0.00 sec)
[31 May 2016 12:09] Philippe Florent
been debugging the python script
apparently after the connector has done its handshage, mysql returns an error
"unknown database mysql_fabric"
wich is odd since the script is supposed to create the db after logging to the server (I guess)
[2 Jun 2016 11:39] MySQL Verification Team
Hello Philippe,

Thank you for the report.
Did you create the backing store before running 'mysqlfabric manage start'? Because it assumes that you have set up the backing store and looking at the error this seems to be the case here.

Please see - https://dev.mysql.com/doc/mysql-utilities/1.5/en/fabric-backing-store.html
https://dev.mysql.com/doc/mysql-utilities/1.5/en/fabric-man-mysqlfabric-manage.html

Thanks,
Umesh
[2 Jun 2016 13:34] Philippe Florent
you're the man !!

why did they put that information, two chapters below after the Quickstart chapter ???

anyway, thanks you saved my life
[3 Jun 2016 5:20] MySQL Verification Team
Thank you Philippe for confirming, closing the bug for now.