MySQL Bugs: #102095: MySql Workbench will not recognize path to MySqlDump executable

Bug #102095	MySql Workbench will not recognize path to MySqlDump executable
Submitted:	30 Dec 2020 22:34	Modified:	31 Dec 2020 16:07
Reporter:	Ian Sliney	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	All	OS:	MacOS (Big Sur)
Assigned to:		CPU Architecture:	x86 (3ghz 6 core i5 32GB ram)

Description:
Dear MySql bug fixers,

I have a massive (200 million+ records) database stored in MySql 8.0.022 on a 2017 MacBookPro which I have just spent over a week processing and analyzing for eventual upload to an AWS Production server.

I have tried to get MySql Workbench to dump the database to an external SSD so it can be transported to AWS, but I keep getting the message "Could not get mysqldump version" even when in Workbench preferences I provide the Path to mysqldump Tool.

For some inexplicable reason, every version of Workbench that I install simply fails to connect to the mysqldump executable that is stored in /usr/local/mysql-8.0.22-macos10.15-x86_64/bin.

The Workbench export function works just fine on two other MySql installations on a 2018 MacMini and a 2013 MacBook Pro, but on the 2017 MacBook it is a dud.

I have scoured all the threads for almost a week, tried all the proposed solutions that have been proposed, and it just will not work.

The unix executable file mysqldump is present and correct and dated September 24, 2020 at 5:44pm

About 60Gb of precious data is currently trapped on my 2017 MacBook, and I need to make a backup so I can get it onto and AWS server but I am totally stumped.

I'm completely self taught with MySql, and I find it incredibly dense and hard to understand. I've tried to get mysqldump to work using MacOs terminal command line instructions, but it is a complete nightmare - I'm totally out of my depth.

My IT startup needs to get the data onto the AWS server or we risk going belly up........

Can anyone please help me out and fix this?

Thanks.

Ian Sliney,
Founder & CEO Twisty Systems LLC
www.twistysystems.com

How to repeat:
Please call me up and lets use Zoom or any other screen sharing application so you can see what happens.

Suggested fix:
I have no idea....

mysqldump --version gives the same as WorkBench installed?. Thanks.

HI there,

I finally found a solution in the middle of last night.

Following a thread I found online, I Installed workbench 8.0.12

Then I tried the following suggestion:
 
[7 May 2019 2:28] deke zhang 
The problem is caused by the my.cnf ,   use the fellow command to fix the problem. 
 
Sudo chmod 644 /etc/my.cnf
 
After executing this command in the MacOs Terminal, Workbench was able to connect to MySqlDump, and began to work correctly, and I was able to create the dump files and get them off the MacBook, so that's was a great relief.

However Workbench can no longer purge binary logs, so the computer is eventually going to run out of disk space and MySql will crash.

This seems like a bug that also needs a fix.

Thank you for the feedback. I couldn't repeat with WorkBench 8.0.22.