| Bug #53271 | Error in dump module: error calling WbAdmin.openExportImport | ||
|---|---|---|---|
| Submitted: | 28 Apr 2010 21:33 | Modified: | 7 May 2010 13:29 |
| Reporter: | J Chimene | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Workbench: Administration | Severity: | S2 (Serious) |
| Version: | 5.2.20 | OS: | Linux (Debian Lenny) |
| Assigned to: | Alfredo Kojima | CPU Architecture: | Any |
| Tags: | regression | ||
[29 Apr 2010 0:16]
MySQL Verification Team
Thank you for the bug report. Which OS are you using?. I couldn't repeat on Vista Ultimate X86_64.
[29 Apr 2010 0:22]
J Chimene
I've been building from source since the first 5.2 beta, using
"./debian/rules binary" then dpkg -i {the resulting .deb}
I remember using the import/export in 5.2.19; which is why I tried it in 5.2.20
[29 Apr 2010 12:24]
Susanne Ebrecht
Maybe Workbench is not able to find your mysqldump. Click on: Edit -> preferences -> Administrator and look there if PATH to mysqldump is correct. Also look if your user has rights to execute mysqldump.
[29 Apr 2010 12:33]
MySQL Verification Team
Thank you for the feedback. I was able to repeat on Fedora Core 12 X86_64 but with random crash not all the times I can repeat.
[3 May 2010 14:34]
Alfredo Kojima
Hi Can you attach your ~/.mysql/workbench/server_instances.xml file? If you dont want to share some info in the file, feel free to replace the text with XXXXX, but remove the least amount of info possible.
[3 May 2010 18:48]
Alfredo Kojima
Thank you for the extra info. As a workaround, you can dbl-click the instance in the Home page and switch to the Import/Export tab once the Administrator opens.
[4 May 2010 21:35]
Johannes Taxacher
fix confirmed in repository
[7 May 2010 13:29]
Tony Bedford
An entry has been added to the 5.2.21 changelog: An error was generated when a server was selected from the Import/Export MySQL Data dialog, displayed after clicking the Manage Import/Export action item on the Home screen.
Description: Click on "Manage Import/Export", select mysql server. Import/Export worked in 5.2.19 Version built from generic source via "./debian/rules binary" system is 2.6.32-trunk-amd64 #1 SMP Sun Jan 10 07:51:13 UTC 2010 x86_64 GNU/Linux mysql Ver 14.14 Distrib 5.1.45, for debian-linux-gnu (i486) using readline 6.1 Log details =========== ** (mysql-workbench-bin:26446): WARNING **: :186: link 'com.mysql.wb.toolbar.dbquery' <object db.Toolbar> key=owner could not be resolved ** Message: function call error Traceback (most recent call last): File "/usr/lib/mysql-workbench/modules/wb_admin_grt.py", line 270, in openExportImport tab = do_open_administrator(server) File "/usr/lib/mysql-workbench/modules/wb_admin_grt.py", line 129, in do_open_administrator adminTab = AdministratorTab(server_instance) File "/usr/lib/mysql-workbench/modules/wb_admin_grt.py", line 90, in __init__ self.ctrl_be = wb_admin_control_be.MyCtrl(server_instance_settings) File "/usr/lib/mysql-workbench/modules/wb_admin_control_be.py", line 584, in __init__ if connect_sql and self.server_is_stopped_for_sure(): File "/usr/lib/mysql-workbench/modules/wb_admin_control_be.py", line 832, in server_is_stopped_for_sure return self.is_running() File "/usr/lib/mysql-workbench/modules/wb_admin_control_be.py", line 850, in is_running result = self.exec_cmd(script, usesudo, password) File "/usr/lib/mysql-workbench/modules/wb_admin_control_be.py", line 928, in exec_cmd result = run_cmd(self.wrap_command(script, sudo), sudo, password) File "/usr/lib/mysql-workbench/modules/wb_admin_control_be.py", line 822, in wrap_command wcmd = self.sudo_prefix + " \"" + wcmd + "\"" TypeError: unsupported operand type(s) for +: 'NoneType' and 'str' How to repeat: Click on "Manage Import/Export", select mysql server.