LXC freeze

[einfachnuralex]

Hi,

i have problems with proxmox 4.1 and freezing lxc containers. I'm running several container from debian template (debina-8.0-standard_8.0-1_amd64.tar.gz) which is included in proxmox 4.x.

After approx. 3 days of uptime they partly freeze and cant be stopped from host. The process table of the proxmox hosts shows several process running in each container, most of freezing ones run cron.

I've attached a 'ps axjf' dumb which shows many running cron tasks and i think the problem are too many cron tasks at the same time. But i have no idea how to handle that.

Has anyone else these kind of problems?

Regards
alex

 

[Nemesiz]

I have simmilar problem after updated to

proxmox-ve: 4.1-39 (running kernel: 4.2.8-1-pve)
pve-manager: 4.1-15 (running version: 4.1-15/8cd55b52)
pve-kernel-4.2.8-1-pve: 4.2.8-39
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 1.0-1
pve-cluster: 4.0-33
qemu-server: 4.0-62
pve-firmware: 1.1-7
libpve-common-perl: 4.0-49
libpve-access-control: 4.0-11
libpve-storage-perl: 4.0-42
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.5-9
pve-container: 1.0-46
pve-firewall: 2.0-18
pve-ha-manager: 1.0-24
ksm-control-daemon: 1.2-1
glusterfs-client: 3.7.8-1
lxc-pve: 1.1.5-7
lxcfs: 2.0.0-pve1
cgmanager: 0.39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5-pve7~jessie
openvswitch-switch: 2.3.2-2

Have not saved version info before STABLE version.

Now I updated to

proxmox-ve: 4.1-39 (running kernel: 4.2.8-1-pve)
pve-manager: 4.1-22 (running version: 4.1-22/aca130cf)
pve-kernel-4.2.8-1-pve: 4.2.8-39
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 1.0-1
pve-cluster: 4.0-36
qemu-server: 4.0-64
pve-firmware: 1.1-7
libpve-common-perl: 4.0-54
libpve-access-control: 4.0-13
libpve-storage-perl: 4.0-45
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.5-9
pve-container: 1.0-52
pve-firewall: 2.0-22
pve-ha-manager: 1.0-25
ksm-control-daemon: 1.2-1
glusterfs-client: 3.7.8-1
lxc-pve: 1.1.5-7
lxcfs: 2.0.0-pve2
cgmanager: 0.39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5-pve7~jessie
openvswitch-switch: 2.3.2-2

I hope where will be no more problem. Otherwise I`ll be forced to move to KVM

 

[Nemesiz]

BTW after update I could not start one of my lxc vps.

# lxc-start -n 102 -F
got unexpected ostype (ubuntu != debian)
lxc-start: conf.c: run_buffer: 342 Script exited with status 255
lxc-start: start.c: lxc_init: 436 failed to run pre-start hooks for container '102'.
lxc-start: start.c: __lxc_start: 1170 failed to initialize the container
lxc-start: lxc_start.c: main: 344 The container failed to start.
lxc-start: lxc_start.c: main: 348 Additional information can be obtained by setting the --logfile and --logpriority options.

Don`t know why ostype started to not mach.

 

[Nemesiz]

another record

Mar 17 19:14:41 nmz-lt kernel: [380156.417291] Tainted: P O 4.2.8-1-pve #1
Mar 17 19:14:41 nmz-lt kernel: [380156.417298] ffff88007161bbe8 0000000000000086 ffff880c08a18000 ffff88000ef00dc0
Mar 17 19:14:41 nmz-lt kernel: [380156.417302] Call Trace:
Mar 17 19:14:41 nmz-lt kernel: [380156.417304] [<ffffffff812fb863>] request_wait_answer+0x163/0x280
Mar 17 19:14:41 nmz-lt kernel: [380156.417307] [<ffffffff812fba10>] __fuse_request_send+0x90/0xa0
Mar 17 19:14:41 nmz-lt kernel: [380156.417309] [<ffffffff81306128>] fuse_direct_io+0x3a8/0x5b0
Mar 17 19:14:41 nmz-lt kernel: [380156.417312] [<ffffffff813063d0>] fuse_direct_read_iter+0x40/0x60
Mar 17 19:14:41 nmz-lt kernel: [380156.417314] [<ffffffff811fd2c6>] __vfs_read+0x26/0x40
Mar 17 19:14:41 nmz-lt kernel: [380156.417316] [<ffffffff811fe7e5>] SyS_read+0x55/0xc0

 

[windinternet]

Did you guys look at this thread?

https://forum.proxmox.com/threads/pve-suddunly-stopped-working-all-cts-unrecheable.26458

 

[fabian]

Please provide the debugging output from page 2 of the linked thread, and test the updated lxcfs package from pvetest (also on page 2).

 

[einfachnuralex]

Thank you very much. I've installed the updated package, reboot and no problems for two days. I'm following the other thread.