Bug #74492 MySQL fabric setup problem
Submitted: 22 Oct 2014 5:04 Modified: 27 Oct 2014 14:47
Reporter: Mahesh Patil Email Updates:
Status: Duplicate Impact on me:
Category:MySQL Fabric Severity:S2 (Serious)
Version:1.5.2 OS:Linux (Centos 6.3)
Assigned to: CPU Architecture:Any

[22 Oct 2014 5:04] Mahesh Patil
I am getting this error 

[mysql@dev-dm-gitest101z /root]# mysqlfabric manage setup

Error : 
[INFO] 1413953890.788408 - MainThread - Initializing persister: user (fabric), server (dev.local:3301), database (fabric).
Error: Command (CREATE TABLE providers (provider_id VARCHAR(256) NOT NULL, type INT NOT NULL, username VARCHAR(100) NOT NULL, password VARCHAR(128) NOT NULL, url VARCHAR(256) NOT NULL, tenant VARCHAR(100) NOT NULL, default_image VARCHAR(256), default_flavor VARCHAR(256), CONSTRAINT pk_provider_id PRIMARY KEY (provider_id)), ()) failed accessing (dev.local:3301). 1071 (42000): Specified key was too long; max key length is 767 bytes.

How to repeat:
$  mysqlfabric manage setup

Suggested fix:
I think those tables should get created without any problem
[22 Oct 2014 5:49] Mahesh Patil
Now I am getting this error 

$ mysqlfabric manage setup
[INFO] 1413955889.898494 - MainThread - Initializing persister: user (fabric), server (localhost:3301), database (fabric).
Error: Command (CREATE TABLE log (subject VARCHAR(40) NOT NULL, reported TIMESTAMP /*!50604 (6) */ NOT NULL, reporter VARCHAR(64) NOT NULL, message TEXT, category int NOT NULL, type int NOT NULL, INDEX key_subject_reported (subject, reported), INDEX key_reporter (reporter), INDEX key_reported (reported), INDEX key_category (category), INDEX key_type (type)), ()) failed accessing (localhost:3301). 2055: Lost connection to MySQL server at 'localhost:3301', system error: timed out.
[22 Oct 2014 6:41] Mahesh Patil
I am interchangibly getting the errors reported basically I am unable to complete fabric mangement first process.
[22 Oct 2014 12:42] Fernando Ipar
What character set are you using as default on the server? 
I can't reproduce this but I'm using latin1. I think you may be using utf8 or another charset that can use 3 or more bytes per character. 

If so, I'd guess the best solution would be to use an integer PK for the providers table (and for any other tables as you're likely to hit this problem on any other table with a character PK).
[27 Oct 2014 14:47] Mats Kindahl
Thank you for the bug report. I agree that this should work without problems. This bug is a duplicate of BUG#74192.
[27 Oct 2014 14:48] Mats Kindahl
Hi Fernando,

The bug can be reproduced if you try to use UTF-8.