EasyApache updated now clients site down...
Hey Guys,
Did a security advisor run and it told me to update EasyApache, which I did and I loaded the default profile etc so everything 'would stay the same'.
I now have a client that has a web site down and I cant understand why.
error log from clients site:
1) He is running Joomla 2) PHP is 5.4.45 I get the impression PHP got updated when I updated EasyApache and now there is some incompatibility? How to fix this? Thanks in advance!
[28-Sep-2015 07:00:12 America/Denver] PHP Warning: PHP Startup: PDO: Unable to initialize module
Module compiled with module API=20060613
PHP compiled with module API=20100525
These options need to match
in Unknown on line 0
[28-Sep-2015 07:00:12 America/Denver] PHP Warning: PHP Startup: Unable to load dynamic library '/opt/php52/lib/php/extensions/no-debug-non-zts-20060613/sqlite.so' - /opt/php52/lib/php/extensions/no-debug-non-zts-20060613/sqlite.so: undefined symbol: third_arg_force_ref in Unknown on line 0
[28-Sep-2015 07:00:12 America/Denver] PHP Warning: PHP Startup: pdo_mysql: Unable to initialize module
Module compiled with module API=20060613
PHP compiled with module API=20100525
These options need to match
in Unknown on line 0
[28-Sep-2015 07:00:12 America/Denver] PHP Fatal error: Directive 'allow_call_time_pass_reference' is no longer available in PHP in Unknown on line 0
1) He is running Joomla 2) PHP is 5.4.45 I get the impression PHP got updated when I updated EasyApache and now there is some incompatibility? How to fix this? Thanks in advance!
-
Were you previously running PHP 5.2? Does that user have a customer php.ini and are you using CloudLinux with PHP selector? Off the top of my head I don't recall '/opt/php*', I would search their account for a custom php.ini which could be causing problems and rename it to something else so its not being used. 0 -
I think we had 5.4 and 5.2 running side by side. I think with the upgrade that the configuration of 5.2 died? They dont have custom php.ini files 0 -
Yeah sounds like that's what happened for sure, I would contact HG in that case. 0 -
Yeah, that was it. I am not sure how it was previously setup to 'force' the clients to use 5.2 but I modified the affected clients .htaccess to force the use of 5.2 and they all started working again. Thanks for the help :) 0 -
Ah glad to hear it :) 0 -
Hello :) It's important to note that using the same EasyApache build profile does not guarantee versions remain the same. For instance, if PHP 5.2 is no longer offered in EasyApache, the next build you run will automatically choose the default version of PHP. Thank you. 0
Please sign in to leave a comment.
Comments
6 comments