Apache being updated every day
With the last Apache update, cPanel has been updating Apache every day, apparently with the same modules:
Oct 8 05:37:07 server yum[24852]: Updated: ea-apache24-tools-2.4.65-4.5.2.cpanel.x86_64
Oct 8 05:37:07 server yum[24852]: Updated: ea-apache24-mod_cgi-2.4.65-4.5.2.cpanel.x86_64
Oct 8 05:37:07 server yum[24852]: Updated: ea-apache24-mod_proxy-2.4.65-4.5.2.cpanel.x86_64
Oct 8 05:37:07 server yum[24852]: Updated: ea-apache24-mod_proxy_http-2.4.65-4.5.2.cpanel.x86_64
Oct 8 05:37:07 server yum[24852]: Installed: ea-apache24-mod_remoteip-2.4.65-4.5.2.cpanel.x86_64
Oct 8 05:37:07 server yum[24852]: Updated: ea-apache24-mod_headers-2.4.65-4.5.2.cpanel.x86_64
Oct 8 05:37:07 server yum[24852]: Updated:
ea-apache24-mod_proxy_wstunnel-2.4.65-4.5.2.cpanel.x86_64
Oct 8 05:37:07 server yum[24852]: Updated: ea-apache24-mod_mpm_prefork-2.4.65-4.5.2.cpanel.x86_64
Oct 8 05:37:07 server yum[24852]: Updated: ea-apache24-2.4.65-4.5.2.cpanel.x86_64
Oct 8 05:37:07 server yum[24852]: Updated: ea-apache24-mod_ssl-2.4.65-4.5.2.cpanel.x86_64
Oct 8 05:37:07 server yum[24852]: Updated: ea-apache24-mod_expires-2.4.65-4.5.2.cpanel.x86_64
Oct 8 05:37:07 server yum[24852]: Updated: ea-apache24-mod_deflate-2.4.65-4.5.2.cpanel.x86_64
Oct 8 05:37:07 server yum[24852]: Updated: ea-apache24-mod_unique_id-2.4.65-4.5.2.cpanel.x86_64
Oct 8 05:37:07 server yum[24852]: Updated: ea-apache24-mod_suphp-0.7.2-38.46.4.cpanel.x86_64
Oct 8 05:37:07 server yum[24852]: Updated: ea-apache24-mod_proxy_fcgi-2.4.65-4.5.2.cpanel.x86_64
Oct 8 05:37:07 server yum[24852]: Updated: ea-apache24-mod_suexec-2.4.65-4.5.2.cpanel.x86_64
Oct 8 05:37:07 server yum[24852]: Installed: 1:ea-nginx-1.29.1-1.19.1.cpanel.x86_64
Due to our OS situation, we are running on cPanel Version 110.0.77 which may have something to do with it
-
Hey there! I would have expected an update to run yesterday as we usually release Apache updates on Wednesdays:
What happens if you run the following commands on the server?
yum clean all
yum makecache
yum updateDoes that show any odd output?
0 -
I can't run yum update because we have some kernel updates that we are deferring. The Apache update ran again today:
Oct 9 05:37:00 server yum[23484]: Installed: ea-wappspector-0.2.8-1.3.1.cpanel.x86_64
Oct 9 05:37:00 server yum[23484]: Updated: ea-cpanel-tools-1.0-113.128.1.cpanel.x86_64
Oct 9 05:37:15 server yum[23558]: Updated: ea-apache24-tools-2.4.65-4.5.2.cpanel.x86_64
Oct 9 05:37:15 server yum[23558]: Updated: ea-apache24-mod_cgi-2.4.65-4.5.2.cpanel.x86_64
Oct 9 05:37:15 server yum[23558]: Updated: ea-apache24-mod_proxy-2.4.65-4.5.2.cpanel.x86_64
Oct 9 05:37:15 server yum[23558]: Updated: ea-apache24-mod_proxy_http-2.4.65-4.5.2.cpanel.x86_64
Oct 9 05:37:15 server yum[23558]: Installed: ea-apache24-mod_remoteip-2.4.65-4.5.2.cpanel.x86_64
Oct 9 05:37:15 server yum[23558]: Updated: ea-apache24-mod_headers-2.4.65-4.5.2.cpanel.x86_64
Oct 9 05:37:15 server yum[23558]: Updated:
ea-apache24-mod_proxy_wstunnel-2.4.65-4.5.2.cpanel.x86_64
Oct 9 05:37:15 server yum[23558]: Updated: ea-apache24-mod_mpm_prefork-2.4.65-4.5.2.cpanel.x86_64
Oct 9 05:37:15 server yum[23558]: Updated: ea-apache24-2.4.65-4.5.2.cpanel.x86_64
Oct 9 05:37:15 server yum[23558]: Updated: ea-apache24-mod_ssl-2.4.65-4.5.2.cpanel.x86_64
Oct 9 05:37:15 server yum[23558]: Updated: ea-apache24-mod_expires-2.4.65-4.5.2.cpanel.x86_64
Oct 9 05:37:15 server yum[23558]: Updated: ea-apache24-mod_deflate-2.4.65-4.5.2.cpanel.x86_64
Oct 9 05:37:15 server yum[23558]: Updated: ea-apache24-mod_unique_id-2.4.65-4.5.2.cpanel.x86_64
Oct 9 05:37:15 server yum[23558]: Updated: ea-apache24-mod_suphp-0.7.2-38.46.4.cpanel.x86_64
Oct 9 05:37:15 server yum[23558]: Updated: ea-apache24-mod_proxy_fcgi-2.4.65-4.5.2.cpanel.x86_64
Oct 9 05:37:15 server yum[23558]: Updated: ea-apache24-mod_suexec-2.4.65-4.5.2.cpanel.x86_64
Oct 9 05:37:15 server yum[23558]: Installed: 1:ea-nginx-1.29.1-1.19.1.cpanel.x86_64
It does look like the update is not going through which would explain the retries:
ea-apache24.x86_64 2.4.62-2.3.3.cpanel @EA4
ea-apache24-config.noarch 1.0-193.197.11.cpanel @EA4
ea-apache24-config-runtime.noarch 1.0-201.212.14.cpanel @EA4
ea-apache24-mod_bwlimited.x86_64 1.4-48.56.27.cpanel @EA4
ea-apache24-mod_cgi.x86_64 2.4.62-2.3.3.cpanel @EA4
ea-apache24-mod_deflate.x86_64 2.4.62-2.3.3.cpanel @EA4
ea-apache24-mod_expires.x86_64 2.4.62-2.3.3.cpanel @EA4
ea-apache24-mod_headers.x86_64 2.4.62-2.3.3.cpanel @EA4
ea-apache24-mod_mpm_prefork.x86_64 2.4.62-2.3.3.cpanel @EA4
ea-apache24-mod_proxy.x86_64 2.4.62-2.3.3.cpanel @EA4
ea-apache24-mod_proxy_fcgi.x86_64 2.4.62-2.3.3.cpanel @EA4
ea-apache24-mod_proxy_http.x86_64 2.4.62-2.3.3.cpanel @EA4
ea-apache24-mod_proxy_wstunnel.x86_64 2.4.62-2.3.3.cpanel @EA4
ea-apache24-mod_security2.x86_64 2.9.7-1.1.52.cpanel @EA4
ea-apache24-mod_ssl.x86_64 2.4.62-2.3.3.cpanel @EA4
ea-apache24-mod_suexec.x86_64 2.4.62-2.3.3.cpanel @EA4
ea-apache24-mod_suphp.x86_64 0.7.2-36.40.16.cpanel @EA4
ea-apache24-mod_unique_id.x86_64 2.4.62-2.3.3.cpanel @EA4
ea-apache24-tools.x86_64 2.4.62-2.3.3.cpanel @EA4
I'm not seeing anything unusual in my cPanel update log0 -
If you have manually excluded the kernel updates through yum.conf then a "yum update" wouldn't affect those, and would still be the best way to get more details. I'm guessing there is a larger issue with Yum that running this manually would reveal.
0 -
I'm pretty sure I disabled automatic updates a long time ago so I'm surprised that it is trying to do this one.
cpupdate.conf
CPANEL=11.110
RPMUP=manual
SARULESUP=daily
STAGING_DIR=/usr/local/cpanel
UPDATES=dailyyum.log isn't showing any errors:
Oct 10 05:37:26 Installed: ea-wappspector-0.2.8-1.3.1.cpanel.x86_64
Oct 10 05:37:26 Updated: ea-cpanel-tools-1.0-113.128.1.cpanel.x86_64
Oct 10 05:37:43 Updated: ea-apache24-tools-2.4.65-4.5.2.cpanel.x86_64
Oct 10 05:37:43 Updated: ea-apache24-mod_cgi-2.4.65-4.5.2.cpanel.x86_64
Oct 10 05:37:43 Updated: ea-apache24-mod_proxy-2.4.65-4.5.2.cpanel.x86_64 Oct 10 05:37:43 Updated: ea-apache24-mod_proxy_http-2.4.65-4.5.2.cpanel.x86_64
Oct 10 05:37:43 Installed: ea-apache24-mod_remoteip-2.4.65-4.5.2.cpanel.x86_64
Oct 10 05:37:43 Updated: ea-apache24-mod_headers-2.4.65-4.5.2.cpanel.x86_64
Oct 10 05:37:43 Updated: ea-apache24-mod_proxy_wstunnel-2.4.65-4.5.2.cpanel.x86_64
Oct 10 05:37:43 Updated: ea-apache24-mod_mpm_prefork-2.4.65-4.5.2.cpanel.x86_64
Oct 10 05:37:43 Updated: ea-apache24-2.4.65-4.5.2.cpanel.x86_64
Oct 10 05:37:43 Updated: ea-apache24-mod_ssl-2.4.65-4.5.2.cpanel.x86_64
Oct 10 05:37:43 Updated: ea-apache24-mod_expires-2.4.65-4.5.2.cpanel.x86_64
Oct 10 05:37:43 Updated: ea-apache24-mod_deflate-2.4.65-4.5.2.cpanel.x86_64
Oct 10 05:37:43 Updated: ea-apache24-mod_unique_id-2.4.65-4.5.2.cpanel.x86_64
Oct 10 05:37:43 Updated: ea-apache24-mod_suphp-0.7.2-38.46.4.cpanel.x86_64
Oct 10 05:37:43 Updated: ea-apache24-mod_proxy_fcgi-2.4.65-4.5.2.cpanel.x86_64
Oct 10 05:37:43 Updated: ea-apache24-mod_suexec-2.4.65-4.5.2.cpanel.x86_64
Oct 10 05:37:43 Installed: 1:ea-nginx-1.29.1-1.19.1.cpanel.x86_64This is my yum.conf, I doubt that I ever made any manual changes to this:
[main]
exclude=courier* dovecot* exim* filesystem httpd* mod_ssl* mydns* nsd* p0f php* proftpd* pure-ftpd* spamassassin* squirrelmail*
tolerant=1
errorlevel=1
cachedir=/var/cache/yum/$basearch/$releasever
keepcache=0
debuglevel=2
logfile=/var/log/yum.log
exactarch=1
obsoletes=1
gpgcheck=1
plugins=1
installonly_limit=5
bugtracker_url=http://bugs.centos.org/set_project.php?project_id=23&ref=http://bugs.centos.org/bug_report_page.php?category=yum
distroverpkg=centos-release
# This is the default, if you make this bigger yum won't see if the metadata
# is newer on the remote and so you'll "gain" the bandwidth of not having to
# download the new metadata and "pay" for it by yum not having correct
# information.
# It is esp. important, to have correct metadata, for distributions like
# Fedora which don't keep old packages around. If you don't like this checking
# interupting your command line usage, it's much better to have something
# manually check the metadata once an hour (yum-updatesd will do this).
# metadata_expire=90m
# PUT YOUR REPOS HERE OR IN separate files named file.repo
# in /etc/yum.repos.dI would rather not have cPanel attempting to do an Apache update since I specifically turned everything except cPanel updates off so they can be done manually when I can schedule it.
0 -
You could change the "UPDATES=daily" line to "UPDATES=manual" and that should keep anything else from attempting to update, as everything else is already turned off in your configuration.
Is there a reason this server is specifically pinned to version 110?
0 -
We are on cPanel 110 because our server is frozen at CentOS 7 due to other software limitations. I have kept UPDATES=daily because to my understanding the 110 version track is still being maintained to deliver support for the Extended Lifecycle Support (ELS) program through January 2027.
According to cPanel documentation:All CentOS 7 and CloudLinux 7 servers on cPanel version 110 are enrolled in the ELS program.
•
•
•
These servers will also receive critical security updates and technical support for cPanel & WHM version 110Also, according to cPanel documentation on cpupdate.conf:
UPDATES
This setting determines how to update cPanel & WHM when updates become available.That's why I was confused when the Apache update failure came through on our logs.
If the Apache update is compatible with our system, I would probably go ahead and update it but something is causing it to fail (even though yum says it was installed) and it's not in any logs that I can find.
Is there a way to run the cPanel script that is trying to do the update and have it log extra information (such as a verbose parameter)?0 -
Ah, CentOS 7 - that all makes sense then.
EasyApache packages are not tied to the cPanel version and are part of the standard "yum update" on the machine, so cPanel itself isn't doing anything special with that.
0 -
This is still broken and now we are getting an additional update failure after the daily Apache set:
Oct 22 05:37:42 server yum[8733]: Updated: cpanel-analytics-1.4.57-12.14.1.cpanel.noarch
yum list installed cpanel-analytics
Loaded plugins: fastestmirror, universal-hooks
Loading mirror speeds from cached hostfile
* EA4: 185.125.185.32
* cpanel-addons-production-feed: 185.125.185.32
* cpanel-plugins: 185.125.185.32
* epel: mirror.math.princeton.eduInstalled Packages
cpanel-analytics.noarch 1.4.57-11.13.1.cpanel @cpanel-plugins
0 -
I ran the one cpanel-analytics module update from the command line and it seemed to work fine:
yum list installed cpanel-analytics
Loaded plugins: fastestmirror, universal-hooks
Loading mirror speeds from cached hostfile
* EA4: 185.125.185.32
* cpanel-addons-production-feed: 185.125.185.32
* cpanel-plugins: 185.125.185.32
* epel: d2lzkl7pfhq30w.cloudfront.netInstalled Packages
cpanel-analytics.noarch 1.4.57-12.14.1.cpanel @cpanel-pluginsI'll check in the morning after the cPanel maintenance run to see if cPanel is happy with the update
Also, checking through the nightly logs cPanel did apparently successfully update itself on 10-17 to 11.110.0.790 -
Following up, cPanel recognizes the cpanel-analytics update I did manually and is no longer attempting to update it. All of the ea-apache24-mod failed updates are still happening each morning.
0 -
Could you make a ticket? This thread has been going off and on for a couple weeks now, but a ticket would resolve this quickly.
0 -
I can't open tickets anymore since I have a "Partner Supported License"
0 -
You can *always* create a ticket with the Partner, and then they'd escalate to us if they can't solve the issue.
0
Please sign in to leave a comment.
Comments
13 comments