Yum Error: Cannot retrieve repository metadata (repomd.xml) for repository: dag. Please verify its path and try again

When updating CentOS or RedHat via yum its possible to receive an error similar to the below. This error will cause an issue where yum will not work even though as described below the issue is typically isolated to one yum repository.

Error:Cannot retrieve repository metadata (repomd.xml) for repository: dag. Please verify its path and try again

In the case above the issue was with the dag yum repository. There error is generic in the sense that the issue I was seeing if the fact that the server was up but that directory was either moved or was not mounted to their server properly. Yum is complaining that you need to check the path to make sure it is correct.

You have two options to resolve this yum repo issue as described below.

1. Temporarily Disable Repo:You can temporarily disable the yum repository that is causing you issues by simply changing “enabled=1” to “enabled=0” as shown in the below dag.repo file.
   Disabled Yum Repository:
   bash

   
   

   1. name=Dag RPM Repository for Red Hat Enterprise Linux
   2. baseurl=http://apt.sw.be/redhat/el$releasever/en/$basearch/dag
   3. gpgcheck=1
   4. gpgkey=http://dag.wieers.com/rpm/packages/RPM-GPG-KEY.dag.txt
   5. enabled=o
2. Use a Different Repo Mirror:The second option is to modify the baseurl variable in the .repo file with the issue. Repository files are located in /etc/yum.repos.d/. Below I commented out the problem baseurl and added a new one.
   Modify Repo BaseURL:
   bash

   
   

   1. name=Dag RPM Repository for Red Hat Enterprise Linux
   2. #baseurl=http://apt.sw.be/redhat/el$releasever/en/$basearch/dag
   3. baseurl=http://dag.linux.iastate.edu/dag/redhat/el5/en/$basearch/dag
   4. gpgcheck=1
   5. gpgkey=http://dag.wieers.com/rpm/packages/RPM-GPG-KEY.dag.txt
   6. enabled=1

Once you have either disabled or changed the baseurl variable yum should run without issue. If there is still an error with another yum repository you can resolve that issue as well though its fairly unlikely that two repositories would have errors at the same time so you should investigate issues on your server or with your network connection.