Skip to main content

Update PHP to 5.6.27 with EasyApache4. Running PHP-FPM

Comments

9 comments

  • cPanelKenneth
    If you restart the FPM process (/scripts/restartsrv_apache_php_fpm) do you get the correct PHP version?
    0
  • dogdog
    If you restart the FPM process (/scripts/restartsrv_apache_php_fpm) do you get the correct PHP version?

    Thanks for the suggestion but no,that didn't work I'm afraid.
    0
  • dogdog
    I've just realized that the build date for PHP, as listed in the output of the phpinfo() function, is 3 weeks ago. From what I've read on here the only way to force a rebuild of PHP in EA4 is to remove the PHP version then add it again later, but I have installed a few extra PHP modules so I don't want to have to recreate the same build later if I can avoid this drastic step. Are there any other options?
    0
  • sparek-3
    Has cPanel release 5.6.27 for EA4?
    0
  • cPStacy
    The EasyApache 4 RPMs did not go out yesterday. We updated EasyApache 3, but not EasyApache 4. We're expecting to push the EA4 RPMs later this afternoon. When the update is available, we'll post both here on the forum, and in the change log: EasyApache 4 Change Log - EasyApache 4 - cPanel Documentation Sorry for the confusion!
    0
  • dogdog
    OK that explains it. Someone there sent out an email yesterday with the following line: "SUMMARY cPanel, Inc. has released updated RPMs for EasyApache 4 on September 20, 2016, with PHP versions 5.6.27 and 7.0.12." So you can understand why I thought I should have PHP 5.6.27.
    0
  • cPStacy
    OK that explains it. Someone there sent out an email yesterday with the following line: "SUMMARY cPanel, Inc. has released updated RPMs for EasyApache 4 on September 20, 2016, with PHP versions 5.6.27 and 7.0.12." So you can understand why I thought I should have PHP 5.6.27.

    Oh, absolutely! We DID originally plan to release it yesterday but had to delay it another day. Evidently our email blast system didn't fully cancel the scheduled email like it was supposed to. Sorry for the inconvenience there!
    0
  • sparek-3
    Curious as to why it says September 20, 2016
    0
  • cPStacy
    Curious as to why it says September 20, 2016

    Probably my fault. I must have missed that date when updating the CVE notice template.
    0

Please sign in to leave a comment.