Run-Time error on VPS:


The Virtuozzo Control Center Director service is stopped inside the Service VE (SVE).

You should restart the Virtuozzo Control Center Director service using the following commands from the Hardware Node.

Commands to restart the Node

vzctl exec 1 net stop vzcpd
vzctl exec 1 net start vzcpd

http://kb.parallels.com/en/1303          Click

VZ agent restart

net stop vzaop
net start vzaop


Adding VPN to windows Virtuozzo:

Virtual Private Network (VPN) is a technology allowing you to establish a secure network connection over an insecure public network. In Virtuozzo 3.5.1 SP1 or greater, you can make Virtual Environments operate as VPN clients connecting to VPN remote access servers.

By default, the VPN support inside a VE is disabled. However, you can use the –vpn option of the vzctl set command to enable a VE to take advantage of the VPN technology benefits.

VPN support can be enabled by running the following command:

C:\…\Administrator>vzctl set 101 – -vpn on – -save
Command ‘set’ is successfully finished
C:\…\Administrator>vzctl restart 101

To check that the VPN support is now turned on inside VE 101, run the following command: (101=>Container ID)

C:\…\Administrator>vzlist -o nettype 101

VPN support can be disabled by running the following command:

C:\…\Administrator>vzctl set 101 – -vpn off – -save
Command ‘set’ is successfully finished

Note: This option supports only Microsoft VPN.

http://kb.parallels.com/en/1601     Click

http://www.switchlink.co.uk/blog/wiki/how-to-add-vpn-to-windows-virtuozzo.html   Click

http://forum.parallels.com/showthread.php?t=83481     Click


Command to list-out the Master and Slave VPS  Nodes:

Type the following command in the run prompt.

C:\Users\Administrator>vzagroup list

Queue size can be edited in the vzagent.conf


The following ports should be opened on Virtuozzo  hardware node & Service VE:

  • 4433 – TCP VZAgent non-crypted XML connections to VZAgent
  • 4434 – TCP VZAgent SSL (crypted) XML connections to VZAgent
  • 4435 – TCP VZAgent binary data transfer connections to VZAgent
  • 4646 – TCP VZAgent SOAP
  • 4643 – Parallels Infrastructure Manager
  • 80 – HTTP redirect for Parallels Infrastructure Manager
  • 443 – Parallels Infrastructure manager
  • 22* – SSH. Used in case when Service CT is created in compat mode
  • 8443, 8080 – Plesk integration
  • 3389 – Remote Desktop

The above ports can be enabled and disabled by using the appropriate commands.

http://virtualadmins.blogspot.com/2009_06_01_archive.html     Click


FTP uploads break randomly:

After uploading large files via FTP connection hangs and can be restored only after reconnection. While  connecting the vps container  via FTP  which results. It could not connect to server.

Application Layer Gateway Service causes this problem.
Stop Application Layer Gateway Service and switch start up mode to Disabled.

Most important commands to work with VPS:
To check the Net Type:
“C:\Documents and Settings\Administrator>”  vzlist -a -o veid,nettype
To disable NAT:
“C:\Documents and Settings\Administrator>” vzctl set 101 – -nat off – -save
NSlookup command to check reverse DNS:
From Container:
“C:\Parallels\Plesk\admin\bin>” nslookup ns1.nameserver.net.
From HW Node:
“C:\Documents and Settings\Administrator>” nslookup ns1.nameserver.net. IP
Audio not working on VPS:

Steps to enable sound on the virtual server.
Enabling sound in a widows virtual server or virtual desktop is very easy.
It involves making a change to the terminal server configuration and then logging off and back on.
This document will detail the steps necessary to enable sound in your remote desktop sessions.To enable sound inside VE you have to login inside VE and go to
Start–>Programs->Administrative tools–> Terminal Services Configuration MMC.
From this screen, select the RDP-TCP connection and right mouse click on it.
From the displayed submenu, select Properties. On the Client Settings panel, you will uncheck the ‘Disable Audio mapping’ checkboxAs stated this is done and sound is now working for your VPS server. 

VPS Container Locked Error:
You will come across the  error while working on the VPS “ERROR:VPS 205 is already locked”.
  • Follow the steps one by one and the issue will get fixed in any of the steps.
  • Restarting the hardware node VE may fixes this issue. To unlock VE in this case , please restart VZAOP service on hardware node. It can be done with the following commands:
net stop vzaop
net start vzaop
  • Migrating the container ID may fixes this issue
vzmlocal OLD_ID:NEW_ID
where OLD_ID is the container id of the container that you cant start and the NEW_ID is a new id you choose that is not already in use. This might help you start the container with the NEW_ID.
  • If  any of the above steps didn’t fixes the issue. Finally follow the below steps to fix the issue.
  1. Start the cmd on the hardware node hosting the container that is locked.
  2. vzctl stop <ct#>
  3. The normal answer is that the container cannot be stopped because it is locked.
  4. vzctl stop <ct#> –skiplock
  5. It will run and bring up maybe some errors.
If the container is still down don’t worry. continue the steps given below.
6. vzctl stop <ct#> –skiplock
7. it should tell you that the container is not running.
8.  vzctl start <ct#> –skiplock
How to find IP pools in VPS:
IP pool is found in vz manager.
Just open vz manager local >> network >> right click >> ip pool
VPS Command details:
Configuring Master and slave nodes in VPS:

If you have to add the VPS nodes as a slave in the master. Use the following steps to do so.
Infrastructure ==> Hardware Nodes ==> New Hardware Node
Fill the IP address and login credentials of the remote hardware node and register.
Now the main node acts as a master and the remote nodes added to it acts as a slave.

How to backup and restore Parallels Infrastructure Manager:

Backup of PIM is very important. If we face any disaster or corruption of PIM. It  can be easily resolved by restoring the backup.
Before starting backup procedure make sure that Service Container #1 is stopped.
The scripts are located in “C:\Program Files\SWsoft\Virtuozzo\VZAgent\bin” folder on x86 system and “C:\Program Files (x86)\SWsoft\Virtuozzo\VZAgent\bin” folder on x64 system.
To back up the PIM installation the following command is used:
cscript pimBackupData.vbs <backup_folder>

To restore the PIM installation, the following command is used:

cscript pimRestoreData.vbs [--force] <backup_folder>

A backup is created in the folder you specify after pimBackupData.vbs as <backup_folder>. To restore the created backup, it is necessary to specify the path to this folder after pimRestoreData.vbs.

cscript pimBackupData.vbs C:\PIMBackup\
So the backup of PIM is stored in the folder PIMBackup. Use the same folder path while restoring the PIM backup.

Service Container reinstallation:
Command to disable the firewall for particular container:
vzctl exec 1429 netsh firewall set opmode disable

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s