OpenVZ

Container already locked

http://wiki.openvz.org/Container_already_locked

If you received this message when you try and stop the VE...

[root@server ~]# vzctl stop 104
Container already locked

Here's how to fix it:

    * Delete the lock file

[root@server ~]# rm /vz/lock/104.lck
rm: remove regular file `/vz/lock/104.lck'? y

    * Kill the checkpoint

[root@server ~]# vzctl chkpnt 104 --kill
Killing...

================================================

vzquota : (error) can't lock quota file, some quota operations are performing for id 101
vzquota on failed [7]


vzquota off 101
vzquota on 101

or I think you need to wait until the quota operations gets completed for this VE or you can reboot the Node.

===================================================
Unable to fork: Cannot allocate memory

You see a message â~@~\Unable to fork: Cannot allocate memoryâ~@~] while logging to a VPS from the host server. The reason is the VPS is running out of resources especially RAM. To temporary solve the issue, you may restart the VPS by executing

    vzctl restart VEID

OR increase RAM for the VPS by increasing privvmpages and kmemsize for the VPS.

Edit the configuration file of the VPS

    vi /etc/sysconfig/vz-scripts/veid.conf

increase the value of the above two parameters and restart the VPS.

http://linuxhostingsupport.net/blog/unable-to-fork-cannot-allocate-memory

======================================================
Unable to open pty: No such file or directory


You may receive the following message on entering a VPS:

# vzctl enter 101

enter into VE 101 failed
Unable to open pty: No such file or directory

The reason behind this is the missing tty/pty files . You can create it using the MAKEDEV program, execute the following commands on the host server ( main node ).

# vzctl exec VEID /sbin/MAKEDEV tty
# vzctl exec VEID /sbin/MAKEDEV pty

Replace VEID with your actual vps id . In our example its 101 .

Restart vps .

#vzctl restart VEID

Thats a temporary fix. To Fix this issue permanently follow the below steps after entering to your vps client node (101 in our case) .

1) #vzctl enter VEID

2) Edit the file /etc/rc.sysinit

3) Comment the line
#/sbin/start_udev

4) Add the following lines after /sbin/start_udev:
/sbin/MAKEDEV tty
/sbin/MAKEDEV pty

5) Reboot your VPS client node .
vzctl restart VEID

You can also access the file /etc/rc.sysinit for the node 101 from the main VPS node . It should be from /vz/private/VEID/etc/rc.sysinit .

You can also try the below steps by updating the startup files

# vzctl exec VEID update-rc.d -f udev remove
# vzctl restart veid

Above fixes may not work for ubuntu servers . In that case you can try the below command

# vzctl exec VEID â~@~Xdpkg â~@~Sforce-depends â~@~Spurge udevâ~@~Y
=============================================


    Unfortunately no, it is not possible to upgrade your OS to the next version successfully since Virtuozzo Containers share such core resources across all VPS containers on the host machine.

=============================================
Starting container ...
vzquota : (error) Quota on syscall for id 60690: Device or resource busy
vzquota : (error)       Possible reasons:
vzquota : (error)       - Container's root is already mounted
vzquota : (error)       - there are opened files inside Container's private area
vzquota : (error)       - your current working directory is inside Container's
vzquota : (error)         private area
vzquota : (error)       Currently used file(s):
/vz/private/60690/home/ofertade/public_html/cache/t3/d0ee01f353010557e03721f71775cf11.php_expire
vzquota on failed [3]
Fix:

[root@ovz-bolin ~]# lsof 2> /dev/null | egrep '/vz/root/60690|/vz/private/60690'

==> Kill all processes listed after execute above command

==> Restart container.
===============================================================