Can't stop container - lock file does not exist?

fribse

New Member
Feb 2, 2022
3
1
3
55
Proxmox version 6.4-13

I'm trying to shutdown a container and the shutdown just keeps showing as 'working'.
I also tried a stop, and that tells me it can't lock file /run/lock/lxc/pve-config-106.lock
Looking in that folder, the file doesn't exist.

I tried looking at the processes:

Code:
root@pve:~# ps aux | grep 106
root       106  0.0  0.0      0     0 ?        I<   Feb02   0:00 [acpi_thermal_pm]
root      2015  0.0  0.0   7428  4308 ?        Ds   Feb02   0:02 /usr/bin/lxc-start -F -n 106
root      2972  0.0  0.0   2400  1480 ?        Ss   Feb02   0:00 /usr/bin/dtach -A /var/run/dtach/vzctlconsole106 -r winch -z lxc-console -n 106 -e -1
root      2973  0.0  0.0   7284  3640 pts/4    Ss+  Feb02   0:00 lxc-console -n 106 -e -1
root     23288  0.0  0.3 364236 125492 ?       Ss   04:47   0:00 task UPID:pve:00005AF8:002EF95B:61FB5069:vzshutdown:106:root@pam:
100000   25208  0.0  0.0 103912 10656 ?        Ss   04:52   0:00 /sbin/init
100106   25351  0.0  0.0  23956 12100 ?        Ss   04:52   0:00 /lib/systemd/systemd-resolved

I can see that others mention NFS mounts, it does have nfs mounts from a NAS, but I'm not sure how to unmount them, as the console is just blank.
 
Last edited:
hi,

firstly try to stop the "Shutdown" task (double click it in the tasklog then select stop).

I can see that others mention NFS mounts, it does have nfs mounts from a NAS, but I'm not sure how to unmount them, as the console is just blank.
could you post the container config from /etc/pve/lxc/CTID.conf (CTID = 106 for you)

if you just want to stop the container you can try:
1. pct stop 106 --skiplock (should skip the locking part)
2. if that doesn't work, you can just kill the process /usr/bin/lxc-start -F -n 106 by running kill -9 PID (where PID = 2015 according to your ps aux), but beware that this is basically a forced kill!

Proxmox version 6.4-13
you should upgrade to the latest 7.x when you get a chance [0]

hope this helps!

[0]: https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0
 
Hi @oguz


Thanks for getting back to me :D, the config looks like this:

Code:
arch: amd64
cores: 2
features: mount=fuse,nesting=1
hostname: plex
memory: 2048
nameserver: 10.11.14.1
net0: name=eth0,bridge=vmbr0,gw=10.11.14.1,hwaddr=9E:2C:40:B8:F4:B7,ip=10.11.14.9/24,tag=60,type=veth
onboot: 1
ostype: ubuntu
rootfs: LVM2:vm-106-disk-1,size=70G
searchdomain: fribert-iot.local
swap: 4096
lxc.cgroup.devices.allow: c 226:0 rwm
lxc.cgroup.devices.allow: c 226:128 rwm
lxc.cgroup.devices.allow: c 29:0 rwm
lxc.autodev: 1
lxc.hook.autodev: /var/lib/lxc/106/mount_hook.sh
lxc.mount.entry: /dev/fuse dev/fuse none bind,create=file 0 0
lxc.cap.drop:
lxc.cap.drop: mac_override sys_time sys_module sys_rawio

The kill of the process worked, it is down now.
The container is a plex server, so it has ties to the onboard intel graphics card, that's why there are some extra fiddly stuff in the config.

Ahh, yes upgrade, thankyou very much for the link, I hope I can get some time to it during this weekend.
I think I'm going for a reinstall :cool: just to make sure that the pve is on one disc, and the vm's are on another (bigger ssd).
 
  • Like
Reactions: oguz

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!