MySQL Bugs: #58098: Server Admin Manage Import/Export link Returns Error

Bug #58098	Server Admin Manage Import/Export link Returns Error
Submitted:	9 Nov 2010 22:19	Modified:	22 Nov 2011 6:38
Reporter:	Dave Kelly	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: Administration	Severity:	S2 (Serious)
Version:	5.2.29 CE GA, 5.2.30, 5.2.31a	OS:	Windows (WS2008 Std SP2 x86 32-bit, Win7 Pro x64 64-bit (MySQL Srv 5.1.44, 5.1.48, 5.5.8 (32-bit/64-bit) GA)
Assigned to:		CPU Architecture:	Any
Tags:	Data Dump, excess cpu cycles, export, hang, import, slow performance, WbAdmin.openExportImport, workbench 5.2

Description:
In the Home screen, clicking the Manage Import/Export link under Server Administration returns the following error message in the lower status bar area when the Admin screen opens:

"Error in dump module: error calling WbAdmin.openExportImport: see output for details."

Instead of landing on the Data Dump tab, the Startup tab is selected (which in my case is disabled because I don't have an SSH daemon and consequently cannot use Remote Administration).  Selecting the Data Dump tab immediately causes the CPU cycles consumed to jump up to between 50% and 60%.

Although the Data Dump tab at first appears to work, switching between sub-tabs (Export to Disk, Import from Disk, Advanced Export Options) reveals extremely slow performance:  screens takes 10's of seconds to update visibility of all controls, scrolling causes loss of visibility of controls, and between 50% to 60% of CPU cycles are being consumed while idle.

NOTE: the old GUI tools 5.0 work fine, so this is not being caused by the MySQL server, or anything else in my system for that matter.

How to repeat:
In the Home screen, click the Manage Import/Export link under Server Administration; then, in the Admin screen, try selecting and using the Data Dump features.

Contents of Output Window after error message.

Attachment: MySqlWB-errors-output.txt (text/plain), 711 bytes.

Garbled display after switching from (Data Dump) Export tab to Advanced tab.

Attachment: DataDumpAdvTab.png (image/png, text), 63.58 KiB.

Garbled display after scrolling on (Data Dump) Advanced tab.

Attachment: DataDumpAdvTab2.png (image/png, text), 63.36 KiB.

Garbled display after switching from (Data Dump) Import tab to Export tab.

Attachment: DataDumpExpTab.png (image/png, text), 65.45 KiB.

Forgot to mention:  while the Admin screen is open, switching off of the Data Dump tab to other tabs only reduces CPU cycles consumed by about 5%; however, closing the Admin screen (returning to Home screen) returns the CPU cycles consumed back down to normal--about 2% total.

Could you please try new version 5.2.30. Thanks in advance.

OK, I've uninstalled 5.2.29 and installed 5.2.30 as requested.  I still get the same error message when opening the Data Dump tab:

"Error in dump module: error calling WbAdmin.openExportImport: see output for details."

I've attached the contents of the Output window in a text file.

However, the newer version does seem to perform a little better, but is still consuming too many CPU cycles.  The screens are refreshing at an acceptable rate, albeit a little slowly, but entering the Administration screen (regardless of which tab) causes the CPU cycles consumed to rise to an average of 40% (idle) to 50% or more when performing various tasks.  Switching to the Home screen, or closing the Administration screen returns CPU cycles to normal (about 2%).

Contents of MySQL WB 5.2.30 Output Window after error message.

Attachment: MySqlWB_5.2.30-OutputWin-Contents.txt (text/plain), 708 bytes.

Seems there are two bugs here - I want to add details to the CPU Cycles bit.

Admin/Data Dump worked fine for me on 29. I upgraded to 30 and now, when I choose Admin of a remote server (without SSH), CPU jumps to 50% (dual core PC, so 100% of the CPU core). Everything hangs or goes extremely slowly.
Clicking the Advanced Export Options screws the display (the top frame of options eventually appears, any other options do not appear, even after a 5 minute wait).

Click off this tab to another one, cpu returns to normal.

I'm rolling back to 5.2.29 until this is fixed... unless you've done what you did on 5.2.28 and made it impossible to rollback - that'll be fun.

Impact: High - I can't back up any tables on remote databases.

Note: This is the second time in three releases that Admin functions have broken with a GA - does anyone test them?

Update on last comment: I uninstalled and reverted to 5.2.29. Now runs, but excruciatingly slowly. 

Let me know what information you need to resolve this bug.
For now:
Workbench version:
MySQL Workbench CE for Windows version 5.2.29
Data Directory: C:\Program Files\MySQL\MySQL Workbench 5.2 CE
Cairo Version: 1.8.8
Rendering Mode: OpenGL is available on this system, so OpenGL is used for rendering.
OpenGL Driver Version: 1.5.0 - Build 6.14.10.4873
OS: Microsoft Windows XP Professional Service Pack 3 (build 2600)
CPU: 2x Intel(R) Core(TM)2 Duo CPU     T5670  @ 1.80GHz, 2.0 GiB RAM
Video adapter info:
Adapter type: Mobile Intel(R) 965 Express Chipset Family
Chip Type: Mobile Intel(R) 965 Express Chipset Family
BIOS String: Intel Video BIOS
Video Memory: 393216 KB
Current user language: English (United Kingdom)

Remote servers are non-ssh over a VPN'd WAN.

I still couldn't repeat on Vista 64-bit, please try 5.2.31 if it resolves the issue. Thanks in advance.

OK, I Uninstalled 5.2.30 and Installed 5.2.31a (rev 7115).  Still getting the same error message in the lower status bar area:

'Error in dump module: error calling WbAdmin.openExportImport: see output for details'

I've attached the Output window contents in a text file (OutputError-WBv5_2_31a.txt).

However, I notice a marked improvement in performance.  The CPU cycles consumed stay within nominal range during ops.  Although I haven't exercised all functions yet, it appears that at least that part of the problem is fixed.

But, the error message is troubling and it makes me reluctant to use this tool until the error is resolved.

May I suggest that the same operating system on which a bug is reported is used when trying to reproduce a problem, or at least the same architecture (i.e., x86 verus x64) if not the same OS.

Unless someone knows that a specific update fixes this problem, I won't be doing any more tests of incremental updates on the off chance that it will be fixed. (Sorry, just don't have the time now.)

Thanks.

Contents of MySQL WB 5.2.31a Output Window after error message.

Attachment: OutputError-WBv5_2_31a.txt (text/plain), 711 bytes.

Updated the versions affected.

FYI:  I just tested WB 5.2.31a on Window 7 Pro 64-bit and got the same error message in the status bar area after clicking Manage Import/Export:

'Error in dump module: error calling WbAdmin.openExportImport: see output for details'

So, I updated the OS details.  I also removed 'Data Dump features hang' from the bug synopsis, as the hanging (excess CPU cycles consumption) problem seems to have been fixed with version 5.2.31a.

I've attached a file (Win7x64-WB-5.2.31a-OutputError.txt) with the contents of the Output window while running on Windows 7 Pro 64-bit, which seems to have more detail and may provide better clues about the error message referred to above.

Contents of MySQL WB 5.2.31a Output Window after error message (when running on Windows 7 Pro 64-bit).

Attachment: Win7x64-WB-5.2.31a-OutputError.txt (text/plain), 1.74 KiB.

Thank you for the feedback.

Updated version details.

I have the same error with a different config.

Windows 2008 R2 x64
Workbench 5.2.31a
MySQL 5.1.52 x64

Output:
WMIShell: Set filters for local windows cli

WMIShell: Set filters for local windows cli

Option verbose  skipped because of missing value

Option standalone  skipped because of missing value

Option one-thread  skipped because of missing value

Option des-key-file  skipped because of missing value

Option innodb_rollback_on_timeout  skipped because of missing value

Option slave-skip-errors  skipped because of missing value

Option large-pages  skipped because of missing value

Option bootstrap  skipped because of missing value

WMIShell: Set filters for local windows cli

WMIShell: Set filters for local windows cli

Option verbose  skipped because of missing value

Option standalone  skipped because of missing value

Option one-thread  skipped because of missing value

Option des-key-file  skipped because of missing value

Option innodb_rollback_on_timeout  skipped because of missing value

Option slave-skip-errors  skipped because of missing value

Option large-pages  skipped because of missing value

Option bootstrap  skipped because of missing value

WMIShell: Set filters for local windows cli

Traceback (most recent call last):

  File "C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE\modules\wb_admin_grt.py", line 305, in openExportImport

    tab.wait_server_check(4)

  File "C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE\modules\wb_admin_grt.py", line 133, in wait_server_check

    while self.configuration.last_is_running_check is None and time.time() - t < timeout:

  File "C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE\mforms.py", line 665, in <lambda>

    __getattr__ = lambda self, name: _swig_getattr(self, Box, name)

  File "C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE\mforms.py", line 34, in _swig_getattr

    raise AttributeError,name

AttributeError: last_is_running_check

WMIShell: Set filters for local windows cli

Traceback (most recent call last):

  File "C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE\modules\wb_admin_grt.py", line 305, in openExportImport

    tab.wait_server_check(4)

  File "C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE\modules\wb_admin_grt.py", line 133, in wait_server_check

    while self.configuration.last_is_running_check is None and time.time() - t < timeout:

  File "C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE\mforms.py", line 665, in <lambda>

    __getattr__ = lambda self, name: _swig_getattr(self, Box, name)

  File "C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE\mforms.py", line 34, in _swig_getattr

    raise AttributeError,name

AttributeError: last_is_running_check

Hope this helps!

I may be getting the same problem in 5.5.8 running under OSX.  "Error in dump module: error calling WbAdmin.openExportImport: see output for details". Output in turn says

Traceback (most recent call last):
  File "/Applications/MySQL Tools/MySQLWorkbench.app/Contents/PlugIns/wb_admin_grt.py", line 305, in openExportImport
    tab.wait_server_check(4)
  File "/Applications/MySQL Tools/MySQLWorkbench.app/Contents/PlugIns/wb_admin_grt.py", line 133, in wait_server_check
    while self.configuration.last_is_running_check is None and time.time() - t < timeout:
  File "/Applications/MySQL Tools/MySQLWorkbench.app/Contents/Resources/libraries/mforms.py", line 665, in <lambda>
    __getattr__ = lambda self, name: _swig_getattr(self, Box, name)
  File "/Applications/MySQL Tools/MySQLWorkbench.app/Contents/Resources/libraries/mforms.py", line 34, in _swig_getattr
    raise AttributeError,name
AttributeError: last_is_running_check
12:18:44 Restoring /Volumes/monkeybrigade/Documents/msdbdevelDump.sql

Running: /Applications/MySQL Tools/MySQLWorkbench.app/Contents/Resources/mysql --defaults-extra-file="/var/folders/ef/efF6AhfmEC816htnKky5OU+++TI/-Tmp-/tmpvYWkRB/extraparams"   --host=127.0.0.1 --user=root --port=3306 --default-character-set=utf8 --comments < "/Volumes/monkeybrigade/Documents/msdbdevelDump.sql"

Fixed as of 5.2.36:
+        <guimenu>Server Administration</guimenu>, <guimenu>Manage
+        Import/Export</guimenu> would return an error about the dump
+        module.