Brandon Davidson wrote: > Brandon Davidson wrote: >> Restarting the server is an immediate fix; but I should probably also >> be including at least Size in there... or maybe just unset it and let >> the default "INode MTime Size" work its magic. >> >> It's possible that the metadata files also have some influence on what >> content ranges are requested, but I'm not a Yum expert so I can't say >> for sure. > > It appears that I was too quick to assign blame. I am still seeing 416 > errors, and there are apparently other problems with the metadata. I > guess Yum requests a content range based on the size reported in the > primary metadata, which is now incorrect for a significant number of files. > I have rerun the metadata on the master mirror and it is going out to the other mirrors, this should clear up soon. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 251 bytes Desc: OpenPGP digital signature URL: <http://lists.centos.org/pipermail/centos-mirror/attachments/20080722/ba5e5fed/attachment-0004.sig>