-
Notifications
You must be signed in to change notification settings - Fork 602
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MariaDB version 10.4.11 error MySQL Database Server/Create User and HOME folder #1183
Comments
Full support for MariaDB 10.4+ and MySQL 8+ has been implemented in Webmin 1.960 and Virtualmin 6.13. Restore MySQL has also been fixed. |
MariaDB 11 deprecated all Also, I don't see any practical reasons in upgrading to MariaDB 11 in production environment. |
Thanks a lot @iliajie for your fast response. So you suggest to downgrade to mariadb v10.5? You think is this safe to try it now? |
I wouldn't use it in production. There is no point, just let it bake. Downgrade .. ? I wouldn't do downgrades from a newer version to an older. If you don't have any data used in MariaDB, simply use Also, I personally use Debian 12 on one of my machines, and see no reason to use Debian 11 nowadays. |
Thanks a lot for the recommendation @iliajie. It was an old machine with Debian 9 and MySQL low version. I need a specific version of MariaDB for a Magento 2 and that's why I switched to. Everything went smoothly. I will now try to upgrade to Debian 12 and then try to purge and reinstall mysql. Can you suggest me the best version to use? Mysql or Mariadb with debian 12 and virtualmin? And whitch specific version for production? |
I'd used MariaDB. Also, I wouldn't distro-upgrade. It's much cleaner and simpler to just install Debian 12 and migrate. |
Error message:
Failed to save user : SQL insert into user (host, user, Select_priv, Insert_priv, Update_priv, Delete_priv, Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv, File_priv, Grant_priv, References_priv, Index_priv, Alter_priv, Show_db_priv, Super_priv, Create_tmp_table_priv, Lock_tables_priv, Execute_priv, Repl_slave_priv, Repl_client_priv, Create_view_priv, Show_view_priv, Create_routine_priv, Alter_routine_priv, Create_user_priv, Event_priv, Trigger_priv, Create_tablespace_priv, Delete_history_priv, ssl_type, ssl_cipher, x509_issuer, x509_subject, authentication_string) values (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) failed : The target table user of the INSERT is not insertable-into
It is impossible to create a new database user via
When creating a new Virtual Server and activating MySQL in Virtualmin, the Database user gets created
Besides that, creating a new Virtualmin Server 'ab-c.123' results in a Virtualmin user/group/folder like 'ab-c' and not 'ab-c.123' and a Database user 'ab-c'
When trying to apply changes it gives a correct warning:
WARNING: This MySQL user (ab_c) is the administration login for Virtualmin domain ab-c.123. Changing any settings here may cause errors in Virtualmin.
BUT problem occurs as in the old server the folder in home was called 'ab-c.123' and now only a user/group/folder 'ab-c' gets created.
EVEN a message when creating a username with a sign not allowed states that DOTs are allowed:
Failed to create virtual server : Missing or invalid domain name - only letters, numbers and the dot, dash and underscore characters are allowed
ADDITION: just realized that the underscore also doesn't get accepted in a username! Only the Hypen is OK!
When importing a sub-server now to this newly created Virtualmin/Webmin User the sub-server Database gets created the sub-server can't get imported because of those differences in the user/group-name and home folder name.
BUT when importing (backup locally uploaded and then Restore Backup) a Virtual-Server from another Webmin installation which runs MySQL version 10.1.43-MariaDB-0ubuntu0.18.04.1 to the new Ubuntu 18.04.1 server with MariaDB version 10.4.11 in no user creation and when importing a subserver with Database to that virtualmin user it results in an empty database but all server content gets created.
AND when now importing the same sub-server like above an empty database gets created and all content gets restored as the folder ab-c.123 got created.
If the Virtualmin User has no DOT or other non-alphabetical or non-numerical letter in its name the output is:
As a work-around for importing servers you can at least import the content like this, but then would need to move everything to another user and importing the database manually to this specific new user. - Unfortunately, there seems to be no way to import a sub-server to a newly created user and into a newly created home directory of that user.
i.e moving the sub-server abc.tld from its main server 'ab-c.123' to a newly created main server 'ab-c'
When you change the Domain Name of the main server - which would be another option to get rid of the DOT - another problem occurs when then afterward trying to activate the MySQL Database
This happens even the Domain name was changed from 'ab-c.123' to 'abc' before! It still tries to create the user 'ab-c.123' which of course results again in failure. So only a manual MOVE of the folder which might contain content you need would be a work-around until those problems get fixed.
In all cases deleting the virtual server results in:
which is correct.
But when deleting the restored sub-server which got restored in the restored main-server the empty database gets NOT deleted and therefore it might cause problems when recreating a server as this database already exists.
I suggest issuing at least a warning for Webmin/Virtualmin users/admin that a username can NOT contain any DOTs or other non-alphabetical or nom-numerical letters/signs to avoid problems with the database user and home folder creation.
After the import the permissions for the database user have to be set/created manually
https://.../mysql/list_dbs.cgi?xnavigation=1
They don't get created by the database creation or changed by a move
Work around:
and change/create the database permissions - i.e. choose the database which got created automatically ...
I hope those problems get fixed soon as they are pretty blocking any workflow and automation of processes. The Virtualmin related problem with the database had been fixed already:
([https://github.com/virtualmin/virtualmin-gpl/issues/137])
The text was updated successfully, but these errors were encountered: