[SOLVED] Metadata does not match checksum

malak33 · 08-23-2012, 09:11 PM

So i am trying to connect to a repo in Centos.
here is the /etc/yum.repos.d/Cloudera-cdh4.repo file

Code:

[cloudera-local]
name=Cloudera's Distribution for Hadoop, Version 4
baseurl=http://archive.cloudera.com/cdh4/redhat/6/x86_64/cdh/4/
gpgkey = http://archive.cloudera.com/cdh4/redhat/6/x86_64/cdh/RPM=GPG-KEY-cloudera
gpgcheck =1
enabled =1
~

now when i run the following i get the error

Code:

[root@example /]# yum clean all
Loaded plugins: fastestmirror, refresh-packagekit
Cleaning repos: base cloudera-local extras updates
Cleaning up Everything
Cleaning up list of fastest mirrors
[root@example /]# yum update
Loaded plugins: fastestmirror, refresh-packagekit
Determining fastest mirrors
 * base: centos.aol.com
 * extras: centos.mirror.freedomvoice.com
 * updates: centos-distro.cavecreek.net
base                                                     | 3.7 kB     00:00     
base/primary_db                                          | 4.5 MB     00:02     
cloudera-local                                           |  951 B     00:00     
cloudera-local/primary                                   |  22 kB     00:00 ... 
http://archive.cloudera.com/cdh4/redhat/6/x86_64/cdh/4/repodata/primary.xml.gz: [Errno -1] Metadata file does not match checksum
Trying other mirror.
cloudera-local/primary                                   |  22 kB     00:00 ... 
http://archive.cloudera.com/cdh4/redhat/6/x86_64/cdh/4/repodata/primary.xml.gz: [Errno -1] Metadata file does not match checksum
Trying other mirror.
Error: failure: repodata/primary.xml.gz from cloudera-local: [Errno 256] No more mirrors to try.
[root@example /]#

I am at a loss and have no idea what i can do to try to solve this issue. i have went through this link and tried everything they said and it also didn't work http://www.linuxquestions.org/questi...-mirro-462093/

also if i disable this cloudera repo i can go out and use YUM

macemoneta · 08-23-2012, 10:04 PM

If 'yum clean all' doesn't resolve the issue, then the problem is on the repository side and there's nothing you can do other than to temporarily disable the repo as you've done. Once the admins for the repo resolve the issue, it will work. If you have a contact for the repository, you can report the issue if it persists for several days.

malak33 · 08-23-2012, 11:35 PM

Thanks for the info, i had no idea. I wish i could have the last 6 hours back trying a whole bunch of different things.