Bug #50137 Cryptic results from mysqldump on export

• Submitted: 7 Jan 2010 12:29
• Modified: 16 Feb 2010 13:39
• Reporter: Martin Eve
• Status: Closed
• Category: MySQL Workbench
• Severity: S3 (Non-critical)
• Version: 5.2.11 Beta 3
• OS: Linux (Arch)
• Assigned to: Alfredo Kojima
• CPU Architecture: Any
• Tags: workbench

[7 Jan 2010 12:29] Martin Eve

Description:
The output when mysqldump fails is cryptic and unhelpful in diagnosing problems.

Expected result: a detailed message explaining why mysqldump failed.

Actual result: "Operation failed with exitcode 2"

How to repeat:
Perform an operation that will fail (for any reason) on the export/dump data tab. An example could be an unsupported server version or insufficient privileges.

Suggested fix:
Read stdout of mysqldump and append to log.

[7 Jan 2010 13:30] Michael G. Zinner

I move this bug up in priority since it is almost impossible to find out what went wrong when something does indeed go wrong.

Alex, please add the mysqldump output to the log ASAP. Thanks.

[8 Jan 2010 11:58] Susanne Ebrecht

Many thanks for writing a bug report.

By accident I got exitcode 7 a few minutes ago and has had same problem.

Verified as described.

[15 Feb 2010 20:12] Alfredo Kojima

This has been fixed around 5.2.13

[15 Feb 2010 21:41] Johannes Taxacher

this has been fixed in release

[16 Feb 2010 13:39] Tony Bedford

An entry has been added to the 5.2.16 changelog:

The messages generated by mysqldump when a data export operation failed were difficult to interpret, for example:

Operation failed with exitcode 2