Plesk 9.2.3 won't install in OpenVZ 32-bit container

[Chris Magnuson]

This is:

# uname -a
Linux blade7.peakpeak.com 2.6.18-164.2.1.el5.028stab066.7 #1 SMP Thu Nov 26 12:54:50 MSK 2009 x86_64 x86_64 x86_64 GNU/Linux

Then in the container:
# uname -a
Linux teton1.peakpeak.com 2.6.18-164.2.1.el5.028stab066.7 #1 SMP Thu Nov 26 12:54:50 MSK 2009 i686 i686 i386 GNU/Linux

# cd /usr/src/plesk/

# ls -l
total 4944
-rwxr-xr-x 1 root root 5049564 Dec 9 01:32 parallels_installer_v3.5.0_build090817.16_os_CentOS_5_i386

So I run the installer with 9.2.3 plesk as the only thing chosen and get:


Select the installation type for Parallels Plesk Panel
===============================================================================

Installation types for the product:

1. (*) Typical
Install typically used components. Recommended for general use.

2. ( ) Full
Install all components.

3. ( ) Custom
Custom components selection. Recommended only for experienced users.


N) Continue installation with selected type; P) Go the previous page; Q) Cancel installing;
L) Overview or change components marked for the installation
To select an installation type or switch product, type the respective number;
Select action [N]:
Retrieving information about the installed packages...
Downloading the file PSA_9.2.3/dist-rpm-CentOS-5-i386/build-9.2.3-cos5-i386.hdr.gz: 10%..20%..30%..40%..50%..60%..70%..80%..90%..100% done.
Downloading the file PSA_9.2.3/update-rpm-CentOS-5-i386/update-9.2.3-cos5-i386.hdr.gz: 10%..20%..30%..40%..50%..60%..70%..80%..90%..100% done.
Downloading the file PSA_9.2.3/thirdparty-rpm-CentOS-5-i386/thirdparty-9.2.3-cos5-i386.hdr.gz: 17%..20%..32%..40%..52%..64%..82%..91%..100% done.
Determining the packages that need to be installed.
ERROR: Unable to install the "psa-9.2.3-cos5.build92091016.19.i586" package.
Not all packages were installed.
Please, contact product technical support.

 

[IgorG]

Look at this workaround. Maybe it will help. Please update thread with results.

 

[Chris Magnuson]

No, that doesn't help. The bind-utils is not installed already, and running these commands prior to running the Plesk installer didn't help the plesk install to succeed:

yum erase bind-libs.i386
yum install db4-utils.i386
yum install gcc-java.i386


I still get:

Determining the packages that need to be installed.
ERROR: Unable to install the "psa-9.2.3-cos5.build92091016.19.i586" package.
Not all packages were installed.
Please, contact product technical support.

 

[Chris Magnuson]

Not even the Typical install will succeed:

Select the installation type for Parallels Plesk Panel
===============================================================================

Installation types for the product:

1. (*) Typical
Install typically used components. Recommended for general use.

2. ( ) Full
Install all components.

3. ( ) Custom
Custom components selection. Recommended only for experienced users.


N) Continue installation with selected type; P) Go the previous page; Q) Cancel installing;
L) Overview or change components marked for the installation
To select an installation type or switch product, type the respective number;
Select action [N]:
Retrieving information about the installed packages...
Downloading the file PSA_9.2.3/dist-rpm-CentOS-5-i386/build-9.2.3-cos5-i386.hdr.gz: 10%..20%..30%..40%..50%..60%..70%..80%..90%..100% done.
Downloading the file PSA_9.2.3/update-rpm-CentOS-5-i386/update-9.2.3-cos5-i386.hdr.gz: 10%..20%..30%..40%..50%..60%..70%..80%..90%..100% done.
Downloading the file PSA_9.2.3/thirdparty-rpm-CentOS-5-i386/thirdparty-9.2.3-cos5-i386.hdr.gz: 17%..20%..40%..58%..88%..91%..100% done.
Determining the packages that need to be installed.
ERROR: Unable to install the "psa-9.2.3-cos5.build92091016.19.i586" package.
Not all packages were installed.
Please, contact product technical support.

 

[IgorG]

Do you have any useful in installation log in /tmp?

 

[Chris Magnuson]

No, the /tmp is completely empty.

 

[IgorG]

Very strange. During autoinstaller operation installation log should be placed to /tmp directory. Try to run autoinstaller again and check /tmp. Log should be there.