LXC Start hangs at Raise Network interfaces

[jnecr]

lxc-start -n 103 -F

Will hang at "A start job is running for Raise network interfaces" until the timeout of 5 minutes is reached. However, once the container is started the network eth0 is running with no problems. Container is Ubuntu 16.04 as downloaded from Proxmox templates.

To make things more complicated this only happens on one of my PVE nodes. When started on the other it breezes right past starting the network.

On container:

$cat /etc/network/interfaces
source-directory /etc/network/interfaces.d
auto eth0
iface eth0 inet dhcp
iface eth0 inet6 dhcp

On Host that hangs:

$pveversion -v
proxmox-ve: 4.2-60 (running kernel: 4.4.15-1-pve)
pve-manager: 4.2-17 (running version: 4.2-17/e1400248)
pve-kernel-4.4.6-1-pve: 4.4.6-48
pve-kernel-4.4.15-1-pve: 4.4.15-60
lvm2: 2.02.116-pve2
corosync-pve: 2.4.0-1
libqb0: 1.0-1
pve-cluster: 4.0-43
qemu-server: 4.0-85
pve-firmware: 1.1-8
libpve-common-perl: 4.0-71
libpve-access-control: 4.0-19
libpve-storage-perl: 4.0-56
pve-libspice-server1: 0.12.8-1
vncterm: 1.2-1
pve-qemu-kvm: 2.6-1
pve-container: 1.0-72
pve-firewall: 2.0-29
pve-ha-manager: 1.0-33
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u2
lxc-pve: 2.0.3-4
lxcfs: 2.0.2-pve1
cgmanager: 0.39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5.7-pve10~bpo80


$cat /etc/network/interfaces
auto lo
iface lo inet loopback

iface eth0 inet manual

iface eth1 inet manual

iface eth2 inet manual

iface eth3 inet manual

auto vmbr0
iface vmbr0 inet static
        address  192.168.2.154
        netmask  255.255.255.0
        gateway  192.168.2.1
        bridge_ports eth0
        bridge_stp off
        bridge_fd 0

On host that does NOT hang:

$pveversion -v
proxmox-ve: 4.2-60 (running kernel: 4.4.15-1-pve)
pve-manager: 4.2-17 (running version: 4.2-17/e1400248)
pve-kernel-4.4.6-1-pve: 4.4.6-48
pve-kernel-4.4.13-2-pve: 4.4.13-58
pve-kernel-4.4.15-1-pve: 4.4.15-60
lvm2: 2.02.116-pve2
corosync-pve: 2.4.0-1
libqb0: 1.0-1
pve-cluster: 4.0-43
qemu-server: 4.0-85
pve-firmware: 1.1-8
libpve-common-perl: 4.0-71
libpve-access-control: 4.0-19
libpve-storage-perl: 4.0-56
pve-libspice-server1: 0.12.8-1
vncterm: 1.2-1
pve-qemu-kvm: 2.6-1
pve-container: 1.0-72
pve-firewall: 2.0-29
pve-ha-manager: 1.0-33
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u2
lxc-pve: 2.0.3-4
lxcfs: 2.0.2-pve1
cgmanager: 0.39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5.7-pve10~bpo80



$cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto vmbr0
iface vmbr0 inet static
        address 192.168.2.150
        netmask 255.255.255.0
        gateway 192.168.2.1
        bridge_ports eth0
        bridge_stp off
        bridge_fd 0

logfile from lxc-start attached.

 

[jnecr]

I've been trying to replicate this problem starting with new containers and installing various packages that are also installed on the containers with problems. I have yet to be able to replicate the problem when starting with a new container. However, I have 4 containers that all have this problem. They were all created on older versions of PVE (but still 4.1 or 4.2).

When starting the new containers the network still gives the "Failed to start Raise network interfaces." error, however, it does not stall for 5 minutes at that step..

 

[sirlance]

I'm running into the same issue. Did you figure out what's causing it? It's fairly hard to debug, since some restarts actually seem to work, but then next one hang again at the network interfaces stage. For me it happens also with newly created containers (using PVE 4.3 at the moment).

 

[forresthopkinsa]

I was having this problem because my container was configured to use DHCP for ipv4 and ipv6 addresses, but my router DHCP server isn't configured for ipv6.

You'll know this is the problem for you if you see this blurb over and over in your networking.service journal:

Aug 25 05:51:35 metrics ifup[157]: XMT: Forming Solicit, 33190 ms elapsed.
Aug 25 05:51:35 metrics ifup[157]: XMT: X-- IA_NA e0:38:e7:c5
Aug 25 05:51:35 metrics ifup[157]: XMT: | X-- Request renew in +3600
Aug 25 05:51:35 metrics ifup[157]: XMT: | X-- Request rebind in +5400
Aug 25 05:51:35 metrics ifup[157]: XMT: Solicit on eth0, interval 34240ms.
Aug 25 05:51:35 metrics dhclient[157]: XMT: Solicit on eth0, interval 34240ms.

 

[lordcheeto]

I was having this problem because my container was configured to use DHCP for ipv4 and ipv6 addresses, but my router DHCP server isn't configured for ipv6.

You'll know this is the problem for you if you see this blurb over and over in your networking.service journal:

Thanks! Fixes that issue, and the issue I was having with the second interface not coming up.