"VPs is locked" error

Solution
During VPs startup, stop, backup, recovery, and other typical operations, the VPs will be locked first.
When the VPs is locked, the VPs cannot beProgramOperated
To avoid conflicts between other operations and the current operation
After the operation is completed, the lock is automatically released.

For example, you can perform backup operations when the VPs is running or when the VPs is stopped.
However, when the VPs is locked, backup and other operations cannot be performed.
VPs locking is a security protection when necessary

Take start and stop as an example. If a program is stuck and locked during startup, it cannot be started or exited normally.
The entire VPs may be stuck.
For the VPs itself, because an internal program is stuck, the VPs cannot skip this step and it cannot start smoothly.
For the worker ozzo node, the VPs is locked because the startup is not completed. Other programs cannot perform other operations on the VPs.
At this time, the error message "VPs is locked" occurs.

To solve this problem, you need to log on to the hardware node, find the program that is stuck with the VPs, and kill the faulty process.
In this way, the VPs can continue to start, stop, and other operations.
If you do not kill an erroneous process, in theory, you only need to wait for a long enough time to cause a timeout (timeout) for the problematic process)
The VPs will automatically exit the locked state and return to the normal state.
However, in many cases, waiting for dozens of minutes may not be able to return to normal, so the process is suspended manually.

For example, if vps101 is locked on the server, log on to the hardware node.
Run the vzlist-a command to check the current VPs list and process. The following result is displayed:

C: \> vzlist-
Veid nproc status ip_addr hostname
1 24 running 192.168.1.1 vps1
101 2 stopped 192.168.1.2 vps23
102 35 running 192.168.1.3 pleskwin761
C: \>

The "nproc" Number of VPs 101 is 2, that is, "Number of processes". The number of processes currently running is 2.
Generally, if the VPs is in the stopped status, the value should be 0. If the VPs is in the running status, the value should be more than 20.
Only two processes indicate that an error may be stuck during VPs startup, leading to an error in VPS locking.

Run the vzquery V2s command to check the problematic VPs session ID.
For example, for VPs with VPs ID 101, run

C: \> vzquery V2s 101
Virtual Private cloud (VPs) ID: 101
Session ID: 2 (Root)
Session ID: 2
C: \>

It can be obtained that all session IDs (session ID 2) belong to vps101.
Now, log on to the hardware node, open the task manager, and kill all processes whose session IDs are 2.

By default, the task manager may not be able to list the session ID project. You can click "View" in the Task Manager menu"
Click "Select column". A list of options is displayed, and the second-to-last item on the left side shows the "session ID ".
Select the session ID and click OK. The session ID of each process can be listed in task manager.
Click the title bar of the session ID, and sort by the number of the session ID.
Now we can list all processes whose session IDs are 2.

In the process where the list session ID is 2, some of the runners are system and some are non-system
Generally, as long as all processes with non-system identities are killed, VPs can be restored to normal.
If the VPs is locked during startup, after killing the problematic Process
Then, run the vzlist-a command to check that the number of processes started in VPS (NPOC) is increasing.
And changed to the running status.
If the VPs is locked during the stop process, after killing the problematic Process
Run the vzlist-a command to check that the VPs should be stopped successfully, and the number of processes (NPOC) is 0.
The VPs is stopped successfully.

when the VPs is unlocked, you can perform any operation on it.