Strange networking behavior after upgrading to 8.0

AprilMan7

New Member
Jun 22, 2023
3
0
1
Hi everyone,

I have a networking issue with my proxmox server. Yesterday I upgraded from 7.4 to 8.0 and had no issues until the reboot. The "networking" service hang at boot and refuse to work properly, after a few hours I was able to access my proxmox server with ssh by adding a killing timer to it using a livecd.
Also, I can make my network work with a very specific setup, any other don't work. Here's the one I currently have and that work (still needed to kill networking.service to fully boot):

Code:
auto lo
iface lo inet loopback

auto eno1
iface eno1 inet static
    address 217.x.x.x/23
    gateway 217.x.x.1

#iface eno2 inet manual

If I use my old interfaces configuration, it doesn't work anymore (no interface go up and I still need to kill networking.service to boot):
Code:
auto lo
iface lo inet loopback

iface eno1 inet manual

#iface eno2 inet manual

auto vmbr0
iface vmbr0 inet static
    address 217.x.x.x/23
    gateway 217.x.x.1
    bridge-ports eno1
    bridge-stp off
    bridge-fd 1
    pointopoint 217.x.x.1
    bridge_hello 2
    bridge_maxage 12

Here's the logs I've been able to get from networking.service in verbose mode (using eno1 only): https://pastebin.com/wjEkDu22

ifupdown2 logs: https://pastebin.com/G1VzFTHY

Any idea of what I could try to fix that?

Thank you
 
Last edited:
the last thing before the timeout is "proxmox info[846]: executing /etc/network/if-up.d/ntpsec-ntpdate" - could you find out if that takes to long or blocks?
 
the last thing before the timeout is "proxmox info[846]: executing /etc/network/if-up.d/ntpsec-ntpdate" - could you find out if that takes to long or blocks?
I'm sure the timeout comes from the fact that I kill the service after 30 seconds to be able to boot completely. I'm not sure if ntpsec-ntpdate is the issue here.
I've been able to turn on all my interfaces after some test, I removed the following options:
Code:
pointopoint 217.x.x.1
bridge_hello 2
bridge_maxage 12
Changed bridge-fd 1 to 0
Then restarted networking by doing systemctl restart networking and all my interfaces were there.

My current interfaces config file for reference:

Code:
auto lo
iface lo inet loopback

iface eno1 inet manual

#iface eno2 inet manual

auto vmbr0
iface vmbr0 inet static
    address 217.x.x.x/23
    gateway 217.x.x.1
    bridge-ports eno1
    bridge-stp off
    bridge-fd 0
 
I was facing this exact issue after upgrading my Proxmox from 7.4 to 8.0, and the reason was that ntpsec service was failing. It was missing /var/log/ntpsec directory and correct permissions for that. There is this in /etc/ntpsec/ntp.conf file:
Code:
# You must create /var/log/ntpsec (owned by ntpsec:ntpsec) to enable logging.
#statsdir /var/log/ntpsec/
For some reason the upgrade did not create that directory and set the permissions, and the service does not create that if it's missing either. I did that manually, but eventually I purged the ntpsec and replaced it with Systemd Chrony, because I'm more familiar with that. Now networking service starts just fine.

But this is kind of critical issue, because the system fails to boot up: networking service won't start because of this issue and there's no time limit to wait that networking service has been executed/started successfully (the boot process won't reach login screen at all because of this). I had to start the system in Recovery mode and troubleshoot + fix the issue there.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!