Virtualmin should include option to create default database instead of force creation

[risharde]

Hi, I encountered a potentially dangerous issue out of which I believe either a new checkbox option should be added. It’s a bit hard to explain but let me try.

1. When you create a new virtual server, one of the options is to enable Mysql/Mariadb database. This automatically creates a new user and database - that’s fine.
2. However, if you do not select this option (in my circumstance: I already have a database created with the default name as the virtual server - due to a Galera cluster), then when you try to enable the database option for the virtual server, you are warned that a database already exists - I backed out because I wasn’t sure if this would affect the current database since that would mess with my galera cluster data).
3. Without enabling this database option, there’s no way to get to the options to attach my galera database to this specific virtual server and thus backups won’t include this database which is critical.
4. Suggestion: Add an additional option for creating the default database and username, make the previous option just allow the features so a virtual server can then associate an existing database.

I hope this makes sense. BTW - This is GPL hence why I’m here on the forums.

[stefan1959]

But confused, you had a “Galera Cluster” on the server before you installed virtualmin?
Not sure many users would know how to help with this sort of setup.

You can turn off create database and login in template, then you the import to associate with domain, if that helps.

[Stegan]

I agree this is confusing me too.
If this “Galera Cluster” was already on the server before installing Virtualmin, then the 1st rule of installing Virtualmin has been broken.

Install on a clean machine.

So for all normal users this would not be a problem, which makes this suggestion irrelevant doesn’t it?