upgrage from 4.1.2 to 4.3.3+?

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • LRW
    #1

    upgrage from 4.1.2 to 4.3.3+?

    We have a RedHat 7.3 server running PHP 4.1.2, and I really need to
    upgrade it to at least 4.3.3 to take advantage of some features.

    What's the easiest, least risky way to upgrade suffering no or nearly
    no server downtime?

    I looked at php.net for patches, but there's none that I found for
    4.1.2.
    I tried RedHat's "up2date" but in the list of available packages to
    download, PHP's not one of them.

    Any suggestions or pointers to any sites or docs would be greatly
    appreciated!
    Thanks
    Liam
    Tags: None
    • Reply Via Newsgroup
      #2
      Re: upgrage from 4.1.2 to 4.3.3+?

      LRW wrote:
      [color=blue]
      > We have a RedHat 7.3 server running PHP 4.1.2, and I really need to
      > upgrade it to at least 4.3.3 to take advantage of some features.
      >
      > What's the easiest, least risky way to upgrade suffering no or nearly
      > no server downtime?
      >
      > I looked at php.net for patches, but there's none that I found for
      > 4.1.2.
      > I tried RedHat's "up2date" but in the list of available packages to
      > download, PHP's not one of them.
      >
      > Any suggestions or pointers to any sites or docs would be greatly
      > appreciated!
      > Thanks
      > Liam[/color]

      I have always upgraded to every stable release of PHP pretty much as
      soon as it was released (as of PHP4) and all I ever did was recompile
      Apache + PHP - It took a couple of minutes on my 128mb 400mhz server and
      I have several modules compiled in (./configure' '--with-mysql'
      '--with-apache=/data/www/software/apache' '--with-mcrypt'
      '--with-jpeg-dir' '--enable-exif' '--with-zlib-dir' '--with-gd'
      '--with-ttf' '--enable-gd-native-ttf' '--with-freetype-dir'
      '--with-mime-magic' '--disable-session' '--disable-cgi')

      If you are unable to perform a compile, you can make another posted
      reply to this and I can give you my simple script that I've used for
      every version 4 'upgrade' that I've done (in a sense, it should be
      considered a re-install but it never gave me problems).

      Alternativly, if you really really want to use 'rpm' to handle it for
      you (and I suppose, why not) then isn't there something like rpm
      --upgrade [packagename] that you can use?

      randelld

        Comment

        • LRW
          #3
          Re: upgrage from 4.1.2 to 4.3.3+?

          Reply Via Newsgroup <reply-to-newsgroup@pleas e.com> wrote in message news:<xGz3c.116 26$Up2.8408@pd7 tw1no>...[color=blue]
          > LRW wrote:
          >[color=green]
          > > We have a RedHat 7.3 server running PHP 4.1.2, and I really need to
          > > upgrade it to at least 4.3.3 to take advantage of some features.
          > >
          > > What's the easiest, least risky way to upgrade suffering no or nearly
          > > no server downtime?
          > >[/color][/color]
          --SNIP--[color=blue]
          >
          > I have always upgraded to every stable release of PHP pretty much as
          > soon as it was released (as of PHP4) and all I ever did was recompile
          > Apache + PHP - It took a couple of minutes on my 128mb 400mhz server and
          > I have several modules compiled in (./configure' '--with-mysql'
          > '--with-apache=/data/www/software/apache' '--with-mcrypt'
          > '--with-jpeg-dir' '--enable-exif' '--with-zlib-dir' '--with-gd'
          > '--with-ttf' '--enable-gd-native-ttf' '--with-freetype-dir'
          > '--with-mime-magic' '--disable-session' '--disable-cgi')
          >
          > If you are unable to perform a compile, you can make another posted
          > reply to this and I can give you my simple script that I've used for
          > every version 4 'upgrade' that I've done (in a sense, it should be
          > considered a re-install but it never gave me problems).
          >
          > Alternativly, if you really really want to use 'rpm' to handle it for
          > you (and I suppose, why not) then isn't there something like rpm
          > --upgrade [packagename] that you can use?
          >[/color]

          Thanks for the advice!
          As for RPM's, well, I did a RedHat up2date which is supposed to locate
          every available RPM for the distro...and there isn't one for PHP.
          And even if there was, I'm not sure I'd trust it not to mess something
          up.
          See, my experience with installing PHP has only been on clean setups.
          Where I'm working now, they installed mods for turning things into
          PDFs and incorporating Ghostscript into image making through the Web
          and other things, and I REALLY am reticent to use any automated
          process that I can't see exactly what it's going to do before it does
          it. Know what I mean?

          And also, I uh, don't believe I've ever recompiled Apache or PHP.
          Sounds rather risky. Or is it? I was so hoping it'd be something as
          easy as putting the new PHP in a folder and changing the httpd.conf to
          use the new version LOL. Hey, I'm the guy who in the 80's was sure
          there was some secret device that could convert Apple programs into
          Commodore. =)
          I less "httpd.conf | grep php" and I see no paths, so, obviously a
          recompile of Apache will be needed.
          Well, if you have any more suggestions for an annoying newbie who
          doesn't want to lose his job for corrupting the Web server, I'm all
          ears! =)

          Thanks!
          Liam

            Comment

            • Reply Via Newsgroup
              #4
              Re: upgrage from 4.1.2 to 4.3.3+?

              LRW wrote:[color=blue]
              > Reply Via Newsgroup <reply-to-newsgroup@pleas e.com> wrote in message news:<xGz3c.116 26$Up2.8408@pd7 tw1no>...
              >[color=green]
              >>LRW wrote:
              >>
              >>[color=darkred]
              >>>We have a RedHat 7.3 server running PHP 4.1.2, and I really need to
              >>>upgrade it to at least 4.3.3 to take advantage of some features.
              >>>
              >>>What's the easiest, least risky way to upgrade suffering no or nearly
              >>>no server downtime?
              >>>[/color][/color]
              >
              > --SNIP--
              >[color=green]
              >>I have always upgraded to every stable release of PHP pretty much as
              >>soon as it was released (as of PHP4) and all I ever did was recompile
              >>Apache + PHP - It took a couple of minutes on my 128mb 400mhz server and
              >>I have several modules compiled in (./configure' '--with-mysql'
              >>'--with-apache=/data/www/software/apache' '--with-mcrypt'
              >>'--with-jpeg-dir' '--enable-exif' '--with-zlib-dir' '--with-gd'
              >>'--with-ttf' '--enable-gd-native-ttf' '--with-freetype-dir'
              >>'--with-mime-magic' '--disable-session' '--disable-cgi')
              >>
              >>If you are unable to perform a compile, you can make another posted
              >>reply to this and I can give you my simple script that I've used for
              >>every version 4 'upgrade' that I've done (in a sense, it should be
              >>considered a re-install but it never gave me problems).
              >>
              >>Alternativl y, if you really really want to use 'rpm' to handle it for
              >>you (and I suppose, why not) then isn't there something like rpm
              >>--upgrade [packagename] that you can use?
              >>[/color]
              >
              >
              > Thanks for the advice!
              > As for RPM's, well, I did a RedHat up2date which is supposed to locate
              > every available RPM for the distro...and there isn't one for PHP.
              > And even if there was, I'm not sure I'd trust it not to mess something
              > up.
              > See, my experience with installing PHP has only been on clean setups.
              > Where I'm working now, they installed mods for turning things into
              > PDFs and incorporating Ghostscript into image making through the Web
              > and other things, and I REALLY am reticent to use any automated
              > process that I can't see exactly what it's going to do before it does
              > it. Know what I mean?
              >
              > And also, I uh, don't believe I've ever recompiled Apache or PHP.
              > Sounds rather risky. Or is it? I was so hoping it'd be something as
              > easy as putting the new PHP in a folder and changing the httpd.conf to
              > use the new version LOL. Hey, I'm the guy who in the 80's was sure
              > there was some secret device that could convert Apple programs into
              > Commodore. =)
              > I less "httpd.conf | grep php" and I see no paths, so, obviously a
              > recompile of Apache will be needed.
              > Well, if you have any more suggestions for an annoying newbie who
              > doesn't want to lose his job for corrupting the Web server, I'm all
              > ears! =)
              >
              > Thanks!
              > Liam[/color]

              Sorry for the delay in replying to your post...

              By the by - with a name like Liam, are you Irish? (I am)

              I don't think you've thought your problem through - its not as difficult
              as you think... and - you can reduce your risk to almost zero - How/Why?

              Well - You could compile your own version of Apache and PHP and place it
              under a location that is seperate than your existing version - I have
              mine installed under /opt/apache - I would gather yours sites under
              /usr/local/bin/apache or something, true?

              Then - once you've compiled it, you could test it out using a different
              port number - By this I mean, whenever you visit a website, it defaults
              to visiting port 80 - If you search for '80' in your httpd.conf file,
              you'll find something like "Port 80" - Thus, what you could do is after
              the compile, is edit your new installations httpd.conf file and change
              the default 80 to something like 8080 or 1234 or whatever you like (just
              make sure you choose a port that is not already in use).

              Then you can test to your hearts content - If your servers IP address
              was 12.34.56.78, and you set the port number to 8080 (which is a popular
              alternative port number to try) then you would access it via a client
              web browser with http://12.34.56.78:8080

              You could do this all the while having your existing (older version) of
              Apache running uninterrupted. You could even go so far as to set your
              newer version to have the same DOCUMENT_ROOT as the old version
              therefore permitting a full test under the new environment without
              changing the old environment.

              Once you've tested everything, all you'd have to do is change the port
              number in your new version to port 80 - Then stop your old version and
              new version - Then start the new version and hey presto! new version is
              working fine and dandy... I would suggest eventually changing startup
              procedures (if you don't, a system reboot would start your old version).

              Eventually, you might/should remove the old version once you are happy
              with the new version.

              Does this help you any? I can help you with the compile if you like
              though you'd better off emailing me in part because I'd need a copy of
              your existing phpinfo(); output - This would tell me what your existing
              (older Apache version) has compiled/included.

              I won't publicise my email address just yet - just let me know if you
              think you need the help and I can let you know how best to contact me.

              laters
              randell d.

                Comment

                • LRW
                  #5
                  Re: upgrage from 4.1.2 to 4.3.3+?

                  Reply Via Newsgroup <reply-to-newsgroup@pleas e.com> wrote in message news:<5Sw4c.397 25$Up2.38896@pd 7tw1no>...
                  --SNIP--[color=blue]
                  > Sorry for the delay in replying to your post...
                  >
                  > By the by - with a name like Liam, are you Irish? (I am)
                  >
                  > I don't think you've thought your problem through - its not as difficult
                  > as you think... and - you can reduce your risk to almost zero - How/Why?
                  >[/color]
                  --SNIP--[color=blue]
                  > Does this help you any? I can help you with the compile if you like
                  > though you'd better off emailing me in part because I'd need a copy of
                  > your existing phpinfo(); output - This would tell me what your existing
                  > (older Apache version) has compiled/included.
                  >
                  > I won't publicise my email address just yet - just let me know if you
                  > think you need the help and I can let you know how best to contact me.
                  >[/color]
                  Randell, thanks for your help!
                  And my father's family is all Irish. =)

                  Great advice about how to install a new PHP version w/o affecting the
                  old! Hadn't thought about that.

                  I had actually successfully installed the latest PHP using static
                  "quick" install instructions:
                  ../configure --with-mysql --with-apxs
                  make
                  make install
                  apachetl restart

                  However, phpinfo then, of course, only shows the mysql and aspx mods.
                  When compared to the old PHP, that's worrisome:

                  Old PHP 4.1.2:
                  './configure' 'i386-redhat-linux' '--prefix=/usr' '--exec-prefix=/usr'
                  '--bindir=/usr/bin' '--sbindir=/usr/sbin' '--sysconfdir=/etc'
                  '--datadir=/usr/share' '--includedir=/usr/include' '--libdir=/usr/lib'
                  '--libexecdir=/usr/libexec' '--localstatedir=/var'
                  '--sharedstatedir=/usr/com' '--mandir=/usr/share/man'
                  '--infodir=/usr/share/info' '--prefix=/usr'
                  '--with-config-file-path=/etc' '--enable-force-cgi-redirect'
                  '--disable-debug' '--enable-pic' '--disable-rpath'
                  '--enable-inline-optimization' '--with-bz2' '--with-db3' '--with-curl'
                  '--with-dom=/usr' '--with-exec-dir=/usr/bin'
                  '--with-freetype-dir=/usr' '--with-png-dir=/usr' '--with-gd'
                  '--enable-gd-native-ttf' '--with-ttf' '--with-gdbm' '--with-gettext'
                  '--with-ncurses' '--with-gmp' '--with-iconv' '--with-jpeg-dir=/usr'
                  '--with-mm' '--with-openssl' '--with-png' '--with-pspell'
                  '--with-regex=system' '--with-xml' '--with-expat-dir=/usr'
                  '--with-zlib' '--with-layout=GNU' '--enable-bcmath'
                  '--enable-debugger' '--enable-exif' '--enable-ftp'
                  '--enable-magic-quotes' '--enable-safe-mode' '--enable-sockets'
                  '--enable-sysvsem' '--enable-sysvshm' '--enable-discard-path'
                  '--enable-track-vars' '--enable-trans-sid' '--enable-yp'
                  '--enable-wddx' '--without-oci8' '--with-imap=shared'
                  '--with-imap-ssl' '--with-kerberos=/usr/kerberos' '--with-ldap=shared'
                  '--with-mysql=shared,/usr' '--with-pgsql=shared'
                  '--with-snmp=shared,/usr' '--with-snmp=shared'
                  '--enable-ucd-snmp-hack' '--with-unixODBC=shared '
                  '--enable-memory-limit' '--enable-bcmath' '--enable-shmop'
                  '--enable-versioning' '--enable-calendar' '--enable-dbx'
                  '--enable-dio' '--enable-mbstring' '--enable-mbstr-enc-trans'
                  '--with-apxs=/usr/sbin/apxs'

                  New PHP 4.3.4:
                  './configure' '--with-mysql' '--with-apxs'

                  I tried running the configure line from the old PHP (deleting
                  config.cache first), and after every attempt an error comes up: first
                  a problem with db4, then with libxml, then something else, each time I
                  remove the offenting line from the configure, or install a newer
                  version of something if it asked for it (like libxml) but after each
                  change, it just finds something new to have a problem with.

                  *sigh*

                  What a mess.
                  I don't know if you could possibly have any suggestions for this...but
                  if you do, I'd be more than happy to hear. =)
                  Thanks for your time already!!
                  Liam
                  druid@NOSPAHMce lticbear.com
                  (remove the caps from the address to e-mail)

                    Comment

                    Previous template Next
                    Working...