parent interface eth0 does not exist!

Help! (Home for newbies)
1

Hi,

On a new created, fresh debian9 install on a vps with plenty of power (8cores, 8Go RAM). I have the following problem:

When I add a new domain with a dedicated IP, on the creation log it says “parent interface eth0 does not exist!”, and the new IP is not configured, I have to go to network configuration and add it manually as a virtual interface inside eth0.
eth0 is the only interface I have there with lo.

Any idea what cause this and why virtualmin can’t add it automatically.

on “Default virtual server IPv4 address”, on virtualmin setup, I have the default server IPv4 manually set, as the re-check config gave me this error before that :

“Virtualmin could not work out the default IPv4 address for virtual servers on your system. You will need to update either the Network interface for virtual addresses or Default virtual server IP address fields on the module configuration page.”

now it still give the same error about ipV6 , but at least it say virtualmin is ready to be used.

/sbin/ifconfig output is :

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet IP.IP.IP.IP netmask 255.255.255.255 broadcast IP.IP.IP.IP
inet6 fe80::ff:xxxx:xxxx prefixlen 64 scopeid 0x20
ether 02:00:00:xx:xx:xx txqueuelen 1000 (Ethernet)
RX packets 2770 bytes 334532 (326.6 KiB)
RX errors 0 dropped 2 overruns 0 frame 0
TX packets 2115 bytes 811162 (792.1 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 1000 (Local Loopback)
RX packets 236 bytes 19470 (19.0 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 236 bytes 19470 (19.0 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

any idea guys ?

2

.

3

Looks like you need to add your other dedicated IP in the network interfaces. it will be eth0:0, without telling your other ips, how would the system know?
Webmin, Networking, Network configuration, Add a new interface.

4

I know, my question is why it’s not added automatically by virtualmin. I tell the interface what’s my dedicated IP when creting the new virtual server, but it tell me “parent interface eth0 does not exist!” on the step where it should configure the new IP.
and, it used to work on previeus version of virtualmin.

5

sorry, I don’t know any previous versions, I only know you need to tell your OS how many interfaces you have, eth0, eth0:0, eth0:1 and so on, but to be honest never seen any os do that automagic. :slight_smile:

6

Virtualmin is supposed to do this automagically, out of the box, wonderfull isn’t it?

7
  • resolved.

that ip was configured on another running CT, even if it was pointing to the centOS6 mac, he could not use it.

I found it adding :
IPV4_FAILURE_FATAL=yes

to :
/etc/sysconfig/network-scripts/ifcfg-eth0

and restarting network :
service network restart

it gave

[root@centos /]# service network restart
Shutting down interface eth0: [ OK ]
Shutting down loopback interface: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface eth0: Determining if ip address IP.IP.IP.IP is already in use for device eth0…
Error, some other host (02:00:00:xx.xx.xx) already uses address IP.IP.IP.IP
[FAILED]

not I just deleted that IP from the other CT and rebooted it.

Now any additional IP is configured automatically, automagically ?

8

Thanks for following up! That’s great troubleshooting. It would have taken me a while to find that one (it’s been a long time since I’ve been working with stuff in my own data center so I could mess up IPs that way, but I’ve sure done it in the past!).