Beta Branch updated workaround for CentOS 7 EOL repo closures in 140.00beta01

updated workaround for CentOS 7 EOL repo closures in 140.00beta01

- CentOS 7 is end of life as of June 30, 2024 so no more security or bug fix updates via official YUM repos. For migration options read https://community.centminmod.com/threads/centos-7-end-of-life-eol-june-30-2024.25589/.
- CentOS folks have been quick to disable their YUM repos as YUM repo's mirror.centos.org etc are now no longer working. This update disables broken YUM repos and switches CentOS 7 mirrorlist.centos.org to archive vault.centos.org to prevent YUM repo errors when you run yum.
- Existing Centmin Mod users can run cmupdate command and then, run and exit centmin.sh once to apply the workarounds

---

Continue reading...

140.00beta01 branch

• Branch: https://github.com/centminmod/centminmod/tree/140.00beta01
• Commit History: https://github.com/centminmod/centminmod/commits/140.00beta01

 

What does your /etc/yum.repos.d/kernelcare.repo contents look like ? like below?

Code (Text):

[kernelcare]
name=kernelcare
baseurl=https://repo.cloudlinux.com/kernelcare/$releasever/$basearch
enabled=1
gpgcheck=1
gpgkey=https://repo.cloudlinux.com/kernelcare/RPM-GPG-KEY-KernelCare

Pretty sure unrelated as that is CloudLinux KernelCare YUM repo and not CentOS releated. Can you ping their repo URL? Any packet loss ?

Code (Text):

ping -c4 repo.cloudlinux.com

Code (Text):

curl -I https://repo.cloudlinux.com
HTTP/1.1 200 OK
Server: nginx
Date: Mon, 01 Jul 2024 19:48:09 GMT
Content-Type: text/html
Content-Length: 0
Last-Modified: Mon, 21 Nov 2016 19:01:46 GMT
Connection: keep-alive
ETag: "5833449a-0"
Strict-Transport-Security: max-age=63072000; includeSubdomains
X-Frame-Options: DENY
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Accept-Ranges: bytes