More bugs as if that is possible.

10 posts / 0 new
Last post
#1 Mon, 08/15/2016 - 07:03

More bugs as if that is possible.

After Joe's suggestion I went ahead and used the functionality of Cloudmin/Cloudmin services and I can not get the servers to cluster slaves right. On one of the VM's, I get the following:

Adding ..
Server is not running Webmin version 1.202 or above.

I could only find one reference to this on Google and none here. The post I found in the Google response was of no use - closed by someone on the team here.

Can anyone tell me why I am having this version issue? For goodness sakes, Webmin in that container is 1.810! Am I going to have to install this stuff again? I am so sick of running into different fatal issues with Cloudmin/Webmin/Virtualmin, I could scream. I said long ago I had some notions of contributing to the project with features through new code/modules, but I want no part of adding functionality to something that is "broken" in number of ways.

For instance, to make all of the servers available to be added as a DNS cluster server, you have to delete all of the Webmin Servers Index machines and add them back in one at a time, then going to the Cluster DNS server setting, otherwise not all of your servers are going to be available for you as an option in Cluster DNS servers.

I could go on and on, but there is no point. I am just right now trying to find the bug is producing the error and ensuing failure in Cluster DNS Servers in Bind.

Mon, 08/15/2016 - 09:58


Yeah it sounds like we need to get Jamie's help with that one, but we should definitely be able to get it fixed up.

Could you open a support request, using the Support link above? That's the best way to include Jamie on that issue.



Mon, 08/15/2016 - 13:34

OK, yeah no problem Eric. I have wondered about using the support system - I.E. when it appropriate, so thank you for that. Will do.


Mon, 08/15/2016 - 17:53
Joe's picture

Are ports 10000-10010 accessible between the Cloudmin master and the Webmin DNS server? That ancient version is probably around about when RPC was added to Webmin, so maybe Webmin thinks it doesn't have it because it can't access the RPC ports (it historically would fall back to non-RPC communication for the DNS slave stuff, but that's probably not possible in Cloudmin Services, since it's new enough that nobody would be running a version without that feature).

But, the error should definitely be better, if that's the problem. And, we probably need to be more clear about that necessity for anything in a Webmin cluster. File bugs when you come across stuff like this; a confusing error is bug-like, even if it's not actually broken functionality.


Check out the forum guidelines!

Mon, 08/15/2016 - 18:39 (Reply to #4)

"Are ports 10000-10010 accessible between the Cloudmin master and the Webmin DNS server?"

Yes everything is open. What I did do out of frustration was basically delete everything that might be tied to anything else. All Webmin systems in the Webmin Server's Index, all DNS - everything that had a setting to be cleared clear back to the install and then moved forward again. I now see no signs of the error, but that is agitating as it would be nice to know the root cause of that error. Since it "worked" and allowed me to use the -->Cloudmin > Virtualmin > Virtualmin Settings > Virtualmin Domains in Cloudmin without error, it seemed improper to file a bug report on something I can no longer provide good accurate data on/reproduce, so I did not file the bug report.

I would agree though Joe, I have seen some very weird behavior which likely should go the route of a bug report and I will file one the next time I find myself where a problem is illogical and insurmountable. It looks like things "should" be setup to run now. We had a failure that wiped the hardware firewall and are dealing with replacing and reprogramming that at this time. Once it is set up properly I can continue to test to see if all is well. Without it up, NAT and such can't make the transfer on port 53 properly. (NAT on a muti-network LAN can be a pain to deal with - something I hate...) BTW, if you were wondering, this is a single physical server located on site with a CentOS 6.8 Cloudmin HN and 3 OpenVZ (CentOS 6.8) containers - all containers being identical save IP's, hostnames, etc.

I will keep you all up to date once the LAN is back up and proven correct. I would like to for kicks then attempt using Cloudmin/Webmin to try and actually make an OpenVZ container system, for that is why I am a CLI genius now for when I started on this project in my free time, none of that worked properly at all. That has been so long ago, I would assume the two errors were fixed - resizing the RAM allotment on boot as well as just failing to install due to lack of memory, even though the amount shown was orders of magnitude larger than the container. (Blank disk basically..)

Thanks in advance, -Douglas

Tue, 11/01/2016 - 12:38

Hi, is there a fix yet? Just installed 3 identical servers, and getting: "Server is not running Webmin version 1.202 or above." no matter which way I try to add servers, from server1 -> server2, from server1 -> server3, from server2 -> server1 etc. etc.

All servers are: OS: CentOS Linux 7.2.1511, Webmin version 1.821 and Bind 9.9.4

Thanks, - Yorkki

Tue, 11/01/2016 - 13:16 (Reply to #6)

Got it to work somehow. Went back and forth "edit server in webmin servers index" and "save", suddenly I got all server statuses say: Running Webmin 1.821, and after that clustering them in Bind worked. Weird.

Thu, 03/30/2017 - 05:07

Unfortunately this bug still exists. On two new VMs exactly same problem. Removing-adding server didn't help, still getting the "is not running Webmin version 1.202 or above" while version on both servers are 1.831.

Anyone with a suggestion?

Mon, 04/03/2017 - 04:05


I think the cause is pretty basic (I have noticed it today). If you add the webmin server without checking the SSL option, it behaves exactly like this. You can observe this editing the added server again, and you will see the error. As soon as you check the SSL option, the error goes away.

Please note, I'm talking about the step where you add the webmin server, not where you add the slave DNS server.

Wed, 05/10/2017 - 07:49

Hello all; After a lot of search and even read this post i have managed to solve it after try to control the server via Cluster Webmin Server and found the problem is port 10014 is not opened after open it Wooh problem solved and display message is:

Adding ..

Added, with 6 existing zones.

Setup with 48 new slave zones.

Hope this help you all. Regards

Topic locked