impossible to stop vm

[daarksim]

Hi,

when I try to enter, stop or shutdown my ct, I cannot do anything (because of file lock ?)
"can't lock file '/run/lock/lxc/pve-config-101.lock' "
I already try to restart the pve-cluster and impossible to restart the pct.
Has anyone got the same problem ?

Thank you in advance for your help

Regards

I also tried pct unlock 101

root@ns3046075:/run/lock/lxc# ps ax | grep vz
31838 pts/23   S+     0:00 grep vz
root@ns3046075:/run/lock/lxc# ps ax | grep dum
31943 pts/23   S+     0:00 grep dum
root@ns3046075:/run/lock/lxc# ps ax | grep pct
31957 pts/23   S+     0:00 grep pct

pct enter 101
lxc-attach: attach.c: lxc_attach_to_ns: 269 No such file or directory - failed to open namespace: 'mnt'.
                                                                                                        lxc-attach: attach.c: lxc_attach: 1004 failed to enter the namespace

I use my server yesterday and it was working perfectly

Ok the lock is remove but :

pct enter 101
lxc-attach: attach.c: lxc_attach_to_ns: 269 No such file or directory - failed to open namespace: 'mnt'.
lxc-attach: attach.c: lxc_attach: 1004 failed to enter the namespace

root@ns3046075:/run/lock/lxc# lxc-info --name 101
Name: 101
State: RUNNING
PID: 7919
lxc-info: utils.c: switch_to_ns: 1140 No such file or directory - failed to open /proc/7919/ns/net
lxc-info: lxccontainer.c: do_lxcapi_get_ips: 1889 No such file or directory - failed to enter namespace
CPU use: 17389.16 seconds
Memory use: 119.46 MiB
KMem use: 0 bytes
Link: veth101i0
TX bytes: 108.62 MiB
RX bytes: 416.13 MiB
Total bytes: 524.76 MiB
root@ns3046075:/run/lock/lxc#

and I cannot stop it



Ok it's solved, then the solution :

first try to unlock the pct :
pct unlock 101
if it works just stop and start again the vm

if it does'nt work (my case) try to stop with this
lxc-stop --name 101
if it's does'nt work (my case) you can force stop with kill command

ps ax | grep lxc
then kill the process with your id (101 for me) kill pid (replace pid by the process name)

after that you can just launch again you'r vm