hmm
sort of points out that the webmin module bails on a failed mysql server very early so from the webmin gui there is no way of re configuring from the gui, hence fixing it from the command line.
This leads to the point should the module then continue with the error in place and then display a message that mysql is not running (perhaps a config error) and allow the user to re configure the mysql server & start it.
From what I remember this effected Ubuntu < 22.04 which has an earlier version of mariadb installed and if mariadb is upgraded from mariaās repro to the latest version rather than from Ubuntuās repro everything works fine so I guess this problem maybe unique to this distro . Perhaps the logic within the mysql should be altered to allow the user to reconfigure ? That said there is the possibility that the end user might not understand the error or have any idea on how to fix it, so perhaps the module could have a go at fixing the error, from reading the log for the said mysql server and the restarting it on a fix.
That said as it seems to apply to a version of mariadb perhaps itās not worth the effort.
1 Like
Oh, you may be right! Thatās a buglike. We shouldnāt prevent editing the config file just because the service isnāt running. Iāll look into it.
This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.