MySQL Bugs: #64970: Unexpected error while exporting data

Bug #64970	Unexpected error while exporting data
Submitted:	13 Apr 2012 10:57	Modified:	3 Jun 2012 17:24
Reporter:	Iván Argulo	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench: Administration	Severity:	S2 (Serious)
Version:	5.2.38, 5.2.39	OS:	Windows (Microsoft Windows 7 Ultimate Edition Service Pack 1 (build 7601), 32-bit)
Assigned to:		CPU Architecture:	Any
Tags:	WBBugReporter

Description:
Connecting to a server via SSH. Doing backup (data export). Aproximately 40 schemata, 2540 tables on them. The Workbench keeps crashing. It's pretty random, not in the same tables nor in the same schemata.

How to repeat:
Connect server via SSH. Data export. Select all schemata and all tables in them. Single file / multiple file options (it doesn't matter, fails with both options). Start export. Randomly fails...

How long since export start it takes to crash usually? I wonder is it related to some ssh/tcp/connection timeout.

It depends. Sometimes, a few seconds after export is launched (I always start a new SSH connection when exporting, not reusing an old connection).
Sometimes it fails after a few minutes. Sometimes it doesn't fail at all.

I've tried exporting 5-10 schemata at one time. Failure occures less often in that case. But sometimes it fails too, just exporting 1 schema.

Thanks a lot

Please, check error log of MySQL server. Do you have anything unusual there for the moments when you got errors during export?

Hi! Sorry for the delay. We've checked the error logs, and there aren't unusual errors (just server restarts and stuff like that). Today the Workbench crashed again. This is the only thing I've found at the Workbench log:

C:\Program Files\MySQL\MySQL Workbench 5.2 CE/python/site-packages\paramiko\client.py:93: UserWarning: Unknown ssh-rsa host key for fsezamora.es: [[here goes the key]]

  (key.get_name(), hostname, hexlify(key.get_fingerprint())))

INFO: Connection opened

WBAMonBE: Data sources were not added. Profile set to non-local or remote admin is disabled.

Please try version 5.2.39. Thanks.

Tried with 5.2.39. I was able to export tables for about 1.5 hours (more than the last version), but it crashed again (while it was exporting table number 1851 of 2450). It seemed to work fine, but at certain point it crashed. My impression is that it works smoother than the other version, but the bug is not fixed yet. Should I open a new bug report with the new version?

Something weird, maybe it's related, maybe it's not. Usually, export crashes after exporting moodle tables. Sometimes at these tables, sometimes short after exporting these tables.

Hello Iván, what kind of remote environment you are using?, can you please share the details in order to reproduce the bug?

Thanks in advance!

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".