Bug #69177 | Can't connect to MySQL server on '127.0.0.1' (61) (code 2003)" | ||
---|---|---|---|
Submitted: | 8 May 2013 17:13 | Modified: | 14 May 2013 11:58 |
Reporter: | Salvatore Vaccarino | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Workbench: Migration | Severity: | S1 (Critical) |
Version: | 5.2.47 | OS: | MacOS (10.8.3) |
Assigned to: | CPU Architecture: | Any |
[8 May 2013 17:13]
Salvatore Vaccarino
[8 May 2013 18:57]
MySQL Verification Team
Thank you for the bug report. Please describe your failed action: servers version source/target, local/remote of both servers? Are you able to connect using both stored connection out of Migration Wizard?. Thanks.
[9 May 2013 9:05]
Salvatore Vaccarino
Both servers source/target are remote. They both have a Linux OS Source: Server: Localhost via UNIX socket Software: MySQL Software version: 5.0.67-community - MySQL Community Edition (GPL) Protocol version: 10 Target: Server: Localhost via UNIX socket Server version: 5.0.77 Protocol version: 10 Both servers are usable outside the connection wizard.
[14 May 2013 10:11]
Salvatore Vaccarino
Any updates on this?
[14 May 2013 11:58]
MySQL Verification Team
Hello Salvatore, I cannot repeat the reported behavior from local/remote with the stored connection for the reported environment(5.0.66->5.0.77). Interestingly, I'm able to hit the error which you are reported when I make the changes to one of the stored source/target environment's host details(be it source or target db) i.e from actual IP address to 127.0.0 then I get these details: Starting... Connect to source DBMS... - Connecting to source... Connecting to Mysql@127.0.0.1:5077... Traceback (most recent call last): File "D:\setups\MySQL Workbench 5.2.47 CE\modules\db_mysql_re_grt.py", line 61, in connect con.connect() File "D:\setups\MySQL Workbench 5.2.47 CE\modules\workbench\db_utils.py", line 168, 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 '127.0.0.1' (10061) (code 2003) Connecting to Mysql@127.0.0.1:5077... Traceback (most recent call last): File "D:\setups\MySQL Workbench 5.2.47 CE\modules\db_mysql_re_grt.py", line 61, in connect con.connect() File "D:\setups\MySQL Workbench 5.2.47 CE\modules\workbench\db_utils.py", line 168, 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 '127.0.0.1' (10061) (code 2003) Traceback (most recent call last): File "D:\setups\MySQL Workbench 5.2.47 CE\modules\workbench\wizard_progress_page_widget.py", line 66, in run self.func() File "D:\setups\MySQL Workbench 5.2.47 CE\modules\migration_source_selection.py", line 415, in task_connect raise e SystemError: MySQLError("Can't connect to MySQL server on '127.0.0.1' (10061) (code 2003)"): error calling Python module function DbMySQLRE.connect ERROR: Error during Connect to source DBMS: MySQLError("Can't connect to MySQL server on '127.0.0.1' (10061) (code 2003)"): error calling Python module function DbMySQLRE.connect ERROR: Exception in task 'Connect to source DBMS': SystemError('MySQLError("Can\'t connect to MySQL server on \'127.0.0.1\' (10061) (code 2003)"): error calling Python module function DbMySQLRE.connect',) Failed So, don't make changes to the stored connection's host details(be it source or target server) when using the migration wizard and should work.
[14 May 2013 12:00]
MySQL Verification Team
stored connection details
Attachment: 69177_1.png (image/png, text), 184.99 KiB.
[14 May 2013 12:00]
MySQL Verification Team
Changes to the stored source db connections..
Attachment: 69177_2.png (image/png, text), 202.15 KiB.
[14 May 2013 12:01]
MySQL Verification Team
Error at the end of migration
Attachment: 69177_3.png (image/png, text), 231.98 KiB.
[16 May 2013 19:54]
Stefan Zahnd
Hi, I have exactly the same problem. I created two connections (source and destination) through the "New Connection"-Wizard on the home screen. I can successfully connect to these two remote MySQL servers (Standard TCP/IP over SSH). The same stored connections aren't working in the Migration wizard or the Scheme transfer wizard. In the latter I even can't select the connections. The error message in the migration wizard is as follows: --- Traceback (most recent call last): File "/Applications/MySQLWorkbench.app/Contents/Resources/libraries/workbench/wizard_progress_page_widget.py", line 66, in run self.func() File "/Applications/MySQLWorkbench.app/Contents/PlugIns/migration_source_selection.py", line 415, in task_connect raise e SystemError: MySQLError("Can't connect to MySQL server on '127.0.0.1' (61) (code 2003)"): error calling Python module function DbMySQLRE.connect ERROR: Error during Connect to source DBMS: MySQLError("Can't connect to MySQL server on '127.0.0.1' (61) (code 2003)"): error calling Python module function DbMySQLRE.connect ERROR: Exception in task 'Connect to source DBMS': SystemError('MySQLError("Can\'t connect to MySQL server on \'127.0.0.1\' (61) (code 2003)"): error calling Python module function DbMySQLRE.connect',) --- Server OS is Ubuntu 12.04 and Debian 6. Client OS is Mac OS X 10.8.3. Kind regards
[4 Jul 2013 8:19]
Hegy Pascal
Hello, issue is still here with version 6.0.2 (beta) : http://bugs.mysql.com/69650