Difference between revisions of "CentOS 7.x troubleshooting yum issues"
(Created page with "<yambe:breadcrumb>CentOS_7.x_yum|CentOS 7.x yum</yambe:breadcrumb> =CentOS7.x troubleshooting yum issues= ==repomd.xml does not match metalink for epel== This problem may ha...") |
m |
||
Line 1: | Line 1: | ||
[[Main Page|Home]] > [[CentOS]] > [[CentOS 7.x]] > [[CentOS 7.x system administration|System Administration]] > [[CentOS 7.x package management|Package management]] > [[CentOS 7.x yum|Yum]] > [[CentOS 7.x troubleshooting yum issues]] | |||
==repomd.xml does not match metalink for epel== | ==repomd.xml does not match metalink for epel== | ||
Line 14: | Line 13: | ||
This is just a high level fix. The actual issue is often caused by ISP/security devices which redirect any request to a standard advertizement / login page. Often yum ends up downloading that advertizement / login page and hence metadata check fails. Opening any URL such as 'http://www.sbarjatiya.com', before running yum, after cleaning metadata might help in avoiding the issue to reappear. | This is just a high level fix. The actual issue is often caused by ISP/security devices which redirect any request to a standard advertizement / login page. Often yum ends up downloading that advertizement / login page and hence metadata check fails. Opening any URL such as 'http://www.sbarjatiya.com', before running yum, after cleaning metadata might help in avoiding the issue to reappear. | ||
[[Main Page|Home]] > [[CentOS]] > [[CentOS 7.x]] > [[CentOS 7.x system administration|System Administration]] > [[CentOS 7.x package management|Package management]] > [[CentOS 7.x yum|Yum]] > [[CentOS 7.x troubleshooting yum issues]] |
Latest revision as of 06:54, 25 August 2022
Home > CentOS > CentOS 7.x > System Administration > Package management > Yum > CentOS 7.x troubleshooting yum issues
repomd.xml does not match metalink for epel
This problem may happen if there is wrong metadata cached for particular repistory. To solve this use:
yum --enablerepo=epel clean metadata
and try the yum command again. This time fresh metadata would be built. If you want to clear metadata for all repositories then use:
yum clean metadata
This is just a high level fix. The actual issue is often caused by ISP/security devices which redirect any request to a standard advertizement / login page. Often yum ends up downloading that advertizement / login page and hence metadata check fails. Opening any URL such as 'http://www.sbarjatiya.com', before running yum, after cleaning metadata might help in avoiding the issue to reappear.
Home > CentOS > CentOS 7.x > System Administration > Package management > Yum > CentOS 7.x troubleshooting yum issues