MySQL Bugs: #50184: dump fails with exitcode 7

Bug #50184	dump fails with exitcode 7
Submitted:	8 Jan 2010 11:52	Modified:	29 Jan 2010 13:50
Reporter:	Susanne Ebrecht	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S2 (Serious)
Version:	5.2.14	OS:	Linux (Ubuntu 9.04, 64 bit)
Assigned to:	Alexander Musienko	CPU Architecture:	Any

Description:
DROP DATABASE IF EXISTS foobar;
CREATE DATABASE foobar;
USE foobar;

CREATE TABLE t(i serial, j integer, k integer);

INSERT INTO t(j,k) VALUES(RAND()*100, RAND()*1000);
INSERT INTO t(j,k) SELECT RAND()*100, RAND()*1000 FROM t;
INSERT INTO t(j,k) SELECT RAND()*100, RAND()*1000 FROM t;
INSERT INTO t(j,k) SELECT RAND()*100, RAND()*1000 FROM t;
INSERT INTO t(j,k) SELECT k,j FROM t;
INSERT INTO t(j,k) SELECT k,j FROM t;
INSERT INTO t(j,k) SELECT k,j FROM t;
INSERT INTO t(j,k) SELECT RAND()*100, RAND()*1000 FROM t;
INSERT INTO t(j,k) SELECT RAND()*100, RAND()*1000 FROM t;
INSERT INTO t(j,k) SELECT RAND()*100, RAND()*1000 FROM t;
INSERT INTO t(j,k) SELECT k,j FROM t;
INSERT INTO t(j,k) SELECT k,j FROM t;
INSERT INTO t(j,k) SELECT k,j FROM t;
INSERT INTO t(j,k) SELECT RAND()*100, RAND()*1000 FROM t;
INSERT INTO t(j,k) SELECT RAND()*100, RAND()*1000 FROM t;
INSERT INTO t(j,k) SELECT RAND()*100, RAND()*1000 FROM t;

- Open Workbench
- double click connection
- data dump
- select schema foobar and table t
- press start export

12:43:02 Dumping foobar (t )
Running: mysqldump --no-create-info=FALSE --order-by-primary=FALSE --force=FALSE --no-data=FALSE --tz-utc=TRUE --flush-privileges=FALSE --compress=FALSE --replace=FALSE --host=127.0.0.1 --insert-ignore=FALSE --extended-insert=TRUE --user=miracee --quote-names=TRUE --hex-blob=FALSE --complete-insert=FALSE --password=xxxxxxx --port=6951 --disable-keys=TRUE --delayed-insert=FALSE --delete-master-logs=FALSE --routines=FALSE --comments=TRUE --add-locks=TRUE --flush-logs=FALSE --dump-date=TRUE --allow-keywords=FALSE --create-options=TRUE --events=FALSE foobar t 
Operation failed with exitcode 7

12:43:02 Export of /home/miracee/dumps has finished

I think it is related to this here:

mysqldump --user=miracee --password=xxxxxxx

Why password = xxxxxxx ? I used blanc pw.

How to repeat:
See above

Suggested fix:
...

Still not working but I figured out why ....

Workbench not use correct path for mysqldump.

On my system:

$ mysqldump => command not found

$ PATH/bin/mysqldump is working fine

I am not sure for which mysql_config is needed. I thought it will be given here already, where to find mysqldump.

Anyway, my suggestion is that you will ask for client execution path during connection configuration.

Path to mysql and mysqldump is configured in Edit->Preferences->MySQL
Although check for mysqldump existence will be added to make clear what is going wrong.

If mysql or mysqldump executables are not found, error will be output to the log.

fix confirmed. will be included in 5.2.15

An entry has been added to the 5.2.15 changelog:

When performing a data dump in the Administrator, the operation failed with an exit code 7.

MySQL Workbench has been changed so that it will generate an error if the mysqldump executable cannot be found.