Intermittent Network Dropouts

Tony C

Member
May 28, 2020
29
2
23
On my proxmox single server setup I have the following network setup:

vmbr0: Bridge onto the main network. This as a video renderer VM (media) and a desktop VM (pluto) connected to it.
vmbr1: NAT, using the PVE host to do the DNS/DHCP by using dnsmasq and NATting via IPTables and forwarding rules in the standard way, again on the host.
vmbr2: Local bridge network. This has a dedicated VM acting and a NAT router, again with DNS and DHCP services. This is to replicate a network at work. Connected to this network is the aforementioned NAT router VM, a Docker Portus registry, a docker server and the second network interface on pluto.
vmbr3: Local bridge network, as yet unused.

I am running Proxmox 6.2-6

So pluto is connected to both vmbr0 and vmbr2. Media is connected to vmbr0 only. On two occasions recently (about a week apart) the these VMs momentarily lost network comms and ssh/vnc sessions were terminated. When this happened I could reconnect without issue (done within a minute the first time).

The first time Media dropped it's VNC and ssh connection on vmbr0 and pluto lost it's ssh/sshfs connections on vmbr2 to the docker server but the VNC connection on vmbr0 was fine. The second time pluto again lost it's ssh/sshfs connections on vmbr2 to the docker server and vmbr0 was fine (media wasn't running).

I looked through the logs on the VMs and the host and found absolutely nothing indicating anything wrong. The media VM was cloned from pluto and renamed etc. These VMs as all the others are running Ubuntu 18.04 LTS server and the desktop is KDE (kubuntu-desktop). The other common thing between pluto and media is that they are both hibernated each night rather than shut down as the PVE server is in my bedroom and so is shut down each night. Incidentally each incident happened hours after the VMs had been resumed (say 4-6 hours).

Has anyone seen anything like this before? Is hibernation not that reliable? What extra diagnosis can be done?

Any ideas would be greatly appreciated.

Tony.

Package versions:
proxmox-ve: 6.2-1 (running kernel: 5.4.41-1-pve)
pve-manager: 6.2-6 (running version: 6.2-6/ee1d7754)
pve-kernel-5.4: 6.2-2
pve-kernel-helper: 6.2-2
pve-kernel-5.4.41-1-pve: 5.4.41-1
pve-kernel-5.4.34-1-pve: 5.4.34-2
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.3-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: not correctly installed
ifupdown2: 3.0.0-1+pve2
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.15-pve1
libproxmox-acme-perl: 1.0.4
libpve-access-control: 6.1-1
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.1-3
libpve-guest-common-perl: 3.0-10
libpve-http-server-perl: 3.0-5
libpve-storage-perl: 6.1-8
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.2-1
lxcfs: 4.0.3-pve2
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.2-7
pve-cluster: 6.1-8
pve-container: 3.1-8
pve-docs: 6.2-4
pve-edk2-firmware: 2.20200229-1
pve-firewall: 4.1-2
pve-firmware: 3.1-1
pve-ha-manager: 3.0-9
pve-i18n: 2.1-3
pve-qemu-kvm: 5.0.0-4
pve-xtermjs: 4.3.0-1
qemu-server: 6.2-3
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.4-pve1
 
Last edited:

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!