• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • 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.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Upgrading tot 7.5.1 safe?

T

Triloxigen

Guest
I'm aware of the problems of PSA 7.5.0, but I saw today the 7.5.1 release.
Is it safe to upgrade from 7.1.6 to 7.5.1 without any problems?
 
I don't know I tried to update today and this is what I got:

Preparing for packages installation...
----- begin of output -----
Installing /PSA_7.5.1/rpm_FedoraCore_2/base/psa-pre-keyupdate-7.5.1-fc2.build75041216.15.i586.rpm
Installing /PSA_7.5.1/rpm_FedoraCore_2/base/libidn-0.4.2-fc2.build75041216.15.i586.rpm
Installing /PSA_7.5.1/rpm_FedoraCore_2/opt/bu/perl-IO-Ftp-0.05-fc2.build75041216.15.noarch.rpm
Installing /PSA_7.5.1/rpm_FedoraCore_2/opt/bu/perl-IO-Zlib-1.01-fc2.build75041216.15.noarch.rpm
Installing /PSA_7.5.1/rpm_FedoraCore_2/opt/bu/perl-MIME-Lite-2.117-fc2.build75041216.15.noarch.rpm
Installing /PSA_7.5.1/rpm_FedoraCore_2/base/psa-7.5.1-fc2.build75041216.15.i586.rpm
Installing /PSA_7.5.1/rpm_FedoraCore_2/base/psa-api-common-7.5.1-fc2.build75041216.15.i586.rpm
Installing /PSA_7.5.1/rpm_FedoraCore_2/base/psa-api-cli-7.5.1-fc2.build75041216.15.i586.rpm
Installing /PSA_7.5.1/rpm_FedoraCore_2/opt/api/psa-api-rpc-1.3.2-3.1.i586.rpm
Installing /PSA_7.5.1/rpm_FedoraCore_2/opt/api/psa-agent-1.3.2-3.1.i586.rpm
Installing /PSA_7.5.1/rpm_FedoraCore_2/base/psa-key-7.5-fc2.build75041216.15.noarch.rpm
Installing /PSA_7.5.1/rpm_FedoraCore_2/base/psa-locale-base-en-US-7.5.1-fc2.build75041216.15.noarch.rpm
Installing /PSA_7.5.1/rpm_FedoraCore_2/opt/bu/psa-bu-7.5.1-fc2.build75041216.15.i586.rpm
Installing /PSA_7.5.1/rpm_FedoraCore_2/opt/docs/psa-manual-custom-skin-guide-7.5.1-fc2.build75041216.15.i586.rpm
error: Failed dependencies:
psa-locale-base = 7.5.0 is needed by (installed) psa-pre-7.5.0-fc2.build75041125.15


----- end of output -----
===> Autoinstaller: stopped logging at Thu Dec 16 12:15:30 2004


***** end of log file *****


Would love to hear how I get around this one!
 
7.5.0 is needed?
So... you have to manuallu upgrade to 7.5.0 and then upgrade to 7.5.1??

That would **** :|
 
You should install base directory first, then the opt directory.
 
All advice well taken, however Plesk 7.5.0 (12/08) version is supposedly already installed.

As to cranky's suggestion... I have tried installing just the base and i get the same error.

Plesk (those people in Siberia :) ) are working on the problem as we speak.


Hopefully they will have an answer. If not I am still open to suggestions.
 
I have the same error updating from 7.5.0 to 7.5.1

error: Failed dependencies:
psa-locale-base = 7.5.0 is needed by (installed) psa-pre-7.5.0-fc2.build75041125.15


I just deleted the psa-pre-7.5.0 with: rpm -e psa-pre

Then the upgrade to 7.5.1 was successful.

Please confirm this with someone from Plesk!
 
perfect upgrade 7.5.0 to 7.5.1 on redhat 9 box.
seems to be safe and stable now.
 
Not to sure about stable yet. I'm still having issues with the automated domain backups [yeah I know, should be using psabackup, but hell this is easier and technically should work].

Backingup and storing locally seems ok, but backing up to an alternate FTP seems a little hit and miss. I have 10 domains on a daily backup; atleast 1 will fail, one night domain A will fail, next evening it will be domain E that fails. Cant figure it out.

The remote FTP is on the same domain range, and is only accessible from within the closed network (1&1 UK).
 
Back
Top