trying to aquire lock...TASK ERROR: can't lock file '/var/lock/qemu-server/...

[fweber]

This one is new. You can check the checkbox "Overrule active shutdown tasks" if you have a shutdown task running. If checked it will kill the running shutdown task.

Yes, this was added in Proxmox VE 8.2 (more specifically, in pve-manager >= 8.2.0). See the feature request [1] for more information.

[1] https://bugzilla.proxmox.com/show_bug.cgi?id=4474

 

[alamoudi.moh]

i am stepping in into this, with even starting a container, the same issue happens.


i just started a created a container, and started it, i got the same ugly message, i was refreshing the desired page waiting for the LXC to load with no luck, then i went back to proxmox and

TASK ERROR: can't lock file '/run/lock/lxc/pve-config-100.lock' - got timeout

 

[fiona]

Hi,

i am stepping in into this, with even starting a container, the same issue happens.


i just started a created a container, and started it, i got the same ugly message, i was refreshing the desired page waiting for the LXC to load with no luck, then i went back to proxmox and

TASK ERROR: can't lock file '/run/lock/lxc/pve-config-100.lock' - got timeout

likely another task is already holding the lock. Please check the Task History of the container to see if there are any other running tasks and also check the output of fuser -vau /run/lock/lxc/pve-config-100.lock.

 

[alamoudi.moh]

Hi,

likely another task is already holding the lock. Please check the Task History of the container to see if there are any other running tasks and also check the output of fuser -vau /run/lock/lxc/pve-config-100.lock.

Thanks for the reply, however there is no task, it is newly created container in a newly created environment. I am crazy when it comes to testing, I rebuilt everything from scratch.

BTW, this is applied to all the containersni created.

Using 8.2.2

 

[fiona]

Thanks for the reply, however there is no task, it is newly created container in a newly created environment. I am crazy when it comes to testing, I rebuilt everything from scratch.

BTW, this is applied to all the containersni created.

Using 8.2.2

Are you sure the creation task is finished and there is not already a second start task? The fuser command should indicate what is holding the lock.

 

[alamoudi.moh]

Are you sure the creation task is finished and there is not already a second start task? The fuser command should indicate what is holding the lock.

i am sure and here is another example from another machine and here is the output, where i cannot shutdown the machine at all. it has ubuntu server 22.04

there is something wrong with Virtual Environment 8.2.4 or 8.2 in general,

USER        PID ACCESS COMMAND

 

[fiona]

Please share your system logs/journal from around the time the issue happens and the container configuration pct config 100, as well as the output of pveversion -v.

 

[shodan]

This is great, is it possible to make that checkbox checked by default ?

 

[gokhansonmez]

Hi,

This thread is google's first link for "proxmox can't lock file shutdown stop"

And this issue is still happenning very easily

I bang my head on it every time I haven't used proxmox in a couple months, trying to shutdown a VM and it won't so I just pull the server's power cord !

I think it's something about using shutdown not stop, or stop not shutdown
View attachment 55561
It's the sort of thing that every proxmox users and devs don't even think about or realize is soooooo frustrating

OK

First double click on that running broken task and hit stop
View attachment 55562
Now you can hit stop, NOT shutdown
View attachment 55563

And this could be made much easier, by changing proxmox's behaviour

If the user clicks STOP, stop previous still running shutdown tasks (as I've done manually here) and then execute the stop command

The problem is that the STOP command is getting queued behind the shutdown command which will never end.

Voila !

You are great, I am using Version 8.2.7 and the same problem still persists, I was able to restart my server after doing what you mentioned.