Virtualmin Replication in Cloudmin 8.4 Pro (with Virtualmin 5.0 GPL and Webmin 1.782 GPL) has trouble recognizing when domains have been deleted. From an e-mail notification I received this morning:
Creating temporary directories .. .. done
Backing up 104 virtual servers on source system .. .. backup failed : Virtual server somedomain.com does not exist
In this particular case, somedomain.com was removed from Worker1, and replication to Worker2 should have simply deleted the offending domain, as the "Delete domains no longer on source" box was checked. Somedomain.com still shows up in the "Virtual Domains to Replicate" list (on the right) though, which is a bit strange, as that list doesn't appear to update properly. When I move it to the exception list on the left, it disappears. Also, we've been having some trouble with simply checking "All on source system" and expecting it to work, and we've got about a dozen domains that end up in the exception list (on the left), or replication fails for various reasons. This is out of a list of a whopping 120 domains, and I'd be scared of what would happen (or how much time I'd be dedicating to fixing replication every day) if we had thousands of domains, and domains were constantly being added and deleted.
Submitted by internetlightspeed on Tue, 01/19/2016 - 11:06 Comment #1
Submitted by JamieCameron on Tue, 01/19/2016 - 21:43 Comment #2
Ok, it looks like the bug here is that when you select specific domains to sync, those that have been removed from the source system aren't automatically excluded from the list .This will be fixed in the next Cloudmin release.
Submitted by JamieCameron on Tue, 01/19/2016 - 21:43 Comment #3
Submitted by itinfra on Wed, 05/30/2018 - 14:18 Pro Licensee Comment #5
I can confirm this hasn't been fixed as I am currently experiencing the issue. Please revert with a solution.
Submitted by JamieCameron on Wed, 05/30/2018 - 21:50 Comment #6
@itinfra - which Cloudmin version are you running there?
Submitted by itinfra on Mon, 06/04/2018 - 08:12 Pro Licensee Comment #7
My cloudmin version is 9.3 Pro.
Submitted by JamieCameron on Tue, 06/05/2018 - 23:21 Comment #8
itinfra - this is definitely fixed. Are you sure you're seeing the exact same issue?
Submitted by ghost23 on Thu, 06/07/2018 - 09:45 Pro Licensee Comment #9
I can confirm this behavior. On a Debian 9 Webmin version 1.883 Usermin version 1.741 Virtualmin version 6.03 Cloudmin version 9.3 Pro
And I've ohter freaky issues with the replication.
I've 3 servers (web0 web1 web2) on web0 is cloudmin here I want to create and edit the domains ( databases are stored on a remote cluster, users goes to a remote ldap cluster and /home is a remote nfs cluster = his all works). I want web1 and web2 to act as frontend servers for www, mail, dns and so on. My plan is to replicate the domains from web0 to web1 and web2. All three are connected to ldap, mysql and nfs. When I replicate a domain (with out: Home directory, BIND DNS domain, MySQL database) I got this: Failed to restore on web1.xx.local : Checking for missing features .. .. all features in backup are supported Checking for errors in backup .. .. no errors found Starting restore.. Extracting backup archive files .. .. done Re-creating virtual server domain2.com .. .. a clash was detected : A unix user named domain2 already exists - try selecting a different administration username Restore failed!
Failed to restore on web2.xx.local : Checking for missing features .. .. all features in backup are supported Checking for errors in backup .. .. no errors found Starting restore.. Extracting backup archive files .. .. done Re-creating virtual server domain2.com .. .. a clash was detected : A unix user named domain2 already exists - try selecting a different administration username Restore failed!
So I thought - OK I don't need to have ldap on the targets for virtualmin ( I want to use it for other applikations i.e. a user can log in a quarantain or something ). I deploy two new servers (web3 and web4) with connections to the remote mysql and nfs. And replicate: Failed to restore on web3.xx.local : Checking for missing features .. .. all features in backup are supported Checking for errors in backup .. .. no errors found Starting restore.. Extracting backup archive files .. .. done Re-creating virtual server domain2.com .. Error: No LDAP client configuration file was found on your system, so the LDAP server must be set on the Module Config page X-Frame-Options: SAMEORIGIN Content-Security-Policy: script-src 'self' 'unsafe-inline' 'unsafe-eval'; frame-src 'self'; child-src 'self' Content-type: text/html; Charset=UTF
Edit: On an other test replicate (that I can't recreate) I could replicate the domains and see the useres in the /etc files ( passwd, shadow and so on) . Than I delete th domains on web0 and replicate with the option "Delete domains no longer on source" I get an error:
.. deletion on web3.xx.local of 2 domains failed : Error: No LDAP client configuration file was found on your system, so the LDAP server must be set on the Module Config page Error ----- No LDAP client configuration file was found on your system, so the LDAP server must be set on the Module Config page ----- Deleting virtual server domain.com
Submitted by JamieCameron on Sat, 06/09/2018 - 14:02 Comment #10
So are these servers are sharing users and groups via a common LDAP server? It looks like they are (based on the error about the user already existing), but Virtualmin doesn't think so.
Submitted by ghost23 on Mon, 06/11/2018 - 01:53 Pro Licensee Comment #11
Yes thats right!
I've done it form "https://www.virtualmin.com/documentation/id%2Ccombining_virtualmin_and_ldap" ( all steps until "Creating LDAP Users with Virtualmin")
and web0, web1 and web2 have all access to the ldap. I can for example create a user in the ldap and login via ssh on all three servers. But virtualmin dot think so as you mentioned.
Submitted by JamieCameron on Tue, 06/12/2018 - 01:09 Comment #12
If you run
virtualmin check-configon one of the systems as
rootvia SSH, does it say anything about LDAP being used?
Submitted by ghost23 on Tue, 06/12/2018 - 03:23 Pro Licensee Comment #13
On logini at the server it self: web1 login: root Password: LDAP Password:
and virtualmin check-config:
LDAP user and group management is properly configured.
Submitted by JamieCameron on Wed, 06/13/2018 - 00:19 Comment #14
On all systems, is the LDAP client configured to use the same IP or hostname for the LDAP server?
Submitted by ghost23 on Wed, 06/13/2018 - 01:25 Pro Licensee Comment #15
Submitted by JamieCameron on Sat, 06/16/2018 - 10:28 Comment #16
Any chance we could get access to your system to see what's going wrong inside Cloudmin/Virtualmin here?
Submitted by ghost23 on Sat, 06/16/2018 - 13:43 Pro Licensee Comment #17
Sure. It's a testing environment. What do you prefere? SSH Web or some like TeamViewer? I'll set this up on monday.
Submitted by JamieCameron on Mon, 06/18/2018 - 00:24 Comment #18
Root SSH access would be the most useful. You can email me credentials at firstname.lastname@example.org
Submitted by ghost23 on Fri, 06/22/2018 - 01:46 Pro Licensee Comment #19
Any news on this Jamie?
Submitted by JamieCameron on Sat, 06/23/2018 - 21:05 Comment #20
Taking a look now ...
Submitted by JamieCameron on Sat, 06/23/2018 - 21:35 Comment #21
OK, looking into this there are some deeper Virtualmin bugs that need to be fixed to get this working, sorry. I will update this ticket with progress..
Submitted by ghost23 on Mon, 06/25/2018 - 01:51 Pro Licensee Comment #22
OK. I close the SSH port, if you need it again give me a sign.
Submitted by JamieCameron on Sun, 09/02/2018 - 16:43 Comment #23
This will be properly fixed in the next release.
Submitted by IssueBot on Thu, 10/11/2018 - 20:07 Comment #24
Automatically closed - issue fixed for 2 weeks with no activity.
Submitted by ghost23 on Mon, 11/26/2018 - 03:12 Pro Licensee Comment #25
Is this fixed ? I tried it with on luck.
Submitted by JamieCameron on Wed, 11/28/2018 - 23:30 Comment #26
I forgot to update this - the latest Virtualmin release and the upcoming Cloudmin release should fix these issues.
Submitted by ghost23 on Tue, 01/22/2019 - 05:55 Pro Licensee Comment #27
Any news on this? Not Work on Cloudmin 9.4 virtualmin 6.05
Submitted by JamieCameron on Wed, 01/23/2019 - 00:00 Comment #28
Releases that include fixes for this issue are out already - make sure you upgrade to the latest Virtualmin and Cloudmin.
Submitted by ghost23 on Wed, 01/23/2019 - 01:33 Pro Licensee Comment #29
On source: Webmin version 1.902 Usermin version 1.751 Virtualmin version 6.05
Cloudmin version 9.4 Pro
on destination: Webmin version 1.902 Usermin version 1.751 Virtualmin version 6.05
should be the latest. Am I wrong?
Submitted by JamieCameron on Fri, 01/25/2019 - 00:12 Comment #30
Those are all the latest versions..
Any chance we can login to your system to see what's going wrong?
Submitted by ghost23 on Mon, 01/28/2019 - 15:11 Pro Licensee Comment #31
No problem I send IP, user, pass and root pass to your mail. please notify me if you need any further information or you are ready that I can deactivate SSH.
Submitted by JamieCameron on Wed, 01/30/2019 - 01:01 Comment #32
Thanks, I was able to login! But which specific domain were you trying to replication, and to which destination system?
Submitted by ghost23 on Wed, 01/30/2019 - 01:42 Pro Licensee Comment #33
The final plan ist to replicate all domains on host000 (cloudmin) without (BIND, MySQL and home-directory) to host001 and host002 .
Submitted by JamieCameron on Wed, 01/30/2019 - 21:55 Comment #34
To trigger the error, what action are you taking in virtualmin or cloudmin exactly? If it's something done via the UI, can I also login to it? I can't access port 10000 from my IP address 184.108.40.206
Submitted by ghost23 on Thu, 01/31/2019 - 02:30 Pro Licensee Comment #35
Port is open for you. What I do: "Cloudmin" > "Virtualmin Settings" > "Virtual Server Replication" > open the existing Job > "Replicate Now"
Submitted by ghost23 on Fri, 02/08/2019 - 07:23 Pro Licensee Comment #36
Submitted by ghost23 on Mon, 02/18/2019 - 07:13 Pro Licensee Comment #37
Jamie? Are you on this?
Submitted by ghost23 on Mon, 02/25/2019 - 07:54 Pro Licensee Comment #38
have you got any news for me? I've to go to production soon.
Submitted by JamieCameron on Wed, 02/27/2019 - 00:35 Comment #39
Taking a look ..
Submitted by JamieCameron on Wed, 02/27/2019 - 00:53 Comment #40
Ok I think I have a fix - you need to apply this patch https://github.com/virtualmin/virtualmin-gpl/commit/3946f7dbedba13cc4b12... on the destination systems.
Submitted by ghost23 on Wed, 02/27/2019 - 01:43 Pro Licensee Comment #41
Patch on both destination systems and reboot them don't work.
Re-creating virtual server ddd.de .. .. a clash was detected : A unix user named ddd already exists - try selecting a different administration username Restore failed!
Submitted by JamieCameron on Thu, 02/28/2019 - 23:20 Comment #42
Apologies, there is another fix needed on the destination systems : https://github.com/virtualmin/virtualmin-gpl/commit/2de5028824109bf956fd...
Submitted by ghost23 on Fri, 03/01/2019 - 03:06 Pro Licensee Comment #43
Unfortunately not working both patches applied on both detination systems and even on the source system.
Submitted by ghost23 on Sun, 03/10/2019 - 06:13 Pro Licensee Comment #44
Any new ideas for this ?
Jamie do you need access to the destination system?
Submitted by ghost23 on Wed, 03/20/2019 - 04:15 Pro Licensee Comment #45
Any new findings ?
Submitted by JamieCameron on Sun, 03/24/2019 - 01:07 Comment #46
Yes, access to the destination system would be really useful in resolving this.
Submitted by ghost23 on Tue, 03/26/2019 - 09:01 Pro Licensee Comment #47
You've got a mail with all informations.
Submitted by ghost23 on Tue, 04/02/2019 - 08:38 Pro Licensee Comment #48
Any news ?
Submitted by JamieCameron on Wed, 04/03/2019 - 00:24 Comment #49
Ok, I'm in now .. taking a look.
Submitted by JamieCameron on Wed, 04/03/2019 - 00:50 Comment #50
I think I see the issue - on your remote systems, you need to go to the Virtualmin Configuration page, and set the "Store users and groups" option to "LDAP". Then run a config re-check.
Submitted by ghost23 on Wed, 04/03/2019 - 03:14 Pro Licensee Comment #51
well! On one it was set to LDAP but the re-check do the trick !!! THANKS.
now it says : "a clash was detected : The DNS domain ddd.de is already hosted by your DNS server Restore failed!" That's right because of the destinations are slave dns eervers. But i select under the replication : " Advanced replication settings" > "Virtualmin features to replicate" > "All except selected features .. " > "Home directory" + "BIND DNS domain" + "MySQL databases" .... So my thougt is BIND will not be replicated am I wrong?
Submitted by JamieCameron on Thu, 04/04/2019 - 00:52 Comment #52
It may be better to not have the remote systems setup as DNS slaves, and instead use the replication to also make them masters. That way they will be able to serve even if the primary is down for an extended period.