no networking after reboot

[neynenmo]

Hi guys,

I'm facing a strange issue after a simple reboot.
The network is not coming up properly.

systemctl status networking shows:

root@pve:~# systemctl status networking
* networking.service - Network initialization
     Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
     Active: inactive (dead)
       Docs: man:interfaces(5)
             man:ifup(8)
             man:ifdown(8)

Dec 23 17:59:22 pve systemd[1]: Dependency failed for Network initialization.
Dec 23 17:59:22 pve systemd[1]: networking.service: Job networking.service/start failed with result 'dependency'.

cat /etc/network/interfaces:

auto lo

iface lo inet loopback

iface eno1 inet manual

auto vmbr0
iface vmbr0 inet static
        address 192.168.10.192/24
        gateway 192.168.10.1
        bridge-ports eno1
        bridge-stp off
        bridge-fd 0
      
iface enp4s0 inet manual

iface wlp3s0 inet manual

I haven't changed anything on the system.
The last thing that may relate to this is an apt update && apt upgrade

During the boot i noticed a period where the process got stuck and displayed the following lines alternating:

[**    ] (1 of 2) A start job is running for Wait for udev To Complete Device Initialization (1min 30s / 3min)
[  *** ] (2 of 2) A start job is running for Helper to synchronize boot up for ifdupdown (1min 31s / 3min)

Right now I'm a bit clueless where to look next.

Hints are much appreciated.

Thanks for your help in advance.

 

[neynenmo]

Since time was a little short, I decided to reinstall the system.

Unfortunately, the cause could not be determined, but I hereby close the thread.

 

[theyost]

Same problem here. The last thing I did was "apt update && apt upgrade"

 

[theyost]

Okay... I am back (was down for about 30min which is a lot less than I was expecting)

Proxmox does have a networking page: https://pve.proxmox.com/wiki/Network_Configuration
... but honestly I don't know if I read it.

No network connection means I wasn't able to use putty/ssh to get in so I had use my Dell's iDrac system (similar to a keyboard + monitor). This allowed me to poke around the OS a bit (knowing a Debian system):

root@pve:/# pveversion
root@pve:/# cat /etc/issue
root@pve:/# cd /etc/network
root@pve:/# ls -al
root@pve:/# cat interfaces

> # network interface settings; autogenerated
> # Please do NOT modify this file directly, unless you know what
> # you're doing.
> #
> # If you want to manage parts of the network configuration manually,
> # please utilize the 'source' or 'source-directory' directives to do
> # so.
> # PVE will preserve these directives, but will NOT read its network
> # configuration from sourced files, so do not attempt to move any of
> # the PVE managed interfaces into external files!
>
> auto lo
> iface lo inet loopback
>
> iface eno1 inet manual
>
> iface eno2 inet manual
>
> iface eno3 inet manual
>
> iface eno4 inet manual
>
> auto vmbr0
> iface vmbr0 inet static
> address 192.168.10.20/24
> gateway 192.168.10.1
> bridge-ports eno1
> bridge-stp off
> bridge-fd 0

... note the "vmbr0" is the normal interface

root@pve:/# ifup vmbr0

... and that did it. When to my browser and it loaded the normal page. The only thing that was different was I needed to manually start all the vm's.

I don't know why the apt-update stopped the network from starting automatically, and there is a good chance it will be down again on the next restart. For now I am going to rely on it staying up for the next couple weeks until I will have time to figure this out.

Just for the record I am now running Proxmox v7.1-10 and the last apt-update caused this mess.

-Dave

 

[Dunuin]

You should never run "apt upgrade" with PVE as this could screw up your installation. Only "apt dist-upgrade" or "apt full-upgrade" should be used.
Don't ask me exactly why. Just repeating what the staff said multiple times.

 

[spirit]

@theyost​

maybe try:
"systemctl mask ifupdown2-pre.service"

if a device is hanging at boot. (could be another device than the network card)

@Dunuin

You should never run "apt upgrade" with PVE as this could screw up your installation. Only "apt dist-upgrade" or "apt full-upgrade" should be used.
Don't ask me exactly why. Just repeating what the staff said multiple times.

This is because, "apt upgrade" only upgrade current installed package. Proxmox, not like a "stable" distro, can release new feature with sometime new package depencies. (For example, qemu need a need lib). If you use only "apt upgrade", the needed new dependencies will not be installed.

That's why you need dist-upgrade, to upgrade current package but also install new dependencies.