I found another potential issue with Cloudmin (Physical Server) with replication and MySQL.
I have cweb1 (primary, and cweb2 setup. They both work with LDAP-stored users that virtualmin handles management of when creating virtual-servers.
My problem right now is with replication and MySQL. As per documentation here:
I setup MySQL to be on a remote host (and that host gets replicated to a secondary database server).
With my replication options set to:
Virtualmin global settings to replicate: Module Configuration, FTP Directory Restrictions, Server Templates and Plans, Custom fields, links and shells (all other options turned off)
Virtualmin features to replicate: Virtual server configuration, Bind DNS Domain, Apache Website, SSL Website, Webmin login. (all other features turned off)
Note that MySQL Database is not turned on in the replicate features, but the problem is the following:
Failed to restore on cweb2.omitted : Checking for missing features .. .. all features in backup are supported Starting restore.. Extracting backup archive files .. .. done Re-creating virtual server domain1 .. .. a clash was detected : A MySQL database named omitted already exists Restoring Virtualmin settings (Module configuration, Server templates and plans, Custom fields, links and shells, FTP directory restrictions) .. .. done Applying FTP server configuration .. .. done Restore failed!
As-in: It's trying to re-create the mysql database on the secondary node, even though that "feature" is specifically not included?
My setup is very similar to how the documentation is from the before-mentioned website on setting up MySQL on a Remote host. The differences are:
On cweb1's Virtualmin -> Server Templates -> Default Settings -> MySQL Database -> Allowed MySQL client hosts: Includes the IP address of cweb1 and cweb2 specifically, space-separated. (seems while this is setup, when creating the initial mysql user, it creates a user with cweb1's FQDN, along with the two IP addressed defined here).