adding virtual servers does not add networking

I am in the land of OZ. New Xeon CentOS server, mim install. First thing I do is command line ping to outsite IP. No problem. Network working as expected. Using control panel add a new virtual server. It looks like it installs but the IP is apparently not added. Look into /etc/sysconfig/network-scripts. Nothing I can recognize. Have to install net-tools just to get ifconfig working. What the heck is going on?

This is not doing a Microsoft thing is it where they change everything for no reason? :-) So I have a "enp2s0" representing the interface. Command nmcli d shows: enp2s0 ethernet connected enp3s0 lo loopback unmanaged --

Virtualmin has created a ifcfg-enp3s0 file and ifcfg-enp3s0:0. This is a first working virtual server. Adding other servers does not add these files. Command to restart network does not work. So we now have the primary IP working and one added virtual account on the next IP working, but when adding anymore accounts no network script files are created. No eth0 file anywhere. Did somebody change all the network on CentOS 7 and forgot to tell me?

Closed (fixed)


Yes, CentOS 7 completely changed how network interfaces are named - which I agree is very annoying.

Did you create this VM using Cloudmin from an image that we provide? Because our images are setup by default to revert to the old naming style.

It is a dedicated server at our small data center here. Ran the script installing the pro version with 100 account license. Added the first account and it worked. Added the second and it does not appear to be creating the files needed. Deleted it, added it back and still nothing. It is not adding the necessary networking and new IP. Using nmcli c down enp3s0; nmcli c up enp3s0 it did restart that interface which is the only working website on the machine. Not sure why Virtualmin is not successful at creating more scripts and restarting the network. I suppose I could rebuild the machine but I don't necessary have an expectation that the results would be any different. I could create the network file myself using nano or something but that seems a bit silly right?

[root@localhost network-scripts]# systemctl reload network.service Job for network.service failed. See 'systemctl status network.service' and 'jour nalctl -xn' for details. [root@localhost network-scripts]# journalctl -xn -- Logs begin at Thu 2015-03-05 21:18:07 PST, end at Fri 2015-03-06 17:12:05 PST Mar 06 17:11:59 localhost.localdomain sshd[23669]: pam_succeed_if(sshd:auth): re Mar 06 17:12:01 localhost.localdomain sshd[23669]: Failed password for root from Mar 06 17:12:01 localhost.localdomain sshd[23669]: Received disconnect from 183. Mar 06 17:12:01 localhost.localdomain sshd[23669]: PAM 2 more authentication fai Mar 06 17:12:03 localhost.localdomain sshd[23673]: Did not receive identificatio Mar 06 17:12:03 localhost.localdomain sshd[23674]: Did not receive identificatio Mar 06 17:12:04 localhost.localdomain sshd[23671]: pam_unix(sshd:auth): authenti Mar 06 17:12:04 localhost.localdomain sshd[23671]: pam_succeed_if(sshd:auth): re Mar 06 17:12:05 localhost.localdomain sshd[23671]: Failed password for root from Mar 06 17:12:05 localhost.localdomain sshd[23671]: pam_succeed_if(sshd:auth): re

So does this second domain you are adding have it's own private IP address? If not, Virtualmin shouldn't need to touch the network config files.

It has been are habit to give each domain a private IP. I realize this is not standard, but that is the way we did it long, long ago. I have tried again but nothing I do so far creates any network files. Nor can I restart the network short of a reboot. Never had any issues before with the


So, that should happen in this case is that each new domain with a private IP gets a ifcfg-enp3s0:X file, where X is an incrementing number. Are you finding that these files don't get created at all? Or that they are created, but the IP isn't activated on the system at boot time?

I would say that the files are not getting created and when an attempt to add another virtual account happens it won't because it says the IP is already in use. Honestly, I don't know where to go from here. I can rebuild the machine and hope to have different results. The files are ifcfg-enp3s0:0, ifcfg-enp3s0.lock and ifcfg-enp3s0. That appears to be the only network files . So a second working virtual is added but no more can be added after that. I would guess it can't create a file because it is already there and it is not augmenting the file name. Just guessing. NAME="Virtualmin server" BOOTPROTO=none NM_CONTROLLED=no MACADDR="" IPV6INIT=no DEVICE=enp3s0:0 NETMASK= MTU="" ONPARENT=yes BROADCAST= IPADDR= NETWORK= ONBOOT=yes

Which one of those files contains those contents?

Also, when creating a domain are you entering a specific IP address, or letting Virtualmin allocate one automatically?


That would be ifcfg-enp3s0:0. I am in the process of building a new server. It was my plan to run your script again using that last 100 client license I used yesterday. I have not been entering the IP by hand but rather setup a range for Virtualmin to select from which is how our other server work at this time. Hopefully, I will have tested the new server in the next hour or two.


So far the server we built today works just fine. Must have been something glitchy with the server we built yesterday. Thanks for your help. All is well that ends well.

Scott Hirsch, SecureWebs

Ok, I will close this ticket for now.

Automatically closed -- issue fixed for 2 weeks with no activity.