The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

PHP Upgrade?

Discussion in 'General Discussion' started by purplep, Mar 1, 2002.

  1. purplep

    purplep Well-Known Member

    Joined:
    Feb 6, 2002
    Messages:
    59
    Likes Received:
    0
    Trophy Points:
    6
    Hi,

    What are the steps to upgrading PHP?

    Are there any guides or manuals?

    I havent done this before and would really like to try instead of paying pwebtech to do it for us.

    Cheers.
     
  2. carperman

    carperman Well-Known Member

    Joined:
    Feb 7, 2002
    Messages:
    150
    Likes Received:
    0
    Trophy Points:
    16
    yep i would like to know this especially with current security issues: http://security.e-matters.de/advisories/012002.html
     
  3. Daniel

    Daniel Well-Known Member

    Joined:
    Aug 13, 2001
    Messages:
    165
    Likes Received:
    0
    Trophy Points:
    16
    See: http://support.cpanel.net/obb/read.php?TID=1816
     
  4. feanor

    feanor Well-Known Member

    Joined:
    Aug 13, 2001
    Messages:
    836
    Likes Received:
    0
    Trophy Points:
    16
    We need a better upgrade for these cpanel machines that pre-date Redhat 7.1 .....

    For 6.2 machines, the library incompatibilities that you run into on *most* of the boxes result in huge ongoing battles with getting php to compile with all of the modules that cpanel requires.

    For instance, the most frequent errors on the 6.2 boxes dovetail with this issue...

    http://www.phpbuilder.com/mail/php-developer-list/2001112/1007.php

    Usually, you can win the day if you spend a few hours on getting things in place so the compile works. But none of these older boxes are the same. Is there a more comprehensive catch-all type upgrade to apache 1.3.23 and php 4.1.2 that can catch all of these issues that come up- including the one mentioned above, including any curl incompatibilities, etc.........

    Because it is a nightmare when you have a sizable amount of machines that still sit at RH 6.2 ......... everything is slightly different and it appears the latest buildapache & fp_upgrade are tailored for RH 7.1 and above.

    Even just a list of all things to get in sync by hand for us administrators on these older boxes would be very helpful. Like &before you run this upgrade on RH 6.2, make sure you have these rpms or sources installed&.....

    Thanks for any guidance anyone might have.
     
  5. carperman

    carperman Well-Known Member

    Joined:
    Feb 7, 2002
    Messages:
    150
    Likes Received:
    0
    Trophy Points:
    16
    how easy would it be to upgrade a 6.2 machine to 7.2?

    would it be worth it?
     
  6. feanor

    feanor Well-Known Member

    Joined:
    Aug 13, 2001
    Messages:
    836
    Likes Received:
    0
    Trophy Points:
    16
    stick RH 7.2 CD in and upgrade it.
    Rate of disaster = 40%

    I'd appreciate to hear some feedback first from the cpanel developing super stallion team about the best course of action for RH 6.2 boxes............

    Otherwise it is supreme risk, anything you try on that particular version of the OS
     
  7. moronhead

    moronhead Well-Known Member

    Joined:
    Aug 12, 2001
    Messages:
    706
    Likes Received:
    0
    Trophy Points:
    16
    I felt the same pain when I first upgraded from 4.0.6. to 4.1.0. ;)! Jumping to 4.1.2 from 4.1.0 was easy.

    Once you've wget the php tar from www.php.net and untarred it, try running ./buildconf in the root directory of the tarred file. That should give you a good indication on missing or outdated libraries.

    You can then try www.rpmfind.net to see if you can find the rpms for those libraries relevant to your servers' OS and the OS version.

    PHP4.1.x needs gd-1.8.4 and ming-0.2a at the minimum for starters (if you intend to compile it with those options).

    Once you've got ./buildconf sorted (no further warnings) just do:

    ./configure
    ./make
    ./make install

    Here's the ./configure build I use:

    [quote:f89bacfdfb]
    ./configure --with-apxs=/usr/local/apache/bin/apxs --with-xml --enable-ftp --with-gd --with-zlib --with-jpeg-dir=/usr/local --with-png-dir=/usr --with-xpm-dir=/usr/X11R6 --with-swf=/usr/local/flash --enable-magic-quotes --with-mysql --enable-safe-mode --enable-track-vars --with-ttf --enable-versioning --with-mcrypt --enable-sockets --enable-calendar --with-ming --with-curl --with-mm
    [/quote:f89bacfdfb]

    If ./configure ends abruptly with a dire warning before it finishes its job you need to eliminate the cause first before you re-run it. Before you re-run it do a:

    rm ./config.cache

    This will erase the previous config file so it can be re-started with a clean sheet.

    Once you've got through the ./configure simply do a:

    ./make (pour yourself a large espresso at this stage and relax ;))

    If ./make ends abruptly, again, just apply the same strategy for ./configure; eliminating the cause for the warnings, if any. Before you re-run ./make do a:

    ./make clean

    This will erase the previous traces of ./make and force a fresh restart.

    If ./make goes to plan just do:

    ./make install

    to let PHP install the libphp4.so and mod_php4.c modules and new version files for you.

    Restart apache and ensure your web server is working after the restart. If it does, you're finally through. Make up a test.php file with a single line in it:

    &?php phpInfo(); ?&

    If this runs as it's meant to, you can start smiling.

    You may want to install the zend optimizer as a final push by running /scripts/installzendopt-php411.

    That's about it. I hope it helps.
     
Loading...

Share This Page