1 Reply Latest reply on May 31, 2018 7:11 PM by Robert Chase

    Failed yum repository

    Raghav_DBA

      [root@cassandra ~]# yum update

      Loaded plugins: langpacks, ulninfo

      ol7_UEKR4                                                | 1.2 kB     00:00    

      ol7_latest                                               | 1.4 kB     00:00    

      (1/2): ol7_latest/x86_64/updateinfo                        | 1.9 MB   00:39    

      (2/2): ol7_latest/x86_64/primary                           |  34 MB   05:57    

       

       

      One of the configured repositories failed (Unknown),

      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=<repoid> ...

       

           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 <repoid>

              or

                  subscription-manager repos --disable=<repoid>

       

           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=<repoid>.skip_if_unavailable=true

       

      Parsing primary.xml error: Document is empty

       

      Please let me know how I can fix this issue.