Hello,
I would recommend switching your scripts to point to 
ftp.scientificlinux.org.  linux21 is currently going through an upgrade, 
(both hardware and software) and when it is stable, will be the new 
ftp.scientificlinux.org as it once was.
Yes, currently right now it has extrememly fast download times.  But it 
also might be down for a day or two, and things like what you are 
showing might show up.
Troy

Kyriakos G. Ginis wrote:
> Hello,
> 
> Lately I have noticed that the nightly yum cronjob on some of our servers
> (running SL303) fails with the message:
> 
> --------------------
> YUM - errata
> --------------------
> Damaged or Bad header.info from sl303 errata
> This is probably because of a downed server or an invalid header.info on a repository.
> 
> 
> 
> Investigating this a bit, I found out that the errors seem to come from
> ftp://linux21.fnal.gov, which happens to be one of the servers in the
> default /etc/yum.d/yum.cron.secondary file. For example, running yum by
> hand with a modified yum.conf pointing at linux21.fnal.gov, this is what
> I get:
> 
> [root@aurum 02:34:37 ~ ]# cat /etc/yum.conf
> [main]
> cachedir=/var/cache/yum
> debuglevel=2
> logfile=/var/log/yum.log
> pkgpolicy=newest
> tolerant=1
> exactarch=1
> 
> [sl303server]
> name=SL 303 main
> baseurl=ftp://linux21.fnal.gov/linux/scientific/303/$basearch/SL/RPMS/
> 
> [sl303errata]
> name=SL 303 errata 
> baseurl=ftp://linux21.fnal.gov/linux/scientific/303/$basearch/errata/SL/RPMS/
> [root@aurum 02:34:41 ~ ]# yum update
> Gathering header information file(s) from server(s)
> Server: SL 303 errata
> Damaged or Bad header.info from SL 303 errata
> This is probably because of a downed server or an invalid header.info on a repository.
> 
> 
> Has anybody else noticed this?
> 
> Cheers,
> 


-- 
__________________________________________________
Troy Dawson  [log in to unmask]  (630)840-6468
Fermilab  ComputingDivision/CSS  CSI Group
__________________________________________________