MySQL Bugs: #91079: Workbench unable to get mysqldump version

Bug #91079	Workbench unable to get mysqldump version
Submitted:	30 May 2018 15:20	Modified:	28 Aug 2018 3:52
Reporter:	Kevin Martin	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench: Administration	Severity:	S3 (Non-critical)
Version:	6.3 CE	OS:	Windows (10)
Assigned to:		CPU Architecture:	x86
Tags:	mysqldump, mysqlworkbench

Description:
This bug was previously reported by another user in Sep, 2017 (Bug #87785) with MySQL 5.7 and Workbench 6.3.9.  The previous Oracle tech claimed that the problem couldn't be repeated/duplicated, yet the originator, and others who have commented since, provided proof that it can be repeated.

I have encountered the same error since recently upgrading from MySQL 5.7 to MySQL 8.0.  I wanted to use the newest version of mysqldump, especially to be rid of the warning message that the current version of mysqldump (from 5.7) didn't match the current version of MySQL itself (8.0.11).  So, I, too, added the path to the 8.0.11 version (C:\Program Files\MySQL\MySQL Server 8.0\bin) and now instead of a pesky warning message, I can't even execute mysqldump and get the exact same message as reported in bug 87785:  "Workbench unable to get mysqldump version.  Please verify the log file for more information."

Please do not try to claim that this error can't be repeated, thus implying it doesn't exist, and fix the dang problem!  This has been ongoing now for nine months.

How to repeat:
-Upgrade MySQL Community Edition 5.7.9 to MySQL Community Edition 8.0.11
-Upgrade MySQL Workbench to v6.3 CE
-In Workbench\Preferences\Administration change 'Path to mysqldump Tool' to "C:\Program Files\MySQL\MySQL Server 8.0\bin"
-Attempt mysqldump of any schema

Note:  Changing the path ALWAYS creates this error!

Please check the mysqldump version you have on WorkBench install directory:

C:\Program Files\MySQL\MySQL Workbench 6.3 CE>mysqldump.exe --version
mysqldump  Ver 10.13 Distrib 5.7.17, for Win64 (x86_64)

C:\Program Files\MySQL\MySQL Workbench 6.3 CE>

Are you tried to upgrade WorkBench for development releaxes rc 8.0.11?.

Thanks.

Current working mysqldump:
C:\Program Files\MySQL\MySQL Workbench 6.3 CE>mysqldump.exe --version
mysqldump  Ver 10.13 Distrib 5.7.17, for Win64 (x86_64)

New version that Workbench refuses to use:
C:\Program Files\MySQL\MySQL Server 8.0\bin>mysqldump.exe --version
mysqldump  Ver 8.0.11 for Win64 on x86_64 (MySQL Community Server - GPL)

I am using the most recent version of MySQL Workbench, 6.3 CE, that is bundled with the Community edition installer.  The installer installs nothing other than this version of Workbench.

Hello  Kevin Martin,

Thank you for the bug report.
This is most likely duplicate of Bug #87785, please see Bug #87785

Please try the Development Release 8.0.11 rc. 
https://dev.mysql.com/downloads/workbench/

Thanks,
Chiranjeevi.

Screenshot

Attachment: Bug_91079.PNG (image/png, text), 51.73 KiB.

Chiranjeevi,

No offense, but please read my original post carefully and in its entirety.  If you do, you will see that I specifically referenced but #87785 in my bug report.  I also stated that it had been opened in 9/2017 and closed with only a statement that the tech couldn’t reproduce the error, in spite of the original reporter’s evidence and continued comments to the contrary.  In fact, it is you who indiscriminately closed the original without actually doing anything to address it.

I also very specifically asked that, since this issue continues, it be given a more thorough investigation, to not just pass this off as “not repeatable” and actually do something to get the problem fixed.

While this is a “duplicate” in the sense that someone else reported the issue previously, it certainly is not resolved.  Please act on my request and, again, not by stating that you are unable to reproduce the error, as myself and other users can reproduce it at will.

If you feel that you are unable to continue the investigation, please pass it to the next level of the company’s “bug fix” technical team and/or provide the contact information for a manager in your area so that the issue can be escalated.

Thanks!

Thank you for the feedback. I will try to repeat this issue, but first clarify: which exactly version of Workbench you are using 6.3.10? and how you did the upgrade from 5.7.9 to 8.0.11. Thanks in advance.

Full Workbench version is 6.3.10.  Upgrade to Server 8.0.11 was done by uninstalling 5.7.9 and installing 8.0.11 using the CE Installer.  Unfortunately, the installer doesn't seem to recognize any version of Workbench beyond 6.3.10; i.e., couldn't get RC 8.0.11 of it, even if I wanted it, which I don't.  I don't like working with beta software in my environment.  Thanks!

I had a similar problem, same version of Workbench, MySql Server version 8.0.1. Workbench log message was: 'Could not parse version number from C:\Program Files\MySQL\MySQL Server 8.0\bin\mysqldump.exe'

MySql reported version number was something like '8.0.1-dmr-log'. Looking at Workbench Python script in 'C:\Program Files\MySQL\MySQL Workbench 6.3 CE\modules\wb_admin_import.py', you'll find in line 114 the version number string checked: 

'...match(".*Distrib ([\d.a-z]+).*", output)'

I know nothing of Python, but I believe this doesn't match the reported version string. So I hard coded the version number by adding a line 'output = ".Distrib 8.0.1"'. Then deleted 'C:\Program Files\MySQL\MySQL Workbench 6.3 CE\modules\wb_admin_import.pyc' and restarted the workbench. After that, the export took place without problems.

Perhaps this gives a clue to a solution for your problem. And of course, you could also try to run mysqldump directly from the command line.

I found a cause of this issue on my system (Ubuntu 16.10), not sure if it will be the same for others. Trying to run `mysqldump -V` in terminal gave an error:

    mysqldump: [ERROR] unknown variable 'database=pinprs_inputs'

That database parameter is a setting in my `.my.cnf` file. I removed that line from the file, and `mysqldump -V` now works as expected. Likewise, going back into MySQL Workbench, the export function now works.

This seems like a bug in `mysqldump` as opposed to within Workbench.

Please try version 8.0.12. Thanks.

https://dev.mysql.com/downloads/workbench/

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

Having this error with workbench 6.3.10, on OS-X.

Upgraded to version 8.0.2 -- exact same error as with 6.3.10 - both on osx. my mysql servers are deployed on ubuntu in docker on AWS instances and everything worked fine for the last 12 months. I think I will try older version of workbench, not newer...

Same error on Workbench 8.0.12

I had this issue too and turns out due to previously having Ansicon installed, deleted Ansicon files but didn't uninstall it properly. This cause cmd console to return an extra line saying "The system cannot find the path specified." which broke workbench's python script trying to get version string of mysqldump. Uninstalling Ansicon properly fixed this issue for me.

The problem is caused by the my.cnf ,   use the fellow command to fix the problem.  

chmod 644 /etc/my.cnf

Hello.

I still tried to solve this issue.

MySQL Workbench CE (GPL) 6.3.8 CE build 1228
MySQL  Ver 8.0.28 for Linux on x86_64 (MySQL Community Server - GPL)

I tried everything no success so far.

Any suggestion would be very helpful. 

Thanks