Upgrading from PHP 5.1.6 -> 5.3 failing

[Swamper]

I tried upgrading via the control panel to 5.3 but it keeps failing. In case this matters, this is a test box that had 9.3 prior and I went straight to 10.1.1 without incident.

What do I need to do to get this to work? Thanks.

Execute command yum -y --enablerepo PSA_10_1_1-dist --enablerepo PSA_10_1_1-thirdparty --enablerepo SITEBUILDER_5_1_0-dist --enablerepo SITEBUILDER_5_1_0-thirdparty --enablerepo PPB_10_1_0-dist --enablerepo PPB_10_1_0-thirdparty install php53-ioncube-loader php53-sqlite2 psa-php53-configurator
Execute command yum -y --enablerepo PSA_10_1_1-dist --enablerepo PSA_10_1_1-thirdparty --enablerepo SITEBUILDER_5_1_0-dist --enablerepo SITEBUILDER_5_1_0-thirdparty --enablerepo PPB_10_1_0-dist --enablerepo PPB_10_1_0-thirdparty install php53-ioncube-loader php53-sqlite2 psa-php53-configurator
Loaded plugins: rhnplugin, security
Excluding Packages in global exclude list
Finished
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package php53-ioncube-loader.i386 0:3.3.20-11011816 set to be updated
--> Processing Dependency: php53 < 5.4.0 for package: php53-ioncube-loader
--> Processing Dependency: php53 >= 5.3.0 for package: php53-ioncube-loader
---> Package php53-sqlite2.i386 0:5.3.2-11011810 set to be updated
---> Package psa-php53-configurator.noarch 0:1.6.1-rhel5.build1010110118.12 set to be updated
--> Processing Dependency: php53-mysql for package: psa-php53-configurator
--> Processing Dependency: php53-imap for package: psa-php53-configurator
--> Processing Dependency: php53-cli for package: psa-php53-configurator
--> Processing Dependency: php53-pdo for package: psa-php53-configurator
--> Processing Dependency: php53-mbstring for package: psa-php53-configurator
--> Processing Dependency: php53-xml for package: psa-php53-configurator
--> Processing Dependency: php53-gd for package: psa-php53-configurator
--> Running transaction check
---> Package php53.i386 0:5.3.3-1.el5 set to be updated
--> Processing Dependency: php53-common = 5.3.3-1.el5 for package: php53
---> Package php53-cli.i386 0:5.3.3-1.el5 set to be updated
---> Package php53-gd.i386 0:5.3.3-1.el5 set to be updated
---> Package php53-imap.i386 0:5.3.3-1.el5 set to be updated
---> Package php53-mbstring.i386 0:5.3.3-1.el5 set to be updated
---> Package php53-mysql.i386 0:5.3.3-1.el5 set to be updated
---> Package php53-pdo.i386 0:5.3.3-1.el5 set to be updated
---> Package php53-xml.i386 0:5.3.3-1.el5 set to be updated
--> Running transaction check
---> Package php53-common.i386 0:5.3.3-1.el5 set to be updated
Loaded plugins: rhnplugin, security
Excluding Packages in global exclude list
Finished
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package php53-ioncube-loader.i386 0:3.3.20-11011816 set to be updated
--> Processing Dependency: php53 < 5.4.0 for package: php53-ioncube-loader
--> Processing Dependency: php53 >= 5.3.0 for package: php53-ioncube-loader
---> Package php53-sqlite2.i386 0:5.3.2-11011810 set to be updated
---> Package psa-php53-configurator.noarch 0:1.6.1-rhel5.build1010110118.12 set to be updated
--> Processing Dependency: php53-mysql for package: psa-php53-configurator
--> Processing Dependency: php53-imap for package: psa-php53-configurator
--> Processing Dependency: php53-cli for package: psa-php53-configurator
--> Processing Dependency: php53-pdo for package: psa-php53-configurator
--> Processing Dependency: php53-mbstring for package: psa-php53-configurator
--> Processing Dependency: php53-xml for package: psa-php53-configurator
--> Processing Dependency: php53-gd for package: psa-php53-configurator
--> Running transaction check
---> Package php53.i386 0:5.3.3-1.el5 set to be updated
--> Processing Dependency: php53-common = 5.3.3-1.el5 for package: php53
---> Package php53-cli.i386 0:5.3.3-1.el5 set to be updated
---> Package php53-gd.i386 0:5.3.3-1.el5 set to be updated
---> Package php53-imap.i386 0:5.3.3-1.el5 set to be updated
---> Package php53-mbstring.i386 0:5.3.3-1.el5 set to be updated
---> Package php53-mysql.i386 0:5.3.3-1.el5 set to be updated
---> Package php53-pdo.i386 0:5.3.3-1.el5 set to be updated
---> Package php53-xml.i386 0:5.3.3-1.el5 set to be updated
--> Running transaction check
---> Package php53-common.i386 0:5.3.3-1.el5 set to be updated
--> Processing Conflict: php53-common conflicts php-common
--> Finished Dependency Resolution
php53-common-5.3.3-1.el5.i386 from rhel-i386-server-5 has depsolving problems
--> php53-common conflicts with php-common
Error: php53-common conflicts with php-common
You could try using --skip-broken to work around the problem
You could try running: package-cleanup --problems
package-cleanup --dupes
rpm -Va --nofiles --nodigest
The program package-cleanup is found in the yum-utils package.
Execute command /usr/sbin/getenforce
--> Processing Conflict: php53-common conflicts php-common
--> Finished Dependency Resolution
php53-common-5.3.3-1.el5.i386 from rhel-i386-server-5 has depsolving problems
--> php53-common conflicts with php-common
Error: php53-common conflicts with php-common
You could try using --skip-broken to work around the problem
You could try running: package-cleanup --problems
package-cleanup --dupes
rpm -Va --nofiles --nodigest
The program package-cleanup is found in the yum-utils package.
Execute command /usr/sbin/getenforce
Disabled
Error: The Yum utility failed to install the required packages.
Attention! Your software might be inoperable.
Please, contact product technical support.


[root@ tmp]# rpm -qa | grep -i php
php-xml-5.1.6-23.el5
php-gd-5.1.6-23.el5
php-common-5.1.6-23.el5
php-imap-5.1.6-23.el5
php-mysql-5.1.6-23.el5
psa-php5-configurator-1.6.1-rhel5.build1010110131.16
php-cli-5.1.6-23.el5
php-mbstring-5.1.6-23.el5
php-5.1.6-23.el5
php-pdo-5.1.6-23.el5

 

[Swamper]

yum erase php php-common php-cli
(this removed PHP 5.1.6 and all dependencies (Plesk/etc.))

Ran autoconfigure from shell and selected PHP53 to be installed.

Seems to be running normally.

 

[ryan_turner]

I had the same problem. I don't know how to run plesk 10's auto configure script, so I didn't try your fix. Waiting on instruction... running RHEL 64 bit, Plesk 10.1.1 that's about 30 minutes old; just migrated all of my accounts and then ran into this issue after trying to switch to PHP 5.3 in the product installer. Now, plesk is broken. Great.

...
psa.module_vpn_objects OK
psa.module_watchdog_disk OK
psa.module_watchdog_disk_event OK
psa.module_watchdog_param OK
psa.module_watchdog_report OK
psa.module_watchdog_service OK
psa.module_watchdog_service_event OK
psa.module_watchdog_sys_stat OK
psa.password_secrets OK
psa.pd_users OK
psa.protected_dirs OK
psa.report OK
psa.report_auto OK
psa.report_section OK
psa.resp_attach OK
psa.resp_forward OK
psa.resp_freq OK
psa.secret_keys OK
psa.sessions OK
psa.siteapppackages_apscategories OK
psa.smb_apsBundleFilterItems OK
psa.smb_apsBundleFilters OK
psa.smb_apsCategories OK
psa.smb_apsContexts OK
psa.smb_apsImportedResources OK
psa.smb_apsImportedSettings OK
psa.smb_apsInstanceErrors OK
psa.smb_apsInstances OK
psa.smb_apsMetas OK
psa.smb_apsPackageUpdates OK
psa.smb_apsPackages OK
psa.smb_apsPackagesCategories OK
psa.smb_apsProvisionEnvironments OK
psa.smb_apsProvisions OK
psa.smb_apsResourceParameters OK
psa.smb_apsResources OK
psa.smb_apsSettings OK
psa.smb_componentUpdates OK
psa.smb_emailAliases OK
psa.smb_fileSharingUnlistedFiles OK
psa.smb_generalPermissions OK
psa.smb_locales OK
psa.smb_productUpgrades OK
psa.smb_roleGeneralPermissions OK
psa.smb_roleServicePermissions OK
psa.smb_roles OK
psa.smb_serviceEntryPoints OK
psa.smb_serviceInstances OK
psa.smb_servicePermissionAccounts OK
psa.smb_servicePermissions OK
psa.smb_serviceProviders OK
psa.smb_settings OK
psa.smb_userServicePermissions OK
psa.smb_users OK
psa.smtp_poplocks OK
psa.spamfilter OK
psa.spamfilter_preferences OK
psa.subdomains OK
psa.suspend_handler_history OK
psa.sys_users OK
psa.upgrade_history OK
psa.web_users OK
psa.webalizer_group_referrer OK
psa.webalizer_hidden_referrer OK

===> Upgrading database

Trying to start service mysqld... done
Trying to establish test connection... connected
done
Trying to find psa database... version is 010101
Version is OK, no need to create psa database.
Trying to backup MySQL database... done
MySQL databases are dumped to /var/lib/psa/dumps/mysql.preupgrade.10.10.1-10.10.1.20110320-020223.dump.gz
===> Cumulative database upgrade has been started
===> Upgrade completed.
Trying to set psa database version to 010101...
**** Product prep-install completed successfully.

Loaded plugins: rhnplugin, security
Setting up Install Process
Package mysql-5.0.77-4.el5_5.5.i386 already installed and latest version
Resolving Dependencies
--> Running transaction check
---> Package libmysqlclient15.x86_64 0:5.0.77-4.el5_5.4.10111810 set to be updated
---> Package mysql.x86_64 0:5.1.52-10121017 set to be updated
---> Package mysql-libs.x86_64 0:5.1.52-10121017 set to be updated
---> Package mysql-server.x86_64 0:5.1.52-10121017 set to be updated
---> Package php53-ioncube-loader.x86_64 0:3.3.20-11011816 set to be updated
--> Processing Dependency: php53 < 5.4.0 for package: php53-ioncube-loader
--> Processing Dependency: php53 >= 5.3.0 for package: php53-ioncube-loader
---> Package php53-sqlite2.x86_64 0:5.3.2-11011812 set to be updated
---> Package plesk-mysql.x86_64 0:5.1-10111810 set to be updated
---> Package psa-php53-configurator.noarch 0:1.6.1-rhel5.build1010110118.12 set to be updated
--> Processing Dependency: php53-pdo for package: psa-php53-configurator
--> Processing Dependency: php53-imap for package: psa-php53-configurator
--> Processing Dependency: php53-cli for package: psa-php53-configurator
--> Processing Dependency: php53-gd for package: psa-php53-configurator
--> Processing Dependency: php53-mbstring for package: psa-php53-configurator
--> Processing Dependency: php53-xml for package: psa-php53-configurator
--> Processing Dependency: php53-mysql for package: psa-php53-configurator
--> Running transaction check
---> Package php53.x86_64 0:5.3.3-1.el5_6.1 set to be updated
--> Processing Dependency: php53-common = 5.3.3-1.el5_6.1 for package: php53
---> Package php53-cli.x86_64 0:5.3.3-1.el5_6.1 set to be updated
---> Package php53-gd.x86_64 0:5.3.3-1.el5_6.1 set to be updated
---> Package php53-imap.x86_64 0:5.3.3-1.el5_6.1 set to be updated
---> Package php53-mbstring.x86_64 0:5.3.3-1.el5_6.1 set to be updated
---> Package php53-mysql.x86_64 0:5.3.3-1.el5_6.1 set to be updated
---> Package php53-pdo.x86_64 0:5.3.3-1.el5_6.1 set to be updated
---> Package php53-xml.x86_64 0:5.3.3-1.el5_6.1 set to be updated
--> Running transaction check
---> Package php53-common.x86_64 0:5.3.3-1.el5_6.1 set to be updated
--> Processing Conflict: php53-common conflicts php-common
--> Finished Dependency Resolution
php53-common-5.3.3-1.el5_6.1.x86_64 from rhel-x86_64-server-5 has depsolving problems
--> php53-common conflicts with php-common
Error: php53-common conflicts with php-common
You could try using --skip-broken to work around the problem
You could try running: package-cleanup --problems
package-cleanup --dupes
rpm -Va --nofiles --nodigest
The program package-cleanup is found in the yum-utils package.
Error: The Yum utility failed to install the required packages.
Attention! Your software might be inoperable.
Please, contact product technical support.

 

[MatthewTLS]

I had a similar issue with upgrading my PHP to 5.3. I had to manually remove the PHP packages:

php-pdo-5.2.10-1.el5.centos
php-ldap-5.2.10-1.el5.centos
php-gd-5.2.10-1.el5.centos
php-common-5.2.10-1.el5.centos
php-cli-5.2.10-1.el5.centos
php-imap-5.2.10-1.el5.centos
php-mysql-5.2.10-1.el5.centos
php-xml-5.2.10-1.el5.centos
php-5.2.10-1.el5.centos
php-mbstring-5.2.10-1.el5.centos

And install the "php53" packages:

php53-mysql-5.3.3-1.el5
php53-gd-5.3.3-1.el5
php53-common-5.3.3-1.el5
php53-pdo-5.3.3-1.el5
php53-xml-5.3.3-1.el5
php53-imap-5.3.3-1.el5
php53-5.3.3-1.el5

The problem is, Plesk simply queries the RPM database for the package "php". RedHat is now packaging PHP 5.3 as "php53", not just "php". So, to make Plesk play happy with PHP 5.3, I had to create a blank RPM and install it:

php-5.3.3-1

I hope this helps!

 

[nalawong]

Hi Matthew,

I've been trying this out for the past 1-2 weeks!
May I know how do you create a blank RPM?

 

[MatthewTLS]

You will want to create your RPM using an under-privileged account (i.e. not root).

First, as root:

yum install rpm-build

Then as your under-privileged account:

mkdir -p ~/rpm/{BUILD,RPMS,SOURCES,SPECS,SRPMS,tmp}

Then create a ~/.rpmmacros file and include the following information:

%packager Your Name
%_topdir /home/YOUR_HOME_DIR/rpm
%_tmppath /home/YOUR_HOME_DIR/rpm/tmp

Then create tarball and put a README file in it:

cd ~/rpm/SOURCES
echo "To make Plesk 10 happy" > README-phpstub

# tar the pkg.
tar -czvf phpstub-5.3.3.tar.gz README-phpstub

Now create the php.spec file

cd ~/rpm/SPECS

touch php.spec

Put the following text in your php.spec file:

Summary: php53-5.3.3-1.el5 stub
Name: php
Version: 5.3.3
Release: 1
Source0: phpstub-5.3.3.tar.gz
License: GPL
Group: Development/Languages
BuildArch: noarch
BuildRoot: %{_tmppath}/%{name}-buildroot
Requires: php53
%description
PHP is an HTML-embedded scripting language. PHP attempts to make it
easy for developers to write dynamically generated webpages. PHP also
offers built-in database integration for several commercial and
non-commercial database management systems, so writing a
database-enabled webpage with PHP is fairly simple. The most common
use of PHP coding is probably as a replacement for CGI scripts.
%prep
%setup -q -c
%files
%doc README-phpstub

Then build the RPM:

rpmbuild -ba php.spec

Then, as root:

rpm -Uvh /home/YOUR_HOME_DIR/rpm/RPMS/noarch/php-5.3.3-1.noarch.rpm

Stop and Restart Plesk:

service psa stopall
service psa start

Login to your admin panel and click on Settings then Server Components. You should see next to php the version number: 5.3.3-1

Cheers,

Matthew

 

[nalawong]

Hi Matthew,

thanks! I'll try this out!

 

[MatthewTLS]

Also, make sure when you remove your php packages prior to installing php53 packages you use the --nodeps option. For example:

rpm -e --nodeps php php-common php-mysql

This will prevent RPM from complaining about dependencies.

Cheers!

 

[nalawong]

Hi Matthew,

would you be able to give an example in command line, how to you remove this?

php-pdo-5.2.10-1.el5.centos
is it?

yum remove php-pdo-5.2.10-1.el5.centos --nodeps

 

[MatthewTLS]

rpm -e --nodeps php-pdo

 

[nalawong]

It worked! I didn't create a blank RPM.
After removing the the previous php, i typed,

yum install php53*

Thank you so much!

 

[nalawong]

Hello Matthew,

Nevertheless, I've followed your instructions.
Created my RPM using an under-privileged account.

I'm having this prompt on my plesk 10.1 panel.

Error: New files of configuration for Apache web server were not built due to errors in configuration templates. The detailed error message was e-mailed to you, so please check the e-mail, fix the errors, and click here to retry generating configuration.

Would you have any idea why?

 

[nalawong]

Now I've got a new error,
after creating a new domain name, I'm prompted,

Error: No secure shell available

 

[MatthewTLS]

Hmm ... honestly, I'm not sure about either issue. I can only think that it would report "No secure shell available" if you removed the SSHTerm package. It could be related to your previous post:

It worked! I didn't create a blank RPM.
After removing the the previous php, i typed,

yum install php53*

I never recommend installing packages by using and asterisk ... funny things can happen. I always explicitly state what packages I want yum or rpm to install for me.

As for Plesk giving you the error:

Error: New files of configuration for Apache web server were not built due to errors in configuration templates. The detailed error message was e-mailed to you, so please check the e-mail, fix the errors, and click here to retry generating configuration.

It could be because you installed the blank PHP package. Did something stop working even though you reported that everything was working after installing php53 via yum?

 

[nalawong]

Sigh... I reported too early. Guess I've got to re-try everything again. this time without the asterisk.
Thanks for replying!

 

[nalawong]

Hello!

Parallels have helped me solve the issue.
below is the their reply.

Issue caused because psa got corrupted, so we repaired the psa.
I repaired the psa by following command.
"/usr/local/psa/bootstrapper/pp10.10.1-bootstrapper/bootstrapper.sh repair".

 

[atomicturtle]

For future reference, you can install PHP 5.2 or 5.3 from here:

http://www.atomicorp.com/wiki/index.php/PHP

the 5.3.6 packages just went into the -testing repo a few days ago.

 

[jiphex]

My only problem with your Atomic RPMs is that I believe the PHP 5.3 ones necessitate an update to MySQL 5.1, which is a step that a lot of our customers are wary of due to the 5.0->5.1 shift requiring a change in the data file format.

The same thing happened when the 5.2 RPMs first hit the Atomic repo which also required this update. I believe this was fixed though?

On a server currently with the Atomic PHP 5.2 (and mysql-server-5.0.77-4.el5_5.3) - trying to run "yum update php" (which takes us to 5.3) shows the conflicts at http://pastie.org/1767961

 

[SilasO]

Am getting "Missing Dependency: php-common = 5.2.17-1.el5.art is needed by package ..." for most packages
Any suggestion?
Thanks in advance...

 

[SilasO]

Solved!.....