Article ID: 116718, created on Aug 12, 2013, last review on May 11, 2014

  • Applies to:
  • Operations Automation 5.4
  • Plesk
  • Virtuozzo
  • Virtuozzo containers for Linux
  • Virtuozzo hypervisor


Installing a Plesk 10 template to a container based on a number of distributions (Debian 6.0, Ubuntu 10.04, SuSE 11.4 and 12.1, CentOS/Redhat 5.x and 6.x) fails with a dependency check for the package psa-libxml-proxy:

~# vzpkg install 6464 .pp10 .pp10-webmail .pp10-vps-optimized .pp10-postfix
dpkg: dependency problems prevent configuration of psa-libxml-proxy:
 psa-libxml-proxy depends on plesk-core (>= 11.0.4); however:
  Version of plesk-core on system is 10.13.4-debian6.0.build1013111102.18.
 psa-libxml-proxy depends on plesk-base (>= 11.0.4); however:
  Version of plesk-base on system is 10.13.4-debian6.0.build1013111102.18.
dpkg: error processing psa-libxml-proxy (--configure):
 dependency problems - leaving unconfigured


The problem results from package naming for Plesk 10 and Plesk 11.0.x: both major Plesk releases have that package with the same version, and the packages are named in exactly the same way. However, the content differs, and the information about dependencies is different in those packages.

Thus, on a server with Plesk 10 and Plesk 11 templates for Debian 6.0 (and: Ubuntu 10.04, Redhat/CentOS 5 and 6, SuSE 11.4 and 12), if you create a container with Plesk 11 first, the problem with installing Plesk 10 occurs.

If the container with Plesk 10 is installed before installing Plesk 11 to any container, the problem does not occur.

The situation was corrected in the later Plesk versions as a result of the request TP #118401, but it remains the same for Plesk 11.0.x.


To fix the situation on the server, it is necessary to do the following:

  1. Stop all containers based on Debian 6.0 with Plesk 11 installed - those ones which use the currently fetched and extracted package;

    ~# for veid in $(\vzlist -ao veid,ostemplate | awk '/debian-6/{print$1}'); do p=$(grep psa-libxml-proxy /vz/private/$veid/templates/vzpackages); [ "$p" ] && echo $veid; done > affected_containers
    ~# while read veid; do vzctl stop $veid; done < affected_containers

    It is necessary to stop the container because the template area will be modified, and if this step is omitted, then there will most likely be a problem with online migration of such containers.

  2. Remove (move to another place) the directory /vz/template/debian/6.0/x86_64/psa-libxml-proxy_2.7.8-0.301910_amd64/ and the file /vz/template/debian/6.0/x86_64/pm/archives/psa-libxml-proxy_2.7.8-0.301910_amd64.vz.deb:

    ~# mv -a /vz/template/debian/6.0/x86_64/psa-libxml-proxy_2.7.8-0.301910_amd64 /vz/template/debian/6.0/x86_64/pm/archives/psa-libxml-proxy_2.7.8-0.301910_amd64.vz.deb /vz/tmp/
  3. Install the template pp10 to a container based on Debian 6.0, it should fetch and extract the proper package:

    ~# vzpkg install $CTID pp10
  4. Start containers that were stopped on the first step.

    ~# while read veid; do vzctl start $veid; done < affected_containers

Search Words

psa-libxml-proxy depends on plesk-core (>= 11.0.4)

a914db3fdc7a53ddcfd1b2db8f5a1b9c 56797cefb1efc9130f7c48a7d1db0f0c ac82ce33439a9c1feec4ff4f2f638899 caea8340e2d186a540518d08602aa065 5356b422f65bdad1c3e9edca5d74a1ae 2554725ed606193dd9bbce21365bed4e d02f9caf3e11b191a38179103495106f 2897d76d56d2010f4e3a28f864d69223 a26b38f94253cdfbf1028d72cf3a498b e8e50b42231236b82df27684e7ec0beb 0dd5b9380c7d4884d77587f3eb0fa8ef 614fd0b754f34d5efe9627f2057b8642

Email subscription for changes to this article
Save as PDF