Search for:

Available article translations:

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

  • Parallels Plesk Panel 11.x for Linux
  • Parallels Plesk Panel 10.x for Linux
  • Parallels Plesk Panel 9.5 for Linux/Unix
  • Parallels Virtuozzo Containers for Linux 4.6
  • Parallels 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.


7a5ab9f25384019cf8b9ba7051f8b781 49af2da0f2dd4c81e962790bbbd0c2b4 5d735c0e028ee5b991e4fb80d34fb87f 6eab23e8dac1eb5df9820a41f94cf4b4 0324051e74e0392d1551a3b559b09eaa 909d99074e442b52ce54cc7b31cf065d eb0ea3b827d18de2329b6477e24c1d59 219be54dff19e220f37105b0000118f4 9bccb04d0396d587d8123e5e12b4740e c7658ac2f68d6572a213687c1077afff 2897d76d56d2010f4e3a28f864d69223 56797cefb1efc9130f7c48a7d1db0f0c

Was this article helpful?
Tell us how we may improve it.
Yes No
Desktop Virtualization
- Parallels Desktop 8 for Mac
- Parallels Transporter
- Parallels Desktop Switch to Mac Edition
- Parallels Desktop for Mac Enterprise Edition
- Parallels Management-Mac for Microsoft SCCM
Server Virtualization
- Parallels Cloud Server
- Parallels Containers for Windows 6.0 Beta
- Parallels Virtuozzo Containers
- 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