Hello,
Yes it will indeed change to 7.4.5-X.X.X.cpanel (I don't know what the cPanel specific revision numbers will be yet)
Yes it will indeed change to 7.4.5-X.X.X.cpanel (I don't know what the cPanel specific revision numbers will be yet)
Nope, you can immediately update once the packages are available on the EA4 repo, I'll let you know how as soon as I get word that the repo is updated.Thank you.
So when the 7.4.5-X.X.X.cpanel is released, we need to wait until EasyApache 4 automatically updates itself?
What other issues have you seen?I see lots of fixes leading up to php 7.4.5
-bash-4.2# ea-php74-pecl install APCu
-bash-4.2# ea-php74 --ri apcu
apcu
APCu Support => Disabled <==
Version => 5.1.18
APCu Debugging => Enabled
==Add "apc.enabled_cli=1"==
-bash-4.2# grep apc /opt/cpanel/ea-php74/root/etc/php.d/zzzzzzz-pecl.ini
extension="apcu.so"
apc.enable_cli=1
-bash-4.2# ea-php74 --ri apcu
apcu
APCu Support => Enabled
Version => 5.1.18
APCu Debugging => Enabled
MMAP Support => Enabled
MMAP File Mask =>
Serialization Support => php
Build Date => Apr 22 2020 10:27:17
Directive => Local Value => Master Value
apc.enabled => On => On
apc.shm_segments => 1 => 1
apc.shm_size => 256M => 256M
apc.entries_hint => 4096 => 4096
apc.gc_ttl => 3600 => 3600
apc.ttl => 7200 => 7200
apc.smart => 0 => 0
apc.mmap_file_mask => no value => no value
apc.enable_cli => On => On
apc.slam_defense => On => On
apc.preload_path => no value => no value
apc.coredump_unmap => Off => Off
apc.use_request_time => On => On
apc.serializer => php => php
-bash-4.2# ea-php74 apcu.php
string(3) "BAR"
string(3) "BAR"
Hey Guys,
I want to get ahead of this before EA4 is updated today. I've just been told that the GD fix did not make it into today's build. But I've been promised it will be added first thing tomorrow. So I'll update here when EA4 is released and I will update again when the fix for GD is released tomorrow. I'm sorry for the delay, they just weren't able to get it resolved in time and the importance of updating the rest took precedence.
Well it wouldn't actually be revision 1.1.2 of PHP 7.4.5 I suppose- it would be if it was an update of 7.4.5This morning I checked EasyApache 4 and i see this:
View attachment 64917
What is confusing to me is that it appears to be installed already. Does this mean that when EasyApache 4 auto upgrades it will install the latest version of PHP?
I assume the new version of PHP74 which will be released today will have a version number like 7.4.5-1.1.2.
Monitoring here: EasyApache 4 Change Log 2020 | cPanel & WHM DocumentationReminder: The GD Fix with JPEG support is coming today and I will update here as soon as it's added.
Yes fixed but have new issue with this update. The provision process exited with errors. Please check the log for details.The GD fix was just pushed guys. Please let us know if you notice any issues.
[2020-04-24 01:33:37 +0600] info [xml-api] [Fri Apr 24 00:00:57.432790 2020] [:error] [pid 1166:tid 47631543867136] [client 93.190.138.231:61437] [client 93.190.138.231] ModSecurity: Warning. String match "Invalid URI in request" at WEBSERVER_ERROR_LOG. [file "/etc/apache2/conf.d/modsec_vendor_configs/comodo_apache/12_HTTP_Protocol.conf"] [line "14"] [id "210210"] [rev "2"] [msg "COMODO WAF: Apache Error: Invalid URI in Request.||www.mysite.com|F|4"] [data "GET www.mysite.com HTTP/1.0"] [severity "WARNING"] [tag "CWAF"] [tag "Protocol"] [hostname "www.mysite.com"] [uri "/400.shtml"] [unique_id "XqHX2QMjH8lIAJzbr8dDmwAAAAs"]
How to get this fix?The GD fix was just pushed guys. Please let us know if you notice any issues.
I'd suggest disabling COMODO WAF and attempting to provision again. This isn't related to the EasyApache update process at all, it's specific to the 3rd party plugin.Yes fixed but have new issue with this update. The provision process exited with errors. Please check the log for details.
Code:[2020-04-24 01:33:37 +0600] info [xml-api] [Fri Apr 24 00:00:57.432790 2020] [:error] [pid 1166:tid 47631543867136] [client 93.190.138.231:61437] [client 93.190.138.231] ModSecurity: Warning. String match "Invalid URI in request" at WEBSERVER_ERROR_LOG. [file "/etc/apache2/conf.d/modsec_vendor_configs/comodo_apache/12_HTTP_Protocol.conf"] [line "14"] [id "210210"] [rev "2"] [msg "COMODO WAF: Apache Error: Invalid URI in Request.||www.mysite.com|F|4"] [data "GET www.mysite.com HTTP/1.0"] [severity "WARNING"] [tag "CWAF"] [tag "Protocol"] [hostname "www.mysite.com"] [uri "/400.shtml"] [unique_id "XqHX2QMjH8lIAJzbr8dDmwAAAAs"]
You'd just need to ensure that it's included in your EasyApache profile then set whichever domains you'd like to use it in the MultiPHP Manager.What do we need to do in WHM to use this new version of php74? I show this currently in EasyApache 4.
Do the following first to clear your cache:How to get this fix?
yum -y update
doesnt make the trick, it says no packages marked for update
yum clean all
This error does not happened before. I am not using COMODO WAF. We are using ModSecurity with COMODO ModSecurity Rules for Apache.I'd suggest disabling COMODO WAF and attempting to provision again. This isn't related to the EasyApache update process at all, it's specific to the 3rd party plugin.