Search for:

Available article translations:

How to update PHP 5.x EZ template on a Container to version 5.3

Article ID: 113432, created on Mar 7, 2012, last review on Aug 12, 2014

  • Plesk 11.x for Linux
  • Plesk 10.x for Linux
  • Plesk 9.5 for Linux/Unix
  • Virtuozzo containers for Linux 4.6
  • Virtuozzo containers for Linux 4.0


I have a Container with the "php5" EZ template on it. When I try to install the "pp10-php53" EZ template to that Container, the installation fails with the following error:

--> Processing Conflict: php53-common conflicts php-common
--> Finished Dependency Resolution
php53-common-5.3.3-1.el5_6.1.i386 from base5 has depsolving problems
  --> php53-common conflicts with php-common
Error: php53-common conflicts with php-common

The article applies to Parallels Virtuozzo Containers versions based on CentOS 5.x and Parallels Plesk Panel version 9.5.4 and later versions.


1. Download the template below which corresponds to your Container's architecture:

MD5 SUM: 1fb73386281d1429458a70a3ae5d860b

MD5 SUM: bfeec658e6360f5636351319478ceaa6

2. Install it to the Hardware Node.

3. Update PHP on the Container by installing the above template to it:

# vzpkg install CTID pp-php53-update

Additional information

- The template is not for standalone installation to a Container and must be installed either on a Container with Parallels Plesk Panel, or in the same transaction with other Parallels Plesk Panel templates.

- The template cannot be installed to Containers where the php53 template is already present; if attempted, the installation will fail.

- The template must not be installed in the same transaction with the pp{*}-php53 template; if attempted, the template will be installed, but the transaction will be marked as "failed," and the installed templates will not be registered on the Container.

- PHP 5.3 installation is performed by means of the autoinstaller utility, using this command:

# /usr/local/psa/admin/sbin/autoinstaller --select-release-current --install-component php53

As the packages are installed inside the Container, an insignificant increase of disk space usage will occur.
The autoinstaller utility also needs virtual memory in amounts of up to 200 MB on some operating systems. If the template installation fails due to lack of memory (failcnt value will increase in /proc/user_beancounters), increase the amount of memory available to the Container and retry the procedure.


60d3e722783ac7177a2b4b4c13af4062 a914db3fdc7a53ddcfd1b2db8f5a1b9c 29d1e90fd304f01e6420fbe60f66f838 6ef0db7f1685482449634a455d77d3f4 dd0611b6086474193d9bf78e2b293040 d02f9caf3e11b191a38179103495106f e8e50b42231236b82df27684e7ec0beb 36627b12981f68a16405a79233409a5e 35c16f1fded8e42577cb3df16429c57a 0a53c5a9ca65a74d37ef5c5eaeb55d7f 2897d76d56d2010f4e3a28f864d69223 56797cefb1efc9130f7c48a7d1db0f0c

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