• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Upgrading to PHP 5.2.17

PTS

New Pleskian
Hello all, I'm pretty comfortable with CLI but I want to make sure I'm taking the right steps when upgrading to PHP 5.2.17. I have a few websites that I can't afford to go down because of an upgrade failure.

I've got Plesk 10.1.1 running on CentOS 5 with the atomic repository already installed. To update to PHP 5.2.17, I am assuming the first step is as follows:

yum update php

If I proceed to install the two new packages and upgrade 18 existing packages, what are my next steps if any?

Does MySQL need to be updated? Right now I get the following error in phpMyAdmin: Your PHP MySQL library version 5.0.77 differs from your MySQL server version 5.1.52. This may cause unpredictable behavior.

Other than that error, everything runs well.

Thanks in advance.
 
Thanks Igor, I did see that page after posting this thread. That said, I do have a questions about Steps 3 and 4.

Step 3) Replace the PHP 4 php.ini with PHP 5.2.x's (if applicable):
mv /etc/php.ini.rpmnew /etc/php.ini

Step 4) Replace the php.conf with the PHP 5.2.x php.conf (if applicable):
mv /etc/httpd/conf.d/php.conf.rpmnew /etc/httpd/conf.d/php.conf


I'm upgrading from PHP 5.1.x so I assume Step 3 isn't applicable. What are you recommendations for Step 4? How do I know it it's applicable or not.

Thanks again.
 
I think it would be better contact atomicturtle user on this forum regarding their solution :)
 
Great question, the simple answer is if /etc/httpd/conf.d/php.conf.rpmnew exists then you probably need to do step 4.
 
Back
Top