MySQL Forums
Forum List  »  Utilities

MySQL Workbench can't connect to Fabric node
Posted by: Robert Sandiford
Date: April 11, 2016 01:16PM


We're evaluating MySQL HA using Fabric. We have a Fabric node up and running on a RHEL 7 server with backing store, and we can run the mysqlfabric commands on the node. i.e. everything there *seems* to be OK.

However, when we try to connect MySQL Workbench (as per, we keep getting

"Failed to Connect to MySQL at {address} fabric node with user admin. WbFabricInterface.openConnection(): Can't connect to MySQL server on '{address}' (10061)"

(where {address} is the server / port).

From the same MySQL Workbench, we can set up a normal Connection direct to the backing store, which is on the same server. So, we know we have the address right for that.

our MySQL Workbench connection properties are:
Connection Method: MySQL Fabric Management Node
Hostname {server name}
Port: 32274
Username: admin
Options MySQL Username fabric_server
Options H.A. Group Filter: none

Our Fabric config has these elements:

user = fabric_server
password = {password}
backup_user = fabric_backup
backup_password = {password}
restore_user = fabric_restore
restore_password = {password}
unreachable_timeout = 5

address = localhost:32274
threads = 5
user = admin
password = {password}
disable_authentication = no
realm = MySQL Fabric
ssl_ca =
ssl_cert =
ssl_key =

On the server, "netstat -tanp | grep 3227" yields:
tcp 0 0* LISTEN 2692/python
tcp 0 0* LISTEN 2692/python

We're using MySQL 5.7.12

We're using Fabric from the 1.5.6 version of the Utilities.

We're using MySQL Workbench version "6.3.6 build 517 CE" on a linux workstation, and "6.3.6 build 511 CE" on a Windows workstation - both are having the same trouble.

Any ideas?



Options: ReplyQuote

Written By
MySQL Workbench can't connect to Fabric node
April 11, 2016 01:16PM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.