• 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 PHP 5.2 to 5.3.17 on debian 5

GregorioM

New Pleskian
Hello everybody,

I am a plesk newbie but I have long experience with webservers and php, I need an advice about the upgrade of Php on plesk 9.5.4: I have found some posts on the forum and some kb articles, but regarding other versions of plesk and centos, it seems like not about debian and Php 5.3.

On debian 5 I cannot find any package newer than 5.3.10, let's assume I am able to download the last tarball from php.net, then compile it and deploy properly for a server without plesk, my question is: once the new php is up and running, how I manage to set up things properly for plesk?

Thank you for any advice you may give to me...

Best to all!
 
Hi, GregorioM

Plesk requires an installed PHP package. Did you try to look in:
http://www.debian-ports.org/
http://www.dotdeb.org/

Perhaps also you can build PHP from Debian source package.

In a theory, if you can install binary package with PHP 5.3.10 and then compile and install 5.3.17 from PHP tarball.
This will work if you will use same paths for 5.3.17 as in the installed PHP package with 5.3.10.
 
Thank you Alexey for your answer.

As you suggested I installed binaries from dotdeb, php 5.3.10, forcing a bit on dependencies but after the installation all runs smooth, so I have checked all scripts against 5.3 as first thing.

I tried to build from 5.3.17 source a php.fcgi almost as configured in debian and to substitute to the binary php-cgi in /var/www/cgi-bin/cgi_wrapper/cgi_wrapper touching as minus as possible the configuration, and, setting in plesk that a domain uses fcgi, I have php 5.3.17 running on that domain wit fcgi.

Now I will try to build php again using the same path on package, as you suggest, and I will report about my progress.

I think I will start to use this congiguration on production site, switching to the new php domain by domain on the panel webpage, then I will use the 5.3.10 version only (?1) on horde; if/when all domains are ok, I will install the rebuilded php with the same path of the package.

I try to create as small problem as I can to users now, this way we will have a more secure server in short time, then we will hold on till next year when we will switch directly to new server with plesk 11.

Do you think this procedure will work?

Thank you!
 
Last edited:
Back
Top