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
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
