1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice

Upgrading tot 7.5.1 safe?

Discussion in 'Plesk for Linux - 8.x and Older' started by Triloxigen, Dec 16, 2004.

  1. Triloxigen

    Triloxigen Guest

    0
     
    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?
     
  2. ZopfWare

    ZopfWare Regular Pleskian

    25
    57%
    Joined:
    May 30, 2004
    Messages:
    215
    Likes Received:
    0
    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!
     
  3. Triloxigen

    Triloxigen Guest

    0
     
    7.5.0 is needed?
    So... you have to manuallu upgrade to 7.5.0 and then upgrade to 7.5.1??

    That would **** :|
     
  4. Cranky

    Cranky Guest

    0
     
    You should install base directory first, then the opt directory.
     
  5. ZopfWare

    ZopfWare Regular Pleskian

    25
    57%
    Joined:
    May 30, 2004
    Messages:
    215
    Likes Received:
    0
    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.
     
  6. albertomesa

    albertomesa Guest

    0
     
    I have the same error updating from 7.5.0 to 7.5.1


    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!
     
  7. Cranky

    Cranky Guest

    0
     
    Yes, that'll work fine.
     
  8. pills

    pills Guest

    0
     
    perfect upgrade 7.5.0 to 7.5.1 on redhat 9 box.
    seems to be safe and stable now.
     
  9. Wythrol

    Wythrol Guest

    0
     
    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).
     
Loading...