Can't do anything with container

dignus

Renowned Member
Feb 12, 2009
157
11
83
Hi,

I've had an issue where a LXC CT locks for the 2nd day in a row when the backup process starts (snapshot). The backup actually never starts, it just hangs. Killing the backup job brings the CT back online.

So I thought that maybe stop/start the CT would help. However.. the stop process just never ends, it doesn't timeout, no error, it's just working. Services in the CT are down though.
I killed the process after an hour:

root@prox1:/tmp# pct stop 100
^Ccommand 'lxc-stop -n 100 --kill' failed: received interrupt


The CT appears to be running:

root@prox1:/tmp# pct list
VMID Status Lock Name
100 running mysql2.domain.com


Any ideas what can be done? I tried stop/starting the pve-cluster service (as recommended in other threads), but no luck.

This is a cluster of 4 nodes, all running CT's. No HA.

root@prox1:/tmp# pveversion -v
proxmox-ve: 4.2-48 (running kernel: 4.4.6-1-pve)
pve-manager: 4.2-2 (running version: 4.2-2/725d76f0)
pve-kernel-4.4.6-1-pve: 4.4.6-48
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 1.0-1
pve-cluster: 4.0-39
qemu-server: 4.0-72
pve-firmware: 1.1-8
libpve-common-perl: 4.0-59
libpve-access-control: 4.0-16
libpve-storage-perl: 4.0-50
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.5-14
pve-container: 1.0-62
pve-firewall: 2.0-25
pve-ha-manager: 1.0-28
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u2
lxc-pve: 1.1.5-7
lxcfs: 2.0.0-pve2
cgmanager: 0.39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5-pve9~jessie
 
Hi,

please update to the current version, there are many improvements what affect lxc.
 
Hi,

please update to the current version, there are many improvements what affect lxc.

I too have same issue, I'm running latest version already, how do I kill the pct? pct list shows running, tried lxc-stop -W -k still running for hours, not actually stopping it. Tried shutdown from GUI and error "TASK ERROR: command 'lxc-wait -n XXX -t 5 -s STOPPED' failed: exit code 1"

# pveversion -v
proxmox-ve: 4.4-79 (running kernel: 4.4.35-2-pve)
pve-manager: 4.4-12 (running version: 4.4-12/e71b7a74)
pve-kernel-4.4.35-2-pve: 4.4.35-79
pve-kernel-4.2.2-1-pve: 4.2.2-16
lvm2: 2.02.116-pve3
corosync-pve: 2.4.2-1
libqb0: 1.0-1
pve-cluster: 4.0-48
qemu-server: 4.0-109
pve-firmware: 1.1-10
libpve-common-perl: 4.0-92
libpve-access-control: 4.0-23
libpve-storage-perl: 4.0-73
pve-libspice-server1: 0.12.8-1
vncterm: 1.3-1
pve-docs: 4.4-3
pve-qemu-kvm: 2.7.1-3
pve-container: 1.0-94
pve-firewall: 2.0-33
pve-ha-manager: 1.0-40
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u3
lxc-pve: 2.0.7-3
lxcfs: 2.0.6-pve1
criu: 1.6.0-1
novnc-pve: 0.5-8
smartmontools: 6.5+svn4324-1~pve80
zfsutils: 0.6.5.9-pve15~bpo80

# ps ax | grep lxc | grep 166
4464 ? Ss 1:10 [lxc monitor] /var/lib/lxc 166
7736 pts/401 S+ 0:00 lxc-stop -n 166 -W -k
28259 ? S 0:00 lxc-stop -n 166 --kill

When trying to enter it, error

# pct enter 166
lxc-attach: attach.c: lxc_attach_to_ns: 270 No such file or directory - Failed to open namespace: "mnt".
lxc-attach: attach.c: lxc_attach: 1005 Failed to enter namespaces.
 

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!