I have/had remote database connections set up using the mysql module and setting the ip address to 0.0.0.0 on the update to mysql server version 8.0.22-0ubuntu0.20.04.3 this configuaration was wiped and all connections were lost. I tried to reconfigure using the mysql module & resetting the ip address to 0.0.0.0 again, this failed for reasons unknown after saving and returning to the module the ip address was still blank and the only fix was to add the following to /etc/mysql/my.cnf bind-address = 0.0.0.0 this fixed the remote connections and also on returning to the mysql module the IP field was populated with 0.0.0.0 Is this a case of a change of mysql server configuration for this version and webmin is saving data to an incorrect file or a permissions error writing data to my.cnf ?
mysql server version 8.0.22-0ubuntu0.20.04.3
Closed (cannot reproduce)
Submitted by JamieCameron on Sun, 12/06/2020 - 01:01 Comment #1
Where in Virtualmin are you seeing or entering this 0.0.0.0 address?
I see it at servers->mysql server->mysql server configuration top right corner. I altered this to 0.0.0.0 to allow remote database connections to the server and it worked fine .. it was only on update 8.0.22-0ubuntu0.20.04.3 the config was reset to 127.0.0.1 connections then failed .. that said does webmin have a better way of setting up remote db connections rather than getting mysql to listen on 0.0.0.0 ?
Submitted by JamieCameron on Sun, 12/06/2020 - 13:54 Comment #3
Which field did you enter 0.0.0.0 into exactly?
What is the content of the following files:
MySQL module configuration has an option for that called Any, right next to where you entered 0.0.0.0.
Package manager (apt) upon upgrading MySQL package in particular, when using the console, offers a variety of options on what should be done with the current config files, and if they should be upgraded as well or left intact. The default is to keep current configs but perhaps you somehow managed to select overwrite with the latest configs, which are delivered by upgradeable package. This is the only reasonable explanation I have for this issue and why it was "reset" to the default value.