All Linux Container freezing/unresponsive

[Superfestung]

Hi Proxmox Community,
im new here and also new to Proxmox. This is my first post.

I have a Server with 3 Containers and 3 VM's running,
The VM's are running without any trouble so far.

The 3 unprivileged Linux Containers, all Debian 11 standard based, are freezing/unresponsive after approximately 1 day.

• Container 1 has a pihole installation.
• Container 2 has a Homebridge installation.
• Container 3 has a DynDNS client from No-IP and a OpenVPN Server installation.

I cannot reach the web server of the containers application anymore. Also SSH access is not possible anymore. Only the Proxmox Interface embedded Terminal still seems to work.
I detected this behaviour by the Network Traffic Chart. The net-in value becomes lower and the net-out becomes 0.
When I reboot the containers they are working fine again for another day.

Did I miss something in setting up of those containers?
Any ideas what the reason could be?

Thanks a lot in advance!

 

[mira]

Please provide the output of pveversion -v

Do you see any errors in the journal or syslog?

 

[Superfestung]

root@pve:~# pveversion -v
proxmox-ve: 7.2-1 (running kernel: 5.15.64-1-pve)
pve-manager: 7.2-11 (running version: 7.2-11/b76d3178)
pve-kernel-5.15: 7.2-13
pve-kernel-helper: 7.2-13
pve-kernel-5.15.64-1-pve: 5.15.64-1
pve-kernel-5.15.30-2-pve: 5.15.30-3
ceph-fuse: 15.2.16-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve1
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.2-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.2-3
libpve-guest-common-perl: 4.1-4
libpve-http-server-perl: 4.1-4
libpve-storage-perl: 7.2-10
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.0-3
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.2.7-1
proxmox-backup-file-restore: 2.2.7-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.5.1
pve-cluster: 7.2-2
pve-container: 4.2-3
pve-docs: 7.2-2
pve-edk2-firmware: 3.20220526-1
pve-firewall: 4.2-6
pve-firmware: 3.5-6
pve-ha-manager: 3.4.0
pve-i18n: 2.7-2
pve-qemu-kvm: 7.0.0-4
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-4
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.6-pve1

I cannot see errors in the syslog

 

[mira]

Based on the description it seems those containers lose the network rather than getting stuck, since you can still access them using the terminal.

Do you have logs inside the containers mentioning network related issues?
Can you get it to work again when removing the network and adding it again?

 

[Superfestung]

will try more as soon as its stucking again.
I changed also 1 container from dhcp to static IP for testing.

Do you mean any specific logs inside of the container I can use, or is it the standard Proxmox Task History?

 

[Superfestung]

It's seems to be a network related issue. The container with static IP is now already running since 3 days.
The strange thing is, that my VM's with DHCP are not having this issue

 

[mira]

You could try to run tcpdump and check for any DHCP traffic.
This could shed some light on where the DHCP packets may be dropped.

 

[leesteken]

Make sure that IP Filter is not enabled (and DHCP is enabled) in Firewall > Options for containers that use DHCP?

 

[bke]

I have same issue. Linux VM with ubuntu and openvpn on it, nothing else is running. While no connection to openvpn netout goes down until reaches 0, but VM is still working. After connecting to VM via terminal and making some pings, VM becomes reachable. Output of pveversion -v

proxmox-ve: 7.1-1 (running kernel: 5.13.19-2-pve)
pve-manager: 7.1-7 (running version: 7.1-7/df5740ad)
pve-kernel-helper: 7.1-6
pve-kernel-5.13: 7.1-5
pve-kernel-5.13.19-2-pve: 5.13.19-4
ceph-fuse: 15.2.15-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-5
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-14
libpve-guest-common-perl: 4.0-3
libpve-http-server-perl: 4.0-4
libpve-storage-perl: 7.0-15
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.11-1
lxcfs: 4.0.11-pve1
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.1.2-1
proxmox-backup-file-restore: 2.1.2-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-4
pve-cluster: 7.1-2
pve-container: 4.1-2
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.3-3
pve-ha-manager: 3.3-1
pve-i18n: 2.6-2
pve-qemu-kvm: 6.1.0-3
pve-xtermjs: 4.12.0-1
qemu-server: 7.1-4
smartmontools: 7.2-1
spiceterm: 3.2-2
swtpm: 0.7.0~rc1+2
vncterm: 1.7-1
zfsutils-linux: 2.1.1-pve3

Network traffic chart looks like this: