• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

ERROR: Unable to install....

B

ByteBistro

Guest
I'm trying to install Plesk on a fresh install of CentOS )64 bit). I have made a directory in /root/plesk where the autoinstaller resides and have set permissions (chmod +x parallels_installer_v3.5.0_build090817.16_os_CentOS_5_x86_64). I run the installer, and get up to this point:

Retrieving information about the installed packages...
Downloading the file PSA_9.2.3/update-rpm-CentOS-5-x86_64/update-9.2.3-cos5-x86_64.hdr.gz: 10%..20%..30%..40%..50%..60%..70%..80%..90%..100% done.
Downloading the file PSA_9.2.3/dist-rpm-CentOS-5-x86_64/build-9.2.3-cos5-x86_64.hdr.gz: 10%..20%..30%..40%..50%..60%..70%..80%..90%..100% done.
Downloading the file PSA_9.2.3/thirdparty-rpm-CentOS-5-x86_64/thirdparty-9.2.3-cos5-x86_64.hdr.gz: 11%..22%..31%..40%..52%..60%..72%..81%..90%..100% done.
Determining the packages that need to be installed.
ERROR: Unable to install the "psa-9.2.3-cos5.build92091016.19.x86_64" package.
Not all packages were installed.
Please, contact product technical support.

I have no clue what is going on and need to get this server up as soon as possible. Any help would be much appreciated. Thanks!
 
Hello
Make sure there is enough disk space on the server.
If yes - the given info is not enough, if it's possible attach log file: /tmp/autoinstaller3.log
 
Back
Top