Skip to main content

Solved : Cannot retrieve repository metadata (repomd.xml) for repository

I just install CentOS 6.4 and use yum install update but got

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

I have double check with nslookup , ping and general internet browsing and everything seems me fine but update didn't work. I also tried yum clean all etc. but what work for me is here;

Solution :  
  1. Open a terminal (become Super user by entering 'su' and then the password)
  2. Type cd /var/run/
  3. Than Type dir to look for the 'yum.pid' file.
  4. Type rm -f yum.pid and press Enter
  5. Again Type dir to Confirm that the 'yum.pid' file has been deleted.
  6. Now again try yum update
Hope this will resolve your issue, I have done this on CentOS 6.4 but I have a great hope that it will also work for fedora, RedHat as well. please show yourself in comments;

Comments

Popular posts from this blog

Setting up per connection Limit Bandwidth on MikroTik Router

Generally, I do not prefer to add any unwanted restriction on the network user until its required due to some Administration reason. I know, there are more ways to tackle this setting up per connection Limit Bandwidth on MikroTik Router question comes into one’s mind but I resolve my concern while using MikroTik PCQs feature in MikroTik Queue Type and then calling this Queue Type to Simple Queue. There are more options for setting up per connection Limit Bandwidth on MikroTik Router but please share your concern to add anything else in this article. Let’s start to add our configurations; I am using WinBox for this Article but you can use anything you are convenient to use. Let’s start Step by Step procedure for Setting up per connection Limit Bandwidth on MikroTik Router, any version.  Setup Queue Types After Successful Login, click on Queues menu. Navigate to Queue Types and Press Add + (Plus Sign) to add a new Queue Type. Type a Name like in my scenario,...

DsReplicaGetInfo failed with status 8453 0x2105 on Windows Server 2008

I have two Domain Controller in my envorinment, Primary Domain Controller is Windows Server 2003 based and Additional domain controller is Windows Server 2008 based. When I Installed New 2008 ADC and after some time, when I check with repadmin /showreps found the error.... DsReplicaGetInfo() failed with status 8453 (0x2105):Replication access was denied. I really worried about Solutions: [ DsReplicaGetInfo failed with status 8453 ]

Event ID 1202 Source SceCli on domain controller - Solved

I was getting rapidly Event ID 1202 Source SceCli on my domain controller. Security policies were propagated with warning. 0x4b8: An extended error has occurred. Advanced help for this problem is available on http://support.microsoft.com. Query for "troubleshooting 1202 events". – Event ID 1202 Source SceCli It was a newly build Windows Server 2012 Domain Controller. I have scenario like this; Before: Primary Domain Controller: Windows Server 2003 (32-bit) Secondary Domain Controller: Windows Server 2008 (32-bit) Now: Primary Domain Controller: Windows Server 2012 Secondary Domain Controller: Windows Server 2008 (32-bit) After successfully DC promotion and after a week, I start getting Event ID 1202 on newly build server. L I tried various solutions but nothing was great except the below one; Solution ( Caution ):  Start > Type CMD > Run As Administrator (Open it on Windows Server 2012: Domain Controller)  Type   dcgpofix /ignoresche...