Found the problem ... First off, we'd have to touch each system which would take one person about two weeks probably (a lot of CentOS boxes).... Second - the actual problem - the server that hosts our mirror site had a client limit of 256 ... we were hitting the default limit which I have now adjusted...;) Thanks very much, Paul From: centos-mirror-bounces at centos.org [mailto:centos-mirror-bounces at centos.org] On Behalf Of Mathew S. McCarrell Sent: October 23, 2009 9:25 AM To: Mailing list for CentOS mirrors. Subject: Re: [CentOS-mirror] 5.4 updates question On Fri, Oct 23, 2009 at 8:08 AM, Paul Stewart <pstewart at nexicomgroup.net> wrote: Checked that as well...;) I'm guessing that we have not hit the last "scan" of who is updated and who is not.... perhaps waiting a bit will fix this. According to my rsync logs we finished getting the 5.4 tree less than 24 hours ago... If you have a local mirror, why not just configure you systems to sync from it instead of pulling the mirror list? Also, you can check the timestamp file in the /centos/ directory to see how far behind your mirror is from the master pool. Matt -- Mathew S. McCarrell Clarkson University '10 mccarrms at gmail.com mccarrms at clarkson.edu 1-518-314-9214 ---------------------------------------------------------------------------- "The information transmitted is intended only for the person or entity to which it is addressed and contains confidential and/or privileged material. If you received this in error, please contact the sender immediately and then destroy this transmission, including all attachments, without copying, distributing or disclosing same. Thank you." -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos-mirror/attachments/20091023/4d1c5af7/attachment-0006.html>