Skip to main content

PHP 7 upgrade checklist?

Comments

8 comments

  • David_spm
    of course I decided instead of waiting for an answer to instead charge ahead and do the upgrade anyway and everything then broke :) After running the migration to EasyApache 4 via WHM nearly all my sites were down and showing this message: Your PHP installation appears to be missing the MySQL extension which is required by WordPress so Ive just done a roll back to EA3 and everything back to normal, phew! So, what do I need to do before doing the migration again but this time making sure that MYSQL doesnt break? I did some Googling and saw some people mention symlinks to modules eg here? cPanel with PHP selector shows WordPress Error "PHP installation appears to be missing the MySQL extension which is required by WordPress" also why were some sites ok? Im currently on 5.5.58-MariaDB
    0
  • David_spm
    So I have been doing some reading here on the forums and found this MySQL extension missing after looking at the sites that had this problem and the ones that didnt I can see in the .htaccess files on the sites that went down with the mysql problem after the EA4 migration they have both suPHP_ConfigPath blocks in as well as Wordfence firewall ones eg
    suPHP_ConfigPath /home/nineoh order allow,deny deny from all # BEGIN WordPress RewriteEngine On RewriteBase / RewriteRule ^index\.php$ - [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L] # END WordPress # Wordfence WAF Require all denied Order deny,allow Deny from all # END Wordfence WAF # php -- BEGIN cPanel-generated handler, do not edit # Set the "ea-php70" package as the default "PHP" programming language. # AddType application/x-httpd-ea-php70 .php .php7 .phtml # php -- END cPanel-generated handler, do not edit
    so, I guess I need to delete those two blocks from all .htaccess files for all my sites before doing the EA4 migrate again? thanks
    0
  • David_spm
    one other thing, I just ran the EA4 pre-flight check again and it returns the following, can they be ignored? Pre-flight check result. Cpanel Migrate Blocker (Cpanel) Cpanel evaluates known issues such as network connectivity Warning: "Cpanel::Easy::PHP5::MailHeaders" ignored since it does not have an RPM. Warning: "Cpanel::Easy::PHP5::MagicQuotes" ignored since it does not have an RPM. Warning: "Cpanel::Easy::Apache::SlowRestartPatch" ignored since it does not have an RPM. Warning: "Cpanel::Easy::Apache::Fileprotect" ignored since it does not have an RPM. Warning: Current profile has the following MPMs: ea-apache24-mod_mpm_prefork Warning: Adding the missing package, ea-apache24-mod_suexec, to the EasyApache 4 profile. I also found this article which addresses the WP MYSQL extensions issue, however it talks about making these changes after migrating, is there anyway to do this before to save downtime? How to Update EasyApache 3 to EasyApache 4 | InMotion Hosting
    0
  • cPanelMichael
    Hello,
    so, I guess I need to delete those two blocks from all .htaccess files for all my sites before doing the EA4 migrate again?

    You could start by removing the suphp block first, as I don't believe the WordFence entries are leading to the error messages you reported.
    Warning: "Cpanel::Easy::PHP5::MailHeaders" ignored since it does not have an RPM. Warning: "Cpanel::Easy::PHP5::MagicQuotes" ignored since it does not have an RPM. Warning: "Cpanel::Easy::Apache::SlowRestartPatch" ignored since it does not have an RPM. Warning: "Cpanel::Easy::Apache::Fileprotect" ignored since it does not have an RPM. Warning: Current profile has the following MPMs: ea-apache24-mod_mpm_prefork Warning: Adding the missing package, ea-apache24-mod_suexec, to the EasyApache 4 profile.

    These are non-fatal warnings and discussed on the following thread: EA3 to EA4 warnings, should I worry? Thank you.
    0
  • David_spm
    Hello, You could start by removing the suphp block first, as I don't believe the WordFence entries are leading to the error messages you reported. These are non-fatal warnings and discussed on the following thread: EA3 to EA4 warnings, should I worry? Thank you.

    Ok thanks, I ran the EA4 update again and then all the php module updates after and all seems ok now. Just one last question, when I did the EA4 migrate in WHM I saw lots of errors like this in the output after, is this anything I need to fix? (XID uqm7jb) The system failed to set the permissions on "/home/myasus" to "0711" (as EUID: 533, EGID: 99 99) because of the following error: Operation not permitted at /usr/local/cpanel/scripts/enablefileprotect line 101. (XID z33azh) The system failed to set the permissions on "/home/hollyw" to "0711" (as EUID: 534, EGID: 99 99) because of the following error: Operation not permitted at /usr/local/cpanel/scripts/enablefileprotect line 101. (XID 3kwxg4) The system failed to set the permissions on "/home/itsecure" to "0711" (as EUID: 536, EGID: 99 99) because of the following error: Operation not permitted at /usr/local/cpanel/scripts/enablefileprotect line 101. (XID hgj539) The system failed to set the permissions on "/home/geeks" to "0711" (as EUID: 537, EGID: 99 99) because of the following error: Operation not permitted at /usr/local/cpanel/scripts/enablefileprotect line 101. (XID dj2bev) The system failed to set the permissions on "/home/english" to "0711" (as EUID: 538, EGID: 99 99) because of the following error: Operation not permitted at /usr/local/cpanel/scripts/enablefileprotect line 101. (XID qkbtxy) The system failed to set the permissions on "/home/studydrive" to "0711" (as EUID: 539, EGID: 99 99) because of the following error: Operation not permitted at /usr/local/cpanel/scripts/enablefileprotect line 101.
    0
  • cPanelMichael
    Hello, What are the permission and ownership values on your /home partition? EX:
    stat /home grep home /etc/fstab
    Thank you.
    0
  • David_spm
    Hello, What are the permission and ownership values on your /home partition? EX:
    stat /home grep home /etc/fstab
    Thank you.

    sorry I missed this, here is the output for stat /home
    File: `/home' Size: 4096 Blocks: 8 IO Block: 4096 directory Device: 803h/2051d Inode: 9961473 Links: 86 Access: (0711/drwx--x--x) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2011-09-23 07:50:20.000000000 -0400 Modify: 2017-12-19 03:28:03.032998324 -0500 Change: 2017-12-19 03:28:03.032998324 -0500
    0
  • cPanelMichael
    Hello, It's likely that files within the account home directories referenced in that output have an invalid UID or are not owned by the account username. To correct this, ensure the ownership of those files matches the default file ownership settings that you see when creating a test account. Thank you.
    0

Please sign in to leave a comment.