[SOLVED] A start job is running for Raise network interfaces

[TheLovinator]

Hi,

I have some problem with containers in Proxmox. When I start a container I get "A start job is running for Raise network interfaces". It's only 50% of all containers that is fucked and they have nothing in common except OS. All containers are up to date.

What could the problem be?

Container:

Network device for container

ifconfig -a on container

   eth0      Link encap:Ethernet  HWaddr ca:15:94:ee:93:5e
              inet addr:192.168.0.9  Bcast:192.168.0.255  Mask:255.255.255.0
              inet6 addr: fe80::c815:94ff:feee:935e/64 Scope:Link
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:3213 errors:0 dropped:0 overruns:0 frame:0
              TX packets:1593 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:956325 (956.3 KB)  TX bytes:1052172 (1.0 MB)
 
    lo        Link encap:Local Loopback
              inet addr:127.0.0.1  Mask:255.0.0.0
              inet6 addr: ::1/128 Scope:Host
              UP LOOPBACK RUNNING  MTU:65536  Metric:1
              RX packets:4784 errors:0 dropped:0 overruns:0 frame:0
              TX packets:4784 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1
              RX bytes:1096030 (1.0 MB)  TX bytes:1096030 (1.0 MB)

systemctl status networking.service on container

    * networking.service - Raise network interfaces
       Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
      Drop-In: /run/systemd/generator/networking.service.d
               `-50-insserv.conf-$network.conf
       Active: failed (Result: timeout) since Sun 2017-02-12 01:18:30 UTC; 11min ago
         Docs: man:interfaces(5)
      Process: 106 ExecStart=/sbin/ifup -a --read-environment (code=killed, signal=TERM)
      Process: 90 ExecStartPre=/bin/sh -c [ "$CONFIGURE_INTERFACES" != "no" ] && [ -n "$(ifquery --read-environment --list --exclude=lo)" ] && udevadm settle (code=exited, status=0/SUCCESS)
     Main PID: 106 (code=killed, signal=TERM)

/etc/network/interfaces on container

    auto lo
    iface lo inet loopback
    iface lo inet6 loopback
  
    # interfaces(5) file used by ifup(8) and ifdown(8)
    # Include files from /etc/network/interfaces.d:
    source-directory /etc/network/interfaces.d
  
    auto eth0
    iface eth0 inet static
            address 192.168.0.9
            netmask 255.255.255.0
            gateway 192.168.0.1
  
    iface eth0 inet6 dhcp

Proxmox:

My Network settings on proxmox

eth0

vmbr0

ifconfig -a on Proxmox

/etc/network/interfaces on Proxmox

    auto lo
    iface lo inet loopback
 
    auto vmbr0
    iface vmbr0 inet static
            address 192.168.0.2
            netmask 255.255.255.0
            gateway 192.168.0.1
            bridge_ports eth0
            bridge_stp off
            bridge_fd 0

Proxmox is running: (Does "running kernel/version" mean I am running a older version? apt upgrade does not update to later version):

    proxmox-ve: 4.4-79 (running kernel: 4.4.35-2-pve)
    pve-manager: 4.4-12 (running version: 4.4-12/e71b7a74)
    pve-kernel-4.4.6-1-pve: 4.4.6-48
    pve-kernel-4.4.35-1-pve: 4.4.35-77
    pve-kernel-4.4.35-2-pve: 4.4.35-79
    pve-kernel-4.4.21-1-pve: 4.4.21-71
    pve-kernel-4.4.24-1-pve: 4.4.24-72
    pve-kernel-4.4.19-1-pve: 4.4.19-66
    lvm2: 2.02.116-pve3
    corosync-pve: 2.4.0-1
    libqb0: 1.0-1
    pve-cluster: 4.0-48
    qemu-server: 4.0-108
    pve-firmware: 1.1-10
    libpve-common-perl: 4.0-91
    libpve-access-control: 4.0-23
    libpve-storage-perl: 4.0-73
    pve-libspice-server1: 0.12.8-1
    vncterm: 1.2-1
    pve-docs: 4.4-3
    pve-qemu-kvm: 2.7.1-1
    pve-container: 1.0-93
    pve-firewall: 2.0-33
    pve-ha-manager: 1.0-40
    ksm-control-daemon: 1.2-1
    glusterfs-client: 3.5.2-2+deb8u3
    lxc-pve: 2.0.7-1
    lxcfs: 2.0.6-pve1
    criu: 1.6.0-1
    novnc-pve: 0.5-8
    smartmontools: 6.5+svn4324-1~pve80
    zfsutils: 0.6.5.8-pve14~bpo80

The containers are running latest version of Ubuntu 16.04.2 LTS.

I have restarted the server and the problem still persists.

Any help will be greatly appreciated!

 

[fireon]

You Problem is this line:

iface eth0 inet6 dhcp

That did not work yet. Use SLAAC in the PVEinterface not DHCP per IPV6. I use also Ubuntu on LXC, maybe this is some bug, don't know on what side.

 

[TheLovinator]

Thanks, that fixed the problem! <3

 

[xbishop]

I signed up to post this on both threads. I've had this issue with a local AND datacenter installation of proxmox for testing. SSHD would not start on ubuntu 16.04 after a reboot and the way that I've found to fix this is to:

sudo nano /etc/systemd/system/network-online.target.wants/networking.service

Change

TimeoutStartSec=5min

to

TimeoutStartSec=1sec

Reboot and you have SSH!

Hello future me for when you stress out over this again.

keywords: sshd_server sshd proxmox ubuntu dead inactive halt restart ssh_server systemd