Bug #68126 Migration failure in MySQL Workbench 5.2.44 rev 9933
Submitted: 19 Jan 2013 17:46 Modified: 21 Feb 2013 20:45
Reporter: Mark Garber Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench: Migration Severity:S3 (Non-critical)
Version:5.2.44 OS:Linux (Migration failure: MySQL local to MySQL remote)
Assigned to: CPU Architecture:Any
Tags: migration, MySQL Workbench

[19 Jan 2013 17:46] Mark Garber
Description:
The problem was encounted at "Fetch Schemata List " in the wizard in an attempt to transfer a database running on an 
Ubuntu 12.10 host (Desktop) to an Unbuntu 12.10 server running as a virtual machine on the KVM (QEMU) platform within
the host.  The host and server are networked on IPv6.  The following log is produced:
Starting...
Connect to source DBMS...
- Connecting to source...
Connect to source DBMS done
Check target DBMS connection...
- Connecting to target...
Connecting to Mysql@ip6-localhost:3306@test.usadance.org:22...
Traceback (most recent call last):
  File "/usr/lib/mysql-workbench/modules/db_mysql_fe_grt.py", line 137, in connect
    con.connect()
  File "/usr/share/mysql-workbench/libraries/workbench/db_utils.py", line 169, in connect
    raise MySQLError(modules.DbMySQLQuery.lastError(), modules.DbMySQLQuery.lastErrorCode(), "%s@%s" % (self.connect_info.parameterValues["userName"], self.connect_info.parameterValues["hostName"]))
workbench.db_utils.MySQLError: Can't connect to MySQL server on 'ip6-localhost' (111) (code 2003)
Connecting to Mysql@ip6-localhost:3306@test.usadance.org:22...
Traceback (most recent call last):
  File "/usr/lib/mysql-workbench/modules/db_mysql_fe_grt.py", line 137, in connect
    con.connect()
  File "/usr/share/mysql-workbench/libraries/workbench/db_utils.py", line 169, in connect
    raise MySQLError(modules.DbMySQLQuery.lastError(), modules.DbMySQLQuery.lastErrorCode(), "%s@%s" % (self.connect_info.parameterValues["userName"], self.connect_info.parameterValues["hostName"]))
workbench.db_utils.MySQLError: Can't connect to MySQL server on 'ip6-localhost' (111) (code 2003)

Traceback (most recent call last):
  File "/usr/share/mysql-workbench/libraries/workbench/wizard_progress_page_widget.py", line 65, in run
    self.func()
  File "/usr/lib/mysql-workbench/modules/migration_source_selection.py", line 450, in task_test_target
    raise e
SystemError: MySQLError("Can't connect to MySQL server on 'ip6-localhost' (111) (code 2003)"): error calling Python module function DbMySQLFE.connect
ERROR: Error during Check target DBMS connection: MySQLError("Can't connect to MySQL server on 'ip6-localhost' (111) (code 2003)"): error calling Python module function DbMySQLFE.connect

Traceback (most recent call last):
  File "/usr/share/mysql-workbench/libraries/workbench/wizard_progress_page_widget.py", line 543, in update_status
    task.run()
  File "/usr/share/mysql-workbench/libraries/workbench/wizard_progress_page_widget.py", line 80, in run
    raise e
SystemError: MySQLError("Can't connect to MySQL server on 'ip6-localhost' (111) (code 2003)"): error calling Python module function DbMySQLFE.connect
ERROR: Exception in task 'Check target DBMS connection': SystemError('MySQLError("Can\'t connect to MySQL server on \'ip6-localhost\' (111) (code 2003)"): error calling Python module function DbMySQLFE.connect',)

Failed

How to repeat:
The "Source Selection" is setup with a local connection to MySQL on the host.
"Source Selection" is tested for good connection.
The "Target Selection" is connected to a the virtual machine via ssh.  A local connection to the root database user via ssh.
"Target Selection" is tested for good connection.
When "Next" is chosen the the "Message Log" appears ...See description.

Suggested fix:
Please send a suggestion.
[21 Jan 2013 20:45] MySQL Verification Team
Please try version 5.2.45. Thanks.
[22 Feb 2013 1:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".