Mine has been syncronizing for 2 days now slowly, and using inconsistent ammounts of bandwidth. Low during the day, high at night.
Thanks!
Andrew Zwieg IT Network Administrator Phone: 920.319.4217 Fax: 920.390.2750 Mobile: 920.342.6084 andrew@zwiegnet.com www.zwiegnet.com
----- Reply message ----- From: "Jeff Fisher" jeff@lfchosting.com Date: Thu, Mar 8, 2012 1:50 pm Subject: [CentOS-mirror] Mirror bandwidth To: "Mailing list for CentOS mirrors." centos-mirror@centos.org
Hey,
Is anyone else seeing a large increase in bandwidth today compared to previous releases?
I barely remember a bump last time a new CentOS release came out and today I'm about 650 gigs over a good day for my mirror.
Jeff _______________________________________________ CentOS-mirror mailing list CentOS-mirror@centos.org http://lists.centos.org/mailman/listinfo/centos-mirror
On Thu, 8 Mar 2012, Andrew B. Zwieg wrote:
Mine has been syncronizing for 2 days now slowly, and using inconsistent ammounts of bandwidth. Low during the day, high at night.
Same thing here at ftp.iitm.ac.in; and, the issue appears to be an upstream mirror that is missing the 5.8 isos - you hit that, all your isos get wiped out and in the next round you download them again. I have not been able to identify the problematic upstream mirror. I am modifying my sync script so the sync log does a logrotate kind of stuff, so I can catch the deleter next time.
On 03/09/2012 12:49 AM, Prof. P. Sriram wrote:
On Thu, 8 Mar 2012, Andrew B. Zwieg wrote:
Mine has been syncronizing for 2 days now slowly, and using inconsistent ammounts of bandwidth. Low during the day, high at night.
Same thing here at ftp.iitm.ac.in; and, the issue appears to be an upstream mirror that is missing the 5.8 isos - you hit that, all your isos get wiped out and in the next round you download them again. I have not been able to identify the problematic upstream mirror. I am modifying my sync script so the sync log does a logrotate kind of stuff, so I can catch the deleter next time.
The msync targets should all be in a consistent state. If you do see something like that, please let us know what IP. There is a basic monitoring script keeping an eye on the current msync targets ( which can and do change ).