Bug #73019 need specific error: ServerError: Error accessing server (127.0.0.1:13002).,
Submitted: 17 Jun 2014 6:58 Modified: 10 Sep 2014 0:42
Reporter: Shane Bester (Platinum Quality Contributor) Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Fabric Severity:S3 (Non-critical)
Version:1.4.3 OS:Windows
Assigned to: CPU Architecture:Any

[17 Jun 2014 6:58] Shane Bester
Description:
The return line forgets to print what error it got.
It could be authentication error, or server is not even running, 
but it is not possible to determine what the problem is.

J:\mutils>mysqlfabric.exe --config=j:/mutils/scripts/etc/mysql/fabric.cfg group add my_group 127.0.0.1:13002
Password for admin:
Procedure :
{ uuid        = 7e4f3e6c-d113-454b-94b7-5a98351f69fb,
  finished    = True,
  success     = False,
  return      = ServerError: Error accessing server (127.0.0.1:13002).,
  activities  =
}

How to repeat:
try adding a note to a group but that node is not running, or the fabric user doesn't exist yet.
[10 Sep 2014 0:42] Philip Olson
Fixed as of the upcoming MySQL Utilities/Fabric 1.5.2 release, and here's the changelog entry:

Some of try/exception blocks were catching the DatabaseError exception and
raising a new exception without propagating information from the original
problem. 

The error messages were improved by adding
information about the server where the error originated, and the caught
DatabaseError information is merged into the appropriate objects.

Thank you for the bug report.