- 3,725,891 Users
- 2,245,077 Discussions
- 7,851,912 Comments
Forum Stats
Discussions
Categories
- Industry Applications
- 3.2K Intelligent Advisor
- Insurance
- 1.6K On-Premises Infrastructure
- 554 Analytics Software
- 47 Application Development Software
- 1.8K Cloud Platform
- 700.5K Database Software
- 17.5K Enterprise Manager
- 20 Hardware
- 265 Infrastructure Software
- 138 Integration
- 70 Security Software
Metadata file does not match checksum
Have an OL7.4 VM which I want to upgrade to OL7.5 (latest).
Running:
yum clean all; rm -rf /var/cache/yum; yum makecache
Fails with:
http://yum.oracle.com/repo/OracleLinux/OL7/UEKR4/x86_64/repodata/primary.xml.gz: [Errno -1] Metadata file does not match checksum
Have tried several times over the last 2 hours - same result.
Am I doing something wrong?
Answers
-
Avi Miller-Oracle Senior Solution Architect, Oracle Cloud Infrastructure Developer Adoption Melbourne, AustraliaPosts: 4,793 EmployeeYou're not, but our CDN is: we're having issues with Akamai clearing the cache on some of its leaf nodes. We're doing our best to kick it as hard as possible.
-
Thanks Avi.
Any idea when it will be kicked into submission? Just checked now and the issue is still there.
-
Thanks. Will try. Mine sees:
yum.oracle.com is an alias for public-yum.oracle.com.edgekey.net.public-yum.oracle.com.edgekey.net is an alias for e14618.g.akamaiedge.net.e14618.g.akamaiedge.net has address 104.94.88.253
-
Does not work (have to use a web proxy). Seems like the hostname resolution happens on the proxy (which makes sense).
Using the IP address directly (e.g. http://104.127.51.166/repo/OracleLinux/OL7/UEKR4/x86_64/repodata/repomd.xml) fails - seems like the CDN server expects the hostname in the URL and not IP.
-
Not the web proxy caching, but it doing the hostname resolution to IP - thus my server's hosts file is not relevant. Which is why I tried the CDN node's IP instead. But that CDN web server likely use virtual hosts, and need the Oracle yum hostname to service the http calls from yum.
Do have ULN for a bunch of servers - will have a look if an alternative yum repository hostname is available. Never used the CSI (which I registered years ago) as far as I recall - unlike our RDBMS related CSI... ;-)
-
Dude! wrote:I wonder though why resolving via the hostsfile shouldn't work.
The local yum http client sends the http GET command (which includes the yum repo hostname) to the web proxy, as is - where the web proxy resolves it to an IP. Thus my local server's host file is not relevant, and the web proxy server's host file needs changing.
Web proxies are owned by group IT, are Windows based I think, and I do not have (or really want) access to these servers. Thus no host file changing. Besides, I dislike sysadmin'ing non-Linux/Unix server platforms.
-
Avi Miller-Oracle Senior Solution Architect, Oracle Cloud Infrastructure Developer Adoption Melbourne, AustraliaPosts: 4,793 EmployeeBilly~Verreynne wrote:Does not work (have to use a web proxy). Seems like the hostname resolution happens on the proxy (which makes sense).
If you're using a proxy, then the proxy is the problem: it has cached the incorrect metadata and your attempts to get new metadata is failing because the proxy is just serving broken cached version. My suggestion is to switch your repos to use https instead (yes, we've enabled https on yum.oracle.com) so that the content is never cached by a proxy server.
-
Thanks Avi - will try the suggestion.
-
Problem has disappeared this morning - probably because the whatever CDN or proxy caches expired old data because of the weekend's "alternative" surfed contents? ;-)