• 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.

[SOLVED] Latest php 5.3.26 yum update from art breaks apache

KirkM

Regular Pleskian
If you do a yum update for php and use the atomic repository, BE CAREFUL!

The latest version 5.3.26 from ART repository created a big problem with apache for me with my Plesk 11.0.9 / Centos 5.9 box.

After the update, Apache will fail to start with this error:

Code:
# service httpd restart
Stopping httpd:                                            [FAILED]
Starting httpd: Syntax error on line 31 of /etc/httpd/conf.d/php.conf:
Invalid command 'php_value', perhaps misspelled or defined by a module not included in the server configuration
                                                           [FAILED]

If you comment out the php_value lines in php.conf, Apache will start but then it will not load web pages, it will ask the user to download them as files, code and all!!

What I finally figured out was to simply use the yum downgrade command.

You MUST have all the dependencies along with php so I have listed them here (at least the ones for my box). If you have others, you should get a message that there are unresolved dependencies so make note of them and add them to this command. Or, remove packages you may not have installed. The downgrade command does NOT automatically downgrade dependencies the way yum update does. You have to explicitly name each package you want to downgrade.

Code:
# yum downgrade php.x86_64 php-devel.x86_64 php-ldap.x86_64 php-pdo.x86_64 php-xml.x86_64 php-mysql.x86_64 php-imap.x86_64 php-common.x86_64 php-sqlite.x86_64 php-mbstring.x86_64 php-gd.x86_64 php-cli.x86_64

I am posting this in case it can save someone else from the terror of having your production server go down.
 
Same problem here after restart Apache.
My resolution:

"yum downgrade php php-devel php-cli php-common php-gd php-soap php-pdo php-imap php-mbstring php-xml"


Removed:
php.x86_64 0:5.3.26-19.el6.art php-cli.x86_64 0:5.3.26-19.el6.art php-common.x86_64 0:5.3.26-19.el6.art php-devel.x86_64 0:5.3.26-19.el6.art php-gd.x86_64 0:5.3.26-19.el6.art
php-imap.x86_64 0:5.3.26-19.el6.art php-mbstring.x86_64 0:5.3.26-19.el6.art php-mysql.x86_64 0:5.3.26-19.el6.art php-pdo.x86_64 0:5.3.26-19.el6.art php-soap.x86_64 0:5.3.26-19.el6.art
php-xml.x86_64 0:5.3.26-19.el6.art

Installed:
php.x86_64 0:5.3.25-18.el6.art php-cli.x86_64 0:5.3.25-18.el6.art php-common.x86_64 0:5.3.25-18.el6.art php-devel.x86_64 0:5.3.25-18.el6.art php-gd.x86_64 0:5.3.25-18.el6.art
php-imap.x86_64 0:5.3.25-18.el6.art php-mbstring.x86_64 0:5.3.25-18.el6.art php-mysql.x86_64 0:5.3.25-18.el6.art php-pdo.x86_64 0:5.3.25-18.el6.art php-soap.x86_64 0:5.3.25-18.el6.art
php-xml.x86_64 0:5.3.25-18.el6.art
 
No need to downgrade. The problem is the corrupted php.conf file in the 5.3.26 update RPM. Just add these lines at the top and everything runs as smooth as always. They forgot to load the mod_php module:

Code:
#
# PHP is an HTML-embedded scripting language which attempts to make it
# easy for developers to write dynamically generated webpages.
#
<IfModule prefork.c>
  LoadModule php5_module modules/libphp5.so
</IfModule>
<IfModule worker.c>
  LoadModule php5_module modules/libphp5-zts.so
</IfModule>

Here's the detailed explanation:
http://www.atomicorp.com/forum/viewtopic.php?f=12&t=6891&sid=a2317265ae0523eb9273d9d6001f10ed
 
Thanks for the explanation. I'm not much of a Linux guy and have never had a problem with Atomic updates in many years of using them for my servers, especially for php and mysql. I did notice it appeared that the php module was not loading but didn't have the overall knowledge to figure out what to do.
I am assuming they will "fix" the packages at some point since you have alerted them to the issue.
 
Back
Top