Not using downloaded cpanel-plugins/repomd.xml
After a recent reboot, every few hours I am now receiving an email from my Cron Daemon with the following information:
/etc/cron.hourly/0yum-hourly.
cron:
Not using downloaded cpanel-plugins/repomd.xml because it is older than what we have:
Current : Wed Jan 3 07:02:02 2018
Downloaded: Mon Nov 13 11:56:52 2017
I've run a software update, to no avail. Suggestions on how to fix this issue?
-
Hello, Can you let us know the contents of the /etc/cron.hourly/0yum-hourly file? EX: cat /etc/cron.hourly/0yum-hourly
Ensure to replace any identifying information about the server with examples. Thank you.0 -
Getting the exact same error on my server with slightly different times. /etc/cron.hourly/0yum-hourly.cron: Not using downloaded cpanel-plugins/repomd.xml because it is older than what we have: Current : Wed Jan 3 15:02:02 2018 Downloaded: Mon Nov 13 19:56:52 2017 0 -
Hello, Can you let us know the contents of the /etc/cron.hourly/0yum-hourly file? EX:
cat /etc/cron.hourly/0yum-hourly
Ensure to replace any identifying information about the server with examples. Thank you.
Looks like it doesn't exist.[root@host ~]# cat /etc/cron.hourly/0yum-hourly cat: /etc/cron.hourly/0yum-hourly: No such file or directory
0 -
same, get No such file or directory 0 -
missed out the .cron extension in the cat command. contents below : #!/bin/bash # Only run if this flag is set. The flag is created by the yum-cron init # script when the service is started -- this allows one to use chkconfig and # the standard "service stop|start" commands to enable or disable yum-cron. if [[ ! -f /var/lock/subsys/yum-cron ]]; then exit 0 fi # Action! exec /usr/sbin/yum-cron /etc/yum/yum-cron-hourly.conf 0 -
Hi, Thank you for your reports @Lee Young and @Dezdan. This is an issue with the update server mirrors being out of sync. You may safely ignore the email alert for now. The sysadmin team has already been made aware of this issue. I'll update this post once our sysadmin team reports it has been resolved. Edit: Our sysadmin team is already reviewing the issue Edit1: Issue identified, fix still underway Edit2: All mirrors should be corrected at this time; you may see some residual emails/alerts though. You may want to issue `yum clean all' or a `yum makecache' to force the update; however, it should be corrected by itself. If you continue to face issues, please update this thread or open a ticket. Thanks, 0 -
Hey guys. It's 2021 and I'm getting the same exact errors reported in this thread. How can I manually fix/sync the mirrors being used for download? 0 -
@Kent Brockman - I'm actually not aware of any recent mirror issues on our end. In order to clear that mirror history you can do the following: echo "" > /root/.HttpRequest/httpupdate.cpanel.net /scripts/upcp --force
as that will rebuild the IP list the system uses to check for cPanel udpates.0 -
@Kent Brockman - I'm actually not aware of any recent mirror issues on our end. In order to clear that mirror history you can do the following:
echo "" > /root/.HttpRequest/httpupdate.cpanel.net /scripts/upcp --force
as that will rebuild the IP list the system uses to check for cPanel udpates.
Thank you very much. That worked great. I'll add it to our FAQ.0 -
I'm glad that worked well! 0 -
Also getting similar warnings. Mail contents: > /etc/cron.hourly/0yum-hourly.cron: > > Could not get metalink Not using downloaded cpanel-plugins/repomd.xml because it is older than what we have: > Current : Wed Dec 1 17:28:03 2021 > Downloaded: Wed Nov 24 22:44:51 2021 0 -
#MeToo Me too, the same warning every hour arrived in the mailboxes from different server's. The time stamps are same like @Bramus / suggestions above doesn't work for me. > /etc/cron.hourly/0yum-hourly.cron: > > Not using downloaded cpanel-plugins/repomd.xml because it is older than what we have: > Current : Wed Dec 1 17:28:03 2021 > Downloaded: Wed Nov 24 22:44:51 2021 0 -
I will check to see if I can find similar instances of this issue as of recently. 0 -
@cPanelAnthony Thank you for your response. Sure, there is a solution for that. There is a solution for everything, it just must be found We have this issue only with all our DNSonly servers. The normal cPanel servers are not affected. 0
Please sign in to leave a comment.
Comments
14 comments