Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
[root@bootserver yum.repos.d]# yum list
Loaded plugins: langpacks, product-id, subscription-manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
file:///var/rhel7/mount/repo/repodata/repomd.xml: [Errno 14] curl#37 - "Couldn't open file /var/rhel7/mount/repo/repodata/repomd.xml"
Trying other mirror.
One of the configured repositories failed (rhel7),
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. Disable the repository, 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 bootserver
4. 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:
failure: repodata/repomd.xml from bootserver: [Errno 256] No more mirrors to try.
file:///var/rhel7/mount/repo/repodata/repomd.xml: [Errno 14] curl#37 - "Couldn't open file /var/rhel7/mount/repo/repodata/repomd.xml
Did you run createrepo against /var/rhel7/mount/repo? Without that command you will not have repomd.xml file unless you have copied repos and it contents as it is from another location.
Since you're 'certified', shouldn't you know such things? Especially after five years working with it, or at least know how to access Red Hat's knowledgebase, where you can find such things?? And as you've been told several times in the past, you need to PAY FOR RED HAT ENTERPRISE. Using RHEL without paying is a bad idea...all you're going to accomplish is to have a system that's insecure, unpatched, unupdated, and more difficult to maintain. What's the point of RHEL without Red Hat support and updates?? Load CentOS instead.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.