After doing a test upgrade to EasyApache 4 PHP completely stopped rendering, I double checked to make sure PHP was in fact installed, and all accounts were configured to inherit the default (which was PHP 5.6) but it was just outputting all PHP pages as plain text. Anyone run into this issue after updating from EasyApache 3?
Hello,
It seems like the issue is potentially related to the discussion on the following thread:
MySQL extension missing
Could you let us know if that thread is helpful?
Thank you.
It seems like the issue is potentially related to the discussion on the following thread:
MySQL extension missing
Could you let us know if that thread is helpful?
Thank you.
I don't think so, nobody has any custom php.ini files. But I just did another upgrade on the same server (after having downgraded it back to EasyApache 3) and it seems to behave as expected so far
I'm happy to see the second conversion attempt succeeded. Let us know if you encounter any additional issues.
Thank you.
Yes I saw this problem amongst several others trying to get EA3 to EA4 to work. The first attempt this didn't happen but the profile it built in EA4 had NO php extensions. The list was blank. Nothing to toggle on or off which is odd as the php that was installed clearly did have extensions.
The second time I got the problem described here. PHP pages were triggering a "where would you like to save the php file." It happened about half the time I loaded the page. The other half of the time it was loading the php correctly from the still running EA3 apache/php. I know this because the php software running gave me the exact build date from my previous EA4 to EA3 fallback when it worked. I also kept getting suspicious process emails from lfd about /usr/local/apache.ea3/bin/httpd. I got them all through the second conversion and after but never during the first.
Since I didn't see an obvious set of EA3 processes to shutdown in ps and I didn't really want all the php config files world readable I rebooted the server and after that the new EA4 server was working normally.
The EA3 to EA4 migration tool clearly needs work.
The second time I got the problem described here. PHP pages were triggering a "where would you like to save the php file." It happened about half the time I loaded the page. The other half of the time it was loading the php correctly from the still running EA3 apache/php. I know this because the php software running gave me the exact build date from my previous EA4 to EA3 fallback when it worked. I also kept getting suspicious process emails from lfd about /usr/local/apache.ea3/bin/httpd. I got them all through the second conversion and after but never during the first.
Since I didn't see an obvious set of EA3 processes to shutdown in ps and I didn't really want all the php config files world readable I rebooted the server and after that the new EA4 server was working normally.
The EA3 to EA4 migration tool clearly needs work.
Hello @Oceans,
Internal case CPANEL-7619 was implemented to preserve EasyApache 3's PHP version as the default PHP version when the system migrates to EasyApache 4. CPANEL-7659 was implemented to preserve EasyApache 3's PHP handler when the system migrates to EasyApache 4. The following document now lists active issues with EasyApache 4:
Current Status of EasyApache 4 - EasyApache 4 - cPanel Documentation
Let us know if you experience any additional problems.
Thank you.
Internal case CPANEL-7619 was implemented to preserve EasyApache 3's PHP version as the default PHP version when the system migrates to EasyApache 4. CPANEL-7659 was implemented to preserve EasyApache 3's PHP handler when the system migrates to EasyApache 4. The following document now lists active issues with EasyApache 4:
Current Status of EasyApache 4 - EasyApache 4 - cPanel Documentation
Let us know if you experience any additional problems.
Thank you.