Closed wp4nuv closed 3 years ago
Hi @wp4nuv thanks for the detailed bug report.
From your docker logs I am seeing the following error message:
mysql_1 | 2020-12-28T21:35:39.596905Z 20 [Note] Access denied for user 'root'@'172.16.238.1' (using password: NO)
In the .env
file however you've setup a password for MySQL. Can you double check this on your setup
Hi @wp4nuv thanks for the detailed bug report.
From your docker logs I am seeing the following error message:
mysql_1 | 2020-12-28T21:35:39.596905Z 20 [Note] Access denied for user 'root'@'172.16.238.1' (using password: NO)
In the
.env
file however you've setup a password for MySQL. Can you double check this on your setup
I can't say for sure why that shows... it may be transient. I can run another log dump to see if its recurring P.
You did already state this in your post: It does work with MySQL Workbench >= 8.0. Just checked it (as it is the version I have installed)
I would rather assume it must be an issue with older Workbench versions, as SSL clearly seems to work. Wdyt?
That makes sense, but here’s the interesting part: I even made copies of all the generated server keys in case it was looking for those.. but the result was the same. I know I can use Workbench 8, but because our database is not 8, there’s always the possibility that a backup made with the newer Workbench won’t load properly into a 5.7 db. I agree that this seems to be more of a Workbench issue not recognizing the server SSL status. Any chance that the default behavior of generating SSL certs could be turned off?
From: cytopia notifications@github.com Sent: Thursday, December 31, 2020 06:31 To: cytopia/devilbox devilbox@noreply.github.com Cc: Pedro J Maldonado pmaldonado1@mac.com; Mention mention@noreply.github.com Subject: Re: [cytopia/devilbox] Unable to use earlier versions of MySQL Workbench in Percona 5.7 mysql (#775)
You did already state this in your post: It does work with MySQL Workbench >= 8.0. Just checked it (as it is the version I have installed)
I would rather assume it must be an issue with older Workbench versions, as SSL clearly seems to work. Wdyt?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/cytopia/devilbox/issues/775#issuecomment-752931617 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AAEMLQIUDT5HRC7FMISDTT3SXROF5ANCNFSM4VMRDCLQ . https://github.com/notifications/beacon/AAEMLQN4TZNCBLCDEPU5ITLSXROF5A5CNFSM4VMRDCL2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOFTQNGII.gif
Any chance that the default behavior of generating SSL certs could be turned off?
I am not really maintaining those images. I just use a combined repository to bring together MySQL, MariaDB and Percona and make them behave the same way (https://github.com/devilbox/docker-mysql)
See for percona 5.7 for instance: https://github.com/devilbox/docker-mysql/blob/master/Dockerfiles/percona-5.7 All it's doing is ensuring required directories are present and then use entrypoint script from percona.
So you would have more luck, looking at the original images:
Awesome, thank you! I think this can be closed. If I do come up with a way to turn it off, ok to submit a PR even though they are not maintained?
From: cytopia notifications@github.com Sent: Thursday, December 31, 2020 12:04 To: cytopia/devilbox devilbox@noreply.github.com Cc: Pedro J Maldonado pmaldonado1@mac.com; Mention mention@noreply.github.com Subject: Re: [cytopia/devilbox] Unable to use earlier versions of MySQL Workbench in Percona 5.7 mysql (#775)
Any chance that the default behavior of generating SSL certs could be turned off?
I am not really maintaining those images. I just use a combined repository to bring together MySQL, MariaDB and Percona and make them behave the same way (https://github.com/devilbox/docker-mysql)
See for percona 5.7 for instance: https://github.com/devilbox/docker-mysql/blob/master/Dockerfiles/percona-5.7 All it's doing is ensuring required directories are present and then use entrypoint script from percona.
So you would have more luck, looking at the original images:
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/cytopia/devilbox/issues/775#issuecomment-753006721 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AAEMLQJGE74XTHGYPYRKHITSXSVHJANCNFSM4VMRDCLQ . https://github.com/notifications/beacon/AAEMLQNI3HDSSQF3DLVJSXLSXSVHJA5CNFSM4VMRDCL2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOFTQ7RAI.gif
If I do come up with a way to turn it off, ok to submit a PR even though they are not maintained?
Totally, would even be much appreciated :+1:
ISSUE TYPE
Checklist
.env
file is attached./check-config.sh
output is added belowdocker-compose logs
output is added belowdocker-compose.override.yml
is attached (if exists)cfg/
dir are attached (if exist)OS / ENVIRONMENT
SUMMARY
When using Percona Mysql 5.7 its impossible to use a version of Mysql Workbench prior to 8.0 due to SSL problems even when the certficates exist:
mysql_1 | 2020-12-28T21:19:48.094984Z 0 [Note] Found ca.pem, server-cert.pem and server-key.pem in data directory. Trying to enable SSL support using them. mysql_1 | 2020-12-28T21:19:48.095527Z 0 [Note] Skipping generation of RSA key pair as key files are present in data directory.
STEPS TO REPRODUCE
Select Percona Mysql version 5.7 Install the latest Mysql Workbench 6.3 Attempt to connect to db through localhost. If the SSL default (If Required) is turned off, connection succeeds but importing a SQL file fails due to SSL errors. If the SSL value is replaced to "If Required", no connection is possible.
EXPECTED BEHAVIOUR
Connect to Devilbox Mysql instance using the correct Workbench version for mysql 5.7
ACTUAL BEHAVIOUR
User is unable to import sql files due to SSL errors. Users cannot connect to database if the default "If Required" option is active in Workbench.
OTHER INFORMATION
Start command
Outputs
output of .env:
Custom config
cfg/php-ini7.2/xdebug.ini
:Custom config
cfg/php-startup-7.2/01-apt-update.sh