mariadb/mysql no access

Submitted by shadowtor on Thu, 02/21/2019 - 06:03 Pro Licensee

MySQL database failed! : mysql::execute_sql_logged failed : SQL alter user '*****'@'localhost' identified by '********' failed : You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'user '******'@'localhost' identified by '*******'' at line 1 at /usr/share/webmin/web-lib-funcs.pl line 1478

Blanked details, but noticed with most recent update of webmin, Mariadb/mysql database is refusing usermin to add domains and users to databases. Was working before update ~1 week ago, updated yesterday and completely broken. If you want more logs let me know thanks!

Status: 
Closed (fixed)

Comments

Submitted by andreychek on Thu, 02/21/2019 - 08:50

Howdy -- we've seen some similar issues recently when using database versions that are newer than what is provided by the distro.

Jamie has been working on fixes for those. However, just to verify -- are you using MySQL, or MariaDB there?

And what database version is it that's in use there?

Thanks!

Submitted by ralmendros on Thu, 02/21/2019 - 10:50

Hi everyone,

I have some similar problem. I have not read this issue and I have created another one. Sorry about that.

On my case Is a Debian 9.6 with Virtualmin v6.0.6 Usermin v1.751, Webmin v1.900. MariaDB installed with the Virtualmin package and running at the same machine. The MariaDB version is v10.1.37

I have executed mysqlcheck and all the databases are giving me OK.

The last week everything worked fine, but have been two updates during this week.

Thanks!!!

Submitted by shadowtor on Thu, 02/21/2019 - 15:46 Pro Licensee

Hi Andreychek Thanks for the quick reply, this is running debian minimal (fresh install) and no extra repos added (so is apart of distro) Debian seems to install both and unsure if webmin/usermin defaults to sql or Maria. Based on errors it Looks like it's referencing maria

Submitted by andreychek on Thu, 02/21/2019 - 19:44

Hmm, that's an odd one! I wonder if Debian has changed what the default is now.

What is the output of these two commands:

dpkg -l 'mysql*'
dpkg -l 'mariadb*'

I meant to include this link above, but there's an existing bug report here about the MariaDB 10.1 issue, where Jamie has been looking into this. It includes a patch to hopefully resolve it:

https://www.virtualmin.com/node/64702

If MariaDB 10.1 is being installed by default now, it looks like we may need to hurry up and get that patch out into a stable release.

Submitted by shadowtor on Thu, 02/21/2019 - 19:48 Pro Licensee

Sorry running off phone currently, but as below: root@v1:~# dpkg -l 'mysql*' Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==============-============-============-================================== ii mysql-client 5.5.9999+def amd64 MySQL database client binaries [tr un mysql-client-5 (no description available) un mysql-client-5 (no description available) un mysql-client-5 (no description available) un mysql-client-c (no description available) un mysql-client-c (no description available) un mysql-client-c (no description available) ii mysql-common 5.8+1.0.2 all MySQL database common files, e.g. un mysql-common-5 (no description available) ii mysql-server 5.5.9999+def amd64 MySQL database server binaries and un mysql-server-5 (no description available) un mysql-server-5 (no description available) un mysql-server-5 (no description available) un mysql-server-c (no description available) un mysql-server-c (no description available) un mysql-server-c (no description available)

root@v1:~# dpkg -l 'mariadb*' Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==============-============-============-================================== un mariadb-client (no description available) ii mariadb-client 10.1.37-0+de amd64 MariaDB database client binaries un mariadb-client (no description available) un mariadb-client (no description available) ii mariadb-client 10.1.37-0+de amd64 MariaDB database core client binar un mariadb-client (no description available) ii mariadb-common 10.1.37-0+de all MariaDB common metapackage un mariadb-galera (no description available) un mariadb-galera (no description available) un mariadb-galera (no description available) un mariadb-server (no description available) ii mariadb-server 10.1.37-0+de amd64 MariaDB database server binaries un mariadb-server (no description available) un mariadb-server (no description available) ii mariadb-server 10.1.37-0+de amd64 MariaDB database core server files un mariadb-server (no description available) un mariadb-test (no description available) un mariadb-tokudb (no description available) un mariadb-tokudb (no description available) un mariadb-tokudb (no description available)

Ah sorry about creating a new ticket/issue then! Guess I didn't look close enough through the others.

Any other info you require, let me know so we can get it up and running again, I'll have a look at the patching added on the other ticket. Thanks!

Submitted by shadowtor on Thu, 02/21/2019 - 19:49 Pro Licensee

Also sorry about the formatting, again running off my phone :p

Submitted by shadowtor on Thu, 02/21/2019 - 22:28 Pro Licensee

No worries, thanks for letting me know Any eta on update? (Otherwise where does this patch need to be adjusted as I wasn't able to find it listed for virtualmin pro. Thanks!

Submitted by JamieCameron on Fri, 02/22/2019 - 00:40

Should be out in a couple of days.

Submitted by shadowtor on Sun, 03/10/2019 - 22:39 Pro Licensee

Fixed in recent updates for virtualmin/webmin

Submitted by IssueBot on Sun, 03/24/2019 - 22:42

Status: Fixed ยป Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.