在 AWS 上創建 EC2 實體后，我已使用 SSH（PEM 檔案）連接到服務器，并且我正在嘗試在服務器上安裝 Cpanel，但在嘗試更新或安裝任何內容時出現此錯誤。
我的命令：
yum update
我得到的錯誤：
amzn2extra-docker | 3.0 kB 00:00:00
amzn2extra-epel | 3.0 kB 00:00:00
amzn2extra-kernel-5.10 | 3.0 kB 00:00:00
epel/x86_64/metalink | 14 kB 00:00:00
remi-safe | 3.0 kB 00:00:00
http://r.vestacp.com/cmmnt//x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
One of the configured repositories failed (Vesta - cmmnt),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:
1. Contact the upstream for the repository and get them to fix the problem.
2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).
3. Run the command with the repository temporarily disabled
yum --disablerepo=vesta ...
4. Disable the repository permanently, so yum won't use it by default. Yum
will then just ignore the repository until you permanently enable it
again or use --enablerepo for temporary usage:
yum-config-manager --disable vesta
or
subscription-manager repos --disable=vesta
5. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:
yum-config-manager --save --setopt=vesta.skip_if_unavailable=true
failure: repodata/repomd.xml from vesta: [Errno 256] No more mirrors to try.
http://r.vestacp.com/cmmnt//x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
PS我使用的是root用戶。
軟體版本：亞馬遜 Linux 2
uj5u.com熱心網友回復：
我已經嘗試了錯誤提示的選項，但沒有一個有效，這就是我解決這個問題的方法
cd /etc/yum.repos.d
然后
rm vesta.repo
現在 Yum 更新和安裝任何軟體包都可以正常作業。
uj5u.com熱心網友回復：
可能是vesta repo 的url 不正確。
無論如何，如果你不需要它，你可以洗掉它，就像你做的那樣。
但是你也可以禁用那個有問題的倉庫：
sed -i 's/enabled=1/enabled=0/g' /etc/yum.repos.d/vesta.repo
轉載請註明出處，本文鏈接：https://www.uj5u.com/yidong/420361.html
標籤：
上一篇：AWS檢查StateMachines/StepFunctions并發運行
下一篇：如何使ec2實體埠安全