MySQL Bugs: #58388: Workbench Data Dump tries to dump wrong server

Bug #58388	Workbench Data Dump tries to dump wrong server
Submitted:	22 Nov 2010 15:47	Modified:	25 Apr 2011 17:03
Reporter:	[ name withheld ]	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench: Administration	Severity:	S2 (Serious)
Version:	5.2.30, 5.2.31	OS:	Windows (Win7 64bit)
Assigned to:		CPU Architecture:	Any
Tags:	datadump, Instance, server, workbench

Description:
Workbench seems confused when doing a data dump. I have 3 server instances set up under Server Administration and when I try to do a data dump backup (self contained file), it completes instantly and with 0kb dump file. It doesn't even create a directory using the dump project folder option. I see in the log that it is trying to do a dump on a database in another server instance. When I try to do a data dump for the other server instance, it is apparently trying to do a dump on a database in the first instance. Workbench is confused between my servers apparently. I also saw that it's trying to dump the database as a table.

I had been doing dumps fine but I think this started happening after I added the last server instance. When I try to do a dump, the correct databases are showing up on the left pane, but no tables show up in the right pane. I also notice that the server health graphs at the top have no data but I'm not using SSH.

I was originally on 5.2.29 and I updated to 5.2.30. At first it seemed this fixed the problem for one server instance. The other one still was incorrect. Then I went back to the first and it had the same problem again and have had it ever since.

I have to use the MySQL Admin to do backups.

---
Log snippet1 - from 5.2.30:
(Note: the database "foo" is on a completely different server from database "bar".)

I try to dump database "bar" from server 1.

09:10:52 Dumping foo (tablea, tableb, tablec.....)
Error executing task u'foo'
09:10:52 Export of E:\Coding\bar\backups\bar_backup_20101122 0910 has finished

---
Log snippet2 - from 5.2.29:
(Note: it's also trying to dump the database as a table for some reason)

I try to dump database "foo" from server 2.

09:08:16 Dumping foo (tablea, tableb, tablec.....)
Running: "mysqldump.exe" --defaults-extra-file="c:\users\michael\appdata\local\temp\tmpoqn5ko" --no-create-info=FALSE --order-by-primary=FALSE --force=FALSE --no-data=FALSE --tz-utc=TRUE --flush-privileges=FALSE --compress=FALSE --replace=FALSE --host=192.168.0.500 foo --insert-ignore=FALSE --extended-insert=TRUE --user=michael.blah --quote-names=TRUE --hex-blob=FALSE --complete-insert=FALSE --add-locks=TRUE --port=3306 --disable-keys=TRUE --delayed-insert=FALSE --create-options=TRUE --delete-master-logs=FALSE --comments=TRUE --default-character-set=utf8 --max_allowed_packet=1G --flush-logs=FALSE --dump-date=TRUE --lock-tables=TRUE --allow-keywords=FALSE --events=FALSE "foo" "tablea" "tableb" "tablec" "tabled"
mysqldump: Couldn't find table: "foo"

Operation failed with exitcode 6
09:08:16 Dumping bar (table1, table2, table3.....)
Error executing task u'bar'
09:08:16 Export of E:\Coding\foo\backups\foo backup 20101122 0908 has finished with 1 errors

How to repeat:
Do Data Dumps

Suggested fix:
I'm using MySQL Admin for now. I have no idea how to fix this. I might try redoing all my server instances though.

Could you please try version 5.2.31. Thanks in advance.

Ok, I went on Admin for localhost server instance. My data dump worked fine there, it didn't get confused and didn't try to dump a database as a table. I had server health graphs working. I did get an error when going to the Configuration tab... when I clicked that tab it said - IOError: [Errno 22] invalid mode ("r") or filename: u"

Then I went to Admin for another server and things got very very slow. It would take several seconds for the tab to change when I clicked a different tab and I have a really fast computer at work (i7, 8GB, SSD). The graphs paused for 6 seconds periodically too. Clicking on the Variables tab then ended up causing Workbench to die. "MySQL Workbench has stopped working - A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available."

Then I went back and tried to go straight to the data dump first and try that. It was halting and pausing like before and it was hard just typing in a name for the data dump file. When I clicked Export, then put in my password, Workbench died again.

The third time I tried I was able to finish the export and everything seemed to do ok there. I exported the db on the remote server, then the local server, then back to the remote server and then Workbench died when trying that one.

Something is definitely not right there, but maybe the data dump problem I had is fixed. There should be a bug opened for this if there isn't already. I'd like to test the data dumps more if I could.

That was on the new 5.2.31 by the way.

Also, the 5.2.31 msi installer I got from "Hoobly Classifieds / Chicago, IL" did not work!!  Geez.  I tried downloading twice too.  Had immediate error upon running: "This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package."  "Argonne National Laboratory / Chicago, IL" one worked however.

Just tried again since I've been able to do other things ok, and Workbench died.
"MySQL Workbench has encountered a problem
Attempted to read or write protected memory. This is often an indication that other memory is corrupt."

May you please install the newest version of the WB?, try to reproduce
the error and if you can, get the screenshot of the error and include
it on the report, besides that please right-click on the error message
to get a popup menu with the menu item "copy stack to clipboard" and
also include the stacktrace on the report.

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