1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice

Installing on Redhat 3 ES (Update4 ??) fails

Discussion in 'Plesk for Linux - 8.x and Older' started by tobtob, Feb 8, 2005.

  1. tobtob

    tobtob Guest

    0
     
    I just loaded a new server up with Redhat 3 ES . I installed all the updates via the up2date facility. When I attempt to load Plesk 7.5.2 it fails with an error about having the wrong level of PHP. It wants me to load up php-4.3.2-14.ent the current version is php-4.3.2-19 .
    I looked around some forums and it seems like I should have loaded the oldest version of redhat 3 es , then loaded plesk .
    I guess my question is ..........................

    What is the best way to proceed at this point ? Should I start over again by reloading redhat ? If i do, should I then install plesk then the updates to get it up to "update 4" ? Will future plesk update work if I do that ?

    Hopefully someone has been throught this and can help. Thanks in advance,
    --
    Tom OBrien
     
  2. EvilSlayer

    EvilSlayer Guest

    0
     
    Possible Solution

    Hi there

    I had a similiar problem when upgrading from 7.1.4 to 7.1.6. What worked for me was to first manually uninstall php's rpm's and then continue with the update.

    to unistall try:
    # rpm -e --nodeps --repackage php-4.3.2-19.ent php-mysql-4.3.2-19.ent php-imap-4.3.2-19.ent php-ldap-4.3.2-19.ent

    (hope i typed that correctly) and then continue with the update.

    When I upgraded from 7.1.6 to 7.5.2 I had another problem with auto install of the migration manager, but doing a forced install of it's rpm manually overcame that problem and the autoupdate then . So you may also be able to do something similiar here.

    I am also new to plesk / linux, so my knowledge is not brilliant - but it may also be an idea to do the update via the plesk console, instead of via up2date?

    hope this help.
     
Loading...