Re: Problems with RHN repository in RHEL Desktop v.5 x86_86

Cliff Perry <[email protected]> Mon, 18 Oct 2010 17:15:25 -0500
Newsgroups gmane.linux.redhat.rhn.user
Message-ID <[email protected]>
Bruno Martins wrote:
> Yes, it really did solve the problem! Thanks for your help, mate.
> 
> On Mon, Oct 18, 2010 at 9:18 PM, inode0 <[email protected]> wrote:
>> On Mon, Oct 18, 2010 at 3:04 PM, Bruno Martins <[email protected]> wrote:
>>> Good night mates,
>>>
>>> I'm currently unable to update or install any packages from my system
>>> (RHEL Desktop v. 5 x86_64) because of this error:
>>>
>>> [user@machine ~]# yum check-update
>>> Loaded plugins: rhnplugin, security
>>> rhel-x86_64-client-5                                     | 1.4 kB     00:00
>>> rhel-x86_64-client-5/primary                             |   10 B     00:00
>>> rhel-x86_64-client-5/primary                             |   10 B     00:00
>>> rhel-x86_64-client-5/primary                             |   10 B     00:00
>>> rhel-x86_64-client-5/primary                             |   10 B     00:00
>>> Error: failed to retrieve
>>> repodata/4d9b8fc1779a8bd59019ff7a315439c417ffd402-primary.xml.gz from
>>> rhel-x86_64-client-5
>>> error was [Errno -1] Metadata file does not match checksum
>>>
>>> Have you guys ever faced this problem, and possibly know a solution?
>>>
>>> I've tried commands like...
>>>
>>> yum clean metadata
>>> yum clean all
>>> rm -rf /var/cache/yum/*
>>> rm -rf /var/spool/up2date/loginAuth.pkl
>>>
>>> ... but with no success, unfortunately.
>>>
>>> Thanks for your cooperation.
>> Try disabling location aware updates in RHN and see if that clears it up?
>>
>> John
>>
>> _______________________________________________
>> rhn-users mailing list
>> [email protected]
>> https://www.redhat.com/mailman/listinfo/rhn-users
>>
> 
> _______________________________________________
> rhn-users mailing list
> [email protected]
> https://www.redhat.com/mailman/listinfo/rhn-users


To Bruno and Charles,
if you can and willing, please do open support cases on these issues so 
that folks can escalate/report/track internally. It also helps for 
tracking/trending when folks impacted by something report these up vs 
hoping someone else did and/or it will be a self healing issue if you 
just wait :)

Regards,
Cliff