Problems with lxc containers

[cryptolukas]

Hi,

I receive such errors during a restart of lxc containers.
This is really creepy.

Message from syslogd@pve02 at Mar 27 21:36:53 ...
 kernel:[862949.880757] unregister_netdevice: waiting for lo to become free. Usage count = 1
Mar 27 21:36:53 pve02 kernel: [862949.880757] unregister_netdevice: waiting for lo to become free. Usage count = 1

 

[tafkaz]

Hi there,

we're experiencing the same error message here with our LXC VM.
Additionally this VM will crash completely everey 4-5 days, all by a sudden.
The VM holds an ISPConfig guest, running mysql dovecot, postfix and apache services.
So, when the freezing happens, no mail services are reachable from one moment to another.
We're really desperate now, as we cannot see any reason for this.
The problem started right after we switched from Proxmox 3.4 to Proxmox 5, and migrated the openVZ VM (never any issues there, rock solid) to LXC about 5 weeks ago.
Any help is highly appreciated!
Here's a little info, let me know should you need more:

root@proxmox:~# pveversion -v
proxmox-ve: 5.0-21 (running kernel: 4.10.17-3-pve)
pve-manager: 5.0-31 (running version: 5.0-31/27769b1f)
pve-kernel-4.10.17-2-pve: 4.10.17-20
pve-kernel-4.10.17-3-pve: 4.10.17-21
libpve-http-server-perl: 2.0-6
lvm2: 2.02.168-pve3
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-12
qemu-server: 5.0-15
pve-firmware: 2.0-2
libpve-common-perl: 5.0-16
libpve-guest-common-perl: 2.0-11
libpve-access-control: 5.0-6
libpve-storage-perl: 5.0-14
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-2
pve-docs: 5.0-9
pve-qemu-kvm: 2.9.0-5
pve-container: 2.0-15
pve-firewall: 3.0-2
pve-ha-manager: 2.0-2
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.0.8-3
lxcfs: 2.0.7-pve4
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.6.5.11-pve17~bpo90

pct config 102
arch: amd64
cores: 2
description: ISPConfig%0AApplicationserver%0A
hostname: ohoco-host.ohoco.de
memory: 12288
net0: name=eth0,bridge=vmbr1,firewall=1,gw=xxx.x.xx.xx,hwaddr=xx:xx:xx:xx:xx:xx,ip=xxx.xx.xx.yyy/29,type=veth
onboot: 1
ostype: debian
parent: vor_removeacl
rootfs: local-lvm:vm-102-disk-2,acl=0,quota=1,size=300G
swap: 5120

thanks a ton
Sascha

 

[tafkaz]

Hi,
just wondering...noone has any idea?
This is urgent, really...
Our VM freezes (only some ports like 25 and 587 not reachable, others still working) every 2 days the latest...
Please help us, thanks
Sascha

 

[Bien]

Hi there,

we're experiencing the same error message here with our LXC VM.
Additionally this VM will crash completely everey 4-5 days, all by a sudden.
The VM holds an ISPConfig guest, running mysql dovecot, postfix and apache services.
So, when the freezing happens, no mail services are reachable from one moment to another.
We're really desperate now, as we cannot see any reason for this.
The problem started right after we switched from Proxmox 3.4 to Proxmox 5, and migrated the openVZ VM (never any issues there, rock solid) to LXC about 5 weeks ago.
Any help is highly appreciated!
Here's a little info, let me know should you need more:

root@proxmox:~# pveversion -v
proxmox-ve: 5.0-21 (running kernel: 4.10.17-3-pve)
pve-manager: 5.0-31 (running version: 5.0-31/27769b1f)
pve-kernel-4.10.17-2-pve: 4.10.17-20
pve-kernel-4.10.17-3-pve: 4.10.17-21
libpve-http-server-perl: 2.0-6
lvm2: 2.02.168-pve3
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-12
qemu-server: 5.0-15
pve-firmware: 2.0-2
libpve-common-perl: 5.0-16
libpve-guest-common-perl: 2.0-11
libpve-access-control: 5.0-6
libpve-storage-perl: 5.0-14
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-2
pve-docs: 5.0-9
pve-qemu-kvm: 2.9.0-5
pve-container: 2.0-15
pve-firewall: 3.0-2
pve-ha-manager: 2.0-2
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.0.8-3
lxcfs: 2.0.7-pve4
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.6.5.11-pve17~bpo90

pct config 102
arch: amd64
cores: 2
description: ISPConfig%0AApplicationserver%0A
hostname: ohoco-host.ohoco.de
memory: 12288
net0: name=eth0,bridge=vmbr1,firewall=1,gw=xxx.x.xx.xx,hwaddr=xx:xx:xx:xx:xx:xx,ip=xxx.xx.xx.yyy/29,type=veth
onboot: 1
ostype: debian
parent: vor_removeacl
rootfs: local-lvm:vm-102-disk-2,acl=0,quota=1,size=300G
swap: 5120

thanks a ton
Sascha

Hi Sascha,

Do you have an update on this? im also having a problem when i switch to other vmbr's i also upgraded from 3.4 to 5.1? I've also noticed when i spin up a ubuntu container it has a problem on its network.

 

[tafkaz]

Hi Bien,

no not really. We had the PVE Support look into this, but they found no issues on PVE side.
Our problem seem to be related to some misconfiguration of dovecot...we're still working on it. For now, we force the vm to be restarted every morning...so we don't get alarmed by a non working mailserver anymore.
still not completely convinced we don't have a network issue with lxc here...