[WorksForMe] Unable to Reach VirtualBox Repo via Yum on CentOS

[jeff112323541351]

I am unable to install VirtualBox on CentOS 7.7 using Yum. I added the VirtualBox repo file (/rpm/el/virtualbox.repo) to /etc/yum.repos.d/. When trying to search for VirtualBox or do a 'yum repolist', Yum cannot find the /rpm/el/latest/x86_64/repodata/repomd.xml file.

I looked around in org/virtualbox/rpm/el/ and there is no latest directory (or symbolic link pointing to the latest version). I tried the basic troubleshooting steps, like removing the Yum cache and 'yum clean all', but no change.

I could not put the full link addresses because the forum is prohibiting me from doing so.

[socratis]

Is that still the case? There was a glitch with the repositories, can you try again?

[jeff112323541351]

I tried again today and the errors are different. Now Yum is looking in http://download.virtualbox.org/virtualb ... /repodata/ (which is a valid path), but I am still getting 404 errors when running 'yum repolist' or 'yum install virtualbox'. Output of 'yum repolist':

virtualbox/7/x86_64/primary_db FAILED
http://download.virtualbox.org/virtualb ... sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
http://download.virtualbox.org/virtualb ... sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
virtualbox/7/x86_64/primary_db FAILED
http://download.virtualbox.org/virtualb ... sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
http://download.virtualbox.org/virtualb ... sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found

The current sqlite.bz2 files have a hex prefix different from 521c97e54890e583573e9b5a48288fdd6630631e5a6fcb14e587669c7807a14e.

[klaus]

Sounds like stale/inconsistent repomd.xml data on your end (this file references the others), because on our side it seems to be consistent. Last updated about 44h ago.

Try running "yum clean all" (throws away all cached repo information) and see if things work afterwards again.

[jeff112323541351]

As I mentioned in my first post, I tried running 'yum clean all'. I am constantly deploying new AWS instances that encounter this issue, so I don't think it was related to a stale cache.

[jeff112323541351]

It works now. Followed the exact same steps, not quite sure what changed.

[socratis]

Glad you finally got it going. Marking as [WorksForMe].