Skip to main content

Open VZ cheat Sheet


VZCTL COMMANDS
---------------------

vzctl set 101 --diskspace 1000000:1100000 --save  To set diskspace for container with ID 101

vzctl set 101 --diskinodes 90000:91000 --save     To set inodes for container with ID 101

vzctl set 101 --quotatime 600 --save              To set quotatime for container with ID 101 (The time limit by

                                                       which container is allowed to temporarily exceed  its quota soft limits)

vzctl exec 101 df                                  To execute command df at the server with the CTID 101

vzctl set 101 --quotaugidlimit 100 --save          Set number of user/group id's allowed for internal disk
                                                                     quota,if 0 UID/GUID quota will not be allowed\

 vzctl set 0 --dcachesize 5G --save        Set dcachesize of the hardware node

sysctl fs.fsync-enable=0     or  echo 0 > /proc/sys/fs/fsync-enable        disable fsync calls inside containers .

Add the  two lines to /etc/sysctl.conf to make permanent across reboots

#disable fsync() calls inside Containers
fs.fsync-enable=0


sysctl fs.file-max=1048576 kernel.pid_max=262144        change kernel.pid_max and fs.file-max

~# vzup2date -m batch install --loader-autoconfig       update virtuozzo installation using Parallels update
                                                                                      utility


vzps auxwwff -E ${CTID}           Check the process list for a particular container

How to locate vzagent.conf ?

-----

All PVA Agent configuration files are located in etc_folder defined in pva.conf.

Check /opt/pva/agent/bin/pva.conf and find the etc_folder section:

etc_folder

/vz/pva/agent/etc

It means that the main configuration file vzagent.conf is located in /vz/pva/agent/etc.


vzctl create VEID [--ostemplate <name>] [--config <name>]  To create a container

vzctl exec 101 /etc/init.d/sshd status

vzpkgls - To display the templates present in the server

vzctl destroy 101 -  To destroy a VPS with VEID 101

vzctl set 101 --hostname test101.my.org --save  -- To set hostname

vzctl start/stop/restart/enter 101    To start/stop/restart/enter container with ID 101

vzctl set 101 --cpus 2 --save  To set two cpus under the container 101

vzctl set 101 --ipadd 10.0.186.1 --save   -- To add an IP address

vzctl set 101 --ipdel 10.0.186.1 --save    -- To delete an IP address

vzctl set 101 --nameserver 192.168.1.165 --save  --To set the name servers

vzctl set 101 --userpasswd root:password -- To set the root password of VPS 101

vzctl start 101 --force  -- To start a disabled VPS

Popular posts from this blog

Qmail cheat sheet

http://supportlobby.com/blog/category/technical/qmail-technical/

========================
1) To check the mail queue in plesk from command line, you can use the command :

 /var/qmail/bin/qmail-qstat
========================

=========================
2) You can examine the queue with qmail-qread.

/var/qmail/bin/qmail-qread
=========================

=========================
3) From the qread command you get the message id . In the above example , let us assume one of the id is 524514 . Now you can find the file holding the email in/var/qmail/queue with find command.

# find /var/qmail/queue -iname 524514

/var/qmail/queue/remote/22/524514

/var/qmail/queue/mess/22/524514 (mail headers)

/var/qmail/queue/info/22/524514

4) From the mail header you get the IP address

vi /var/qmail/queue/mess/22/524514


Or

Shortcut for the cool guys
---------------------------------

find /var/qmail/queue -iname queu_id | grep mess | xargs less

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

=========================
4) If you wish …

Logical volume vmxxxx_img is used by another device - Error on LVM removal

Hi Folks,

I've faced error while trying to remove an LVM from the server.

The exact LVM error will be "Logical volume vmxxxx_img is used by another device" on executing the lvremove command.

Feel free to remove the following steps to remove the LVM from the server.

Note: Please remember to replace <id> with your VMID in the below section.

----------------------------------------------------------
dmsetup ls dmsetup info -c xen-vm<id>_img dmsetup remove xen-vm<id>_img lvremove -f /dev/xen/vm<id>_img ----------------------------------------------------------

File system corrupted on the OpenVZ container.

It happens rarely but when it does, it is hard to handle. The OpenVZ VM's are usually stable in nature, but I've encountered situations where OpenVZ VM was showing file system error and was refusing to start.

You can follow the below steps to recover the VM.


1. ~# vzctl stop ctid

2. # ploop mount /vz/private/ctid/root.hdd/DiskDescriptor.xml
3. now do a df -h and you will get the ploop id for the VM.
4. fdisk -l /dev/ploop12345
5. e2fsck /dev/ploop12345p1
6. ploop umount -d /dev/ploop12345
7. vzctl start ctid