Renaming MySQL user … .. MySQL database failed! : mysql::execute_sql_logged failed : SQL rename 'myUserName'@'localhost' to 'myNewUserName'@'localhost' 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 ''myUserName'@'localhost' to 'myNewUserName'@'localhost'' at line 1 at /usr/share/webmin/web-lib-funcs.pl line 1496.
I only wanted to rename a user as the owner had changed. Not working! All newest and updated but not working at all.
Even worse is that it actually has changed the MYSQL Username!!! to the new one but when you now - because of the error message you got - want to change back to the previous database user it says:
` Updating user and group in Logrotate configuration …
… done
Renaming MySQL user …
… MySQL user does not exist!
Changing administration group for MySQL database files …
… done`
Pretty contra-productive to make things right but giving out a wrong error message and then not being able to bring back the previous state. or?
Line one is =head1 web-lib-funcs.pl
Line 1486 - 1496 which shows only the “}” sub error { $main::no_miniserv_userdb = 1; my $msg = join("", @_); $msg =~ s/<[^>]*>//g; if (!$main::error_must_die) { print STDERR "Error: ",$msg,"\n"; } &load_theme_library(); if ($main::error_must_die) { die @_; }
(Line 1496) so what is wrong with that end bracket (syntax)
======== ADDITION after we deleted the server and wanted to recreate it with the same new username again because the virtualmin told us atht the user is NOT existing. When creating new it says in the new error message:
The following potential problems were detected with the creation of this virtual server :
A MySQL user named ana2xyz already exists - try selecting a different administration username
so what? Is it now existing or not existing - very confusing!
Operating system Ubuntu Linux 20.04 Webmin version 1.942 Usermin version 1.791 Virtualmin version 6.09 Authentic theme version 19.47
Time on systemSaturday, May 23, 2020 12:02 AMKernel and CPU Linux 5.4.0-31-generic on x86_64 Processor information Intel® Core™ i7-7700 CPU @ 3.60GHz, 8 cores
Running processes
0
CPU load averages
2.73 (1 min) 1.98 (5 mins) 1.53 (15 mins)
Real memory
10.29 GiB used / 6.42 GiB cached / 62.6 GiB total
Virtual memory
0 bytes used / 31.99 GiB total
Local disk space
260.45 GiB used / 3.29 TiB free / 3.54 TiB total
Package updates
All installed packages are up to date
Apache version 2.4.41
MariaDB version 10.5.3
php7.4.5
The problem was already existing in 18.04 Ubuntu + MariaDB10 but previous versions
The Processes and Virtual Memory Count is also a problem as that part is completely missing as in Ubuntu 20.04 they changed the path I think which leads to the monitoring program.
the move of the database is working now I changed several servers from a subserver position to a main server position - works fine
BUT
Changing a user name of a main server or subserver user is still not working Renaming MySQL user .. .. MySQL database failed! : mysql::execute_sql_logged failed : SQL rename 'muniberg'@'localhost' to 'mun2ch'@'localhost' 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 ''muniberg'@'localhost' to 'mun2ch'@'localhost'' at line 1 at /usr/share/webmin/web-lib-funcs.pl line 1496.
after you have moved a server to the main server position.
It deleted the database but the message is pretty confusing!
Even databases are assigned they can’t get deleted when the server gets deleted
`Delete Server
In domain bec2one
Deleting mail aliases …
… done
Deleting MySQL database bec2one …
… MySQL database failed! : mysql::execute_sql_logged failed : SQL revoke all privileges on bec2one.* from ‘bec2one’@’%’ failed : There is no such grant defined for user ‘bec2one’ on host ‘%’ at /usr/share/webmin/web-lib-funcs.pl line 1496.
is also not working - it seems there is much more which needs to be changed
Here is another conflict - keep it for the record so it can be fixed - As more and more people are using MariaDB it would really be recommended to integrate and give much more love to MariaDB and keeping things running with updated versions is also more and more common since we have stuff in clouds.
That is what I understood Joe but we simply can’t improving only because a version has a new feature or a new alter syntax.
The point is that new customers want to start with new hardware and with new software and not on software which is already 2 years old from its last release date, so somehow we need to keep up to date also to avoid problems which were existing before PHP 5.2 - you might remember. Hosters did not upgrade! - Times have changed and especially in the cloud you do good to keep your stuff updated.
10.4 is the stable release and 10.5 has already its release candidate and coming soon (Probably in mid June) with further speed improvements.
I know that ALTER changed in 10.4 but that is the case already since 26 June 2019.
