Search

Language:  
Search for:

Available article translations:

How do I (re)create Service Container?

APPLIES TO:
  • Parallels Virtuozzo Containers for Linux 4.0
  • Virtuozzo for Linux 3.x

WARNING

This article applies to Parallels Virtuozzo Containers for Linux 3.0 and 4.0 only.
Parallels Containers 4.6 has a service container with the only process to enable offline management and this article will not work for version 4.6.
Instead of recreating service containers, it is possible to reinstall the PVA Agent on the Parallels Containers 4.6 host.

Refer to these articles for more details:
6965 Service Container has only single 'init' process
9445 How to install/reinstall/upgrade to PVA 4.6 Agent on a PVC 4.x for Linux HW Node

Resoluiton

If you are using Parallels Infrastructure Manager (PIM), please make sure that you have the recent backup of your PIM infrastructure, as described in the article How to backup and restore Parallels Infrastructure Manager.

You may create the Service Container on a Parallels Virtuozzo Containers hardware node using 'vzsveinstall' utility:
# vzsveinstall -D DISTRIB_DIR -s SERVICE_CT_IP

where
- DISTRIB_DIR - path to Virtuozzo distribution directory hierarchy on a server. F.e. if you have the Virtuozzo distributive on your server in the directory /root/Rel400 then DISTRIB_DIR should be /root/Rel400/;
- SERVICE_CT_IP - IP address to be assigned to Service Container;

If you have downloaded Virtuozzo distributive already (example for 64-bit PVC 4.0) as file "virtuozzo-4.0.0-${build_version}-x86_64.sfx", please extract it in the following way:
# mkdir -p /vz/full_distr
# bash /path/to/virtuozzo-4.0.0-${build_version}-x86_64.sfx -d /vz/full_distr --extract

You may then create the Service Container using this command  (make sure the old Service Container #1 does not exist):
# vzsveinstall -v -D /vz/full_distr -s SERVICE_CT_IP

Please refer to the main page on 'vzsveinstall' utility for additional information.

Please note - OS template 'redhat-as3-minimal' must be installed on a hardware node and cached before the Service Container may be created. If you have not installed the template on a node, please do the following:
- install OS template 'redhat-as3-minimal', corresponding RPM package is located in the folder 'virtuozzo/SVE' inside Virtuozzo distrib (in Virtuozzo 3.x it is the folder 'HW/SVE');
- create OS template cache using 'vzpkgcache' command on a node.

Please make sure you have the latest version of the OS template 'redhat-as3-minimal' installed on the hardware node before Service Container re-creation, e.g.:
# vzpkgls | grep minimal

The latest versions of the 'minimal' OS template are the following:

Virtuozzo 3.0: 20050622
Parallels Virtuozzo Containers 4.0: 20080630


You may run 'vzup2date', and update your node. For a manual update, please find 'minimal' template in /vz/vzup2date directory and install it using 'rpm -Uhv path_to_minimal_template_rpm_package' command, e.g. for 64-bit PVC 4.0:
# rpm -Uhv /vz/vzup2date/4.0.0/TU-4.0.0-438/redhat-as3-minimal-x86_64-p5nfs-tmpl-4.0.1-3.swsoft.x86_64.rpm

If the Virtuozzo server has been updated since the very first release (using 'vzup2date' utility or manually), then you need to apply all needed updates to the Service Container as well. Updates downloaded by 'vzup2date' utility are usually located under /vz/vzup2date/3.0.0/TU-3.0.0-* dirs on a Virtuozzo server. You may apply them to the Service Container using 'vzsveupgrade' utility using following two commands:
# find /vz/vzup2date/virtuozzo -path "*/$(awk '{gsub(/-.*$/,"",$NF);print $NF}' /etc/virtuozzo-release)/*/virtuozzo-tools*$(uname -i)*" -printf "%h\n" |sort -u |xargs -rn1 vzsveupgrade -d

# find /vz/vzup2date/pim -path "*/$(awk '{gsub(/-.*$/,"",$NF);print $NF}' /etc/virtuozzo-release)/*/virtuozzo-tools*$(uname -i)*" -printf "%h\n" |sort -u |xargs -rn1 vzsveupgrade -d

If you need to re-create the Service Container, then you may destroy the existing one using 'vzctl destroy 1' command (container must be stopped first), then create it from the scratches and apply available updates as it is described above.

The main point is to have the packages 'vzagent-opcontrol' (on the node) and 'vzagent-srvcontrol' (inside service container) with the same version/release:
# rpm -q vzagent-opcontrol; vzctl exec 1 rpm -q vzagent-srvcontrol

Example of the output for Virtuozzo 3.0:

vzagent-opcontrol-3.0.0-21.2.swsoft
vzagent-srvcontrol-3.0.0-21.2.swsoft


Example of the output for Parallels Virtuozzo Containers 4.0:

vzagent-opcontrol-4.0.0-483.swsoft
vzagent-srvcontrol-4.0.0-483.swsoft

Additional information

For more information about obtaining full distribution please refer to this article:
10043 How to download full distribution of Parallels Containers for Linux



9b9439294978ca011521bd467a069524 909d99074e442b52ce54cc7b31cf065d eb0ea3b827d18de2329b6477e24c1d59 9bccb04d0396d587d8123e5e12b4740e 2897d76d56d2010f4e3a28f864d69223

FEEDBACK
Was this article helpful?
Tell us how we may improve it.
Yes No
 
 
 
 
 
 
Server Virtualization
- Parallels Cloud Server
- Parallels Containers for Windows 6.0
- Parallels Virtuozzo Containers
Automation
- Parallels Automation
- Parallels Automation for Cloud Infrastructure
- Parallels Business Automation Standard
- Parallels Virtual Automation
- Parallels Plesk Panel Suite
- Web Presence Builder
- Parallels Plesk Automation
- Parallels Small Business Panel
- Value-added Services for Hosters
- Parallels Partner Storefront
Services & Resources
- Cloud Acceleration Services
- Professional Services
- Support Services
- Training & Certification