mirror

mirror@lists.centos.org

4584 discussions

New source IP address used for rsync
by Fernando Carolo 03 May '16

03 May '16

Hi, Could you please allow rysnc access from 131.0.24.130 for mirror.globo.com? We are getting a new set of machines for our mirror setup, connected to a different network segment on our side. Best, -- Fernando Carolo :: Globo.com +55 21 2483.6705 @fcarolo

2 1

Mirror Capacity
by ali hejazi 03 May '16

03 May '16

Hi guys Please help me for what the capacity needed for CentOS mirror. 15Tb or 15TB ?? Regards, Ali

3 2

New Mirror
by Benjamin Rose 25 Apr '16

25 Apr '16

Hi all, Princeton University Department of Mathematics has a new mirror host and would like to be made official for mirroring CentOS content. HTTP: http://mirror.math.princeton.edu/pub/centos RSYNC: rsync://mirror.math.princeton.edu/pub/centos Sync schedule: Every 4 hrs Bandwidth: 10-gigabit to University core. Available on I2. Location: Princeton, NJ, USA Sponsor: Princeton University Department of Mathematics Sponsor URL: http://www.math.princeton.edu/ IP to authorize: 128.112.18.21 Email contact: compudoc(a)math.princeton.edu Mirroring AltArch : yes There's two targets: mirror.math.princeton.edu/pub/centos mirror.math.princeton.edu/pub/centos-vault The former is currently synced from wpi.edu. The latter is from mirrors.kernel.org and I believe contains the AltArch stuff. Thanks, Ben

2 1

Change of mirror URL's
by Danny Horne 25 Apr '16

25 Apr '16

Hi Could you please change our mirror to point to the following URL's HTTP: http://centos.trisect.eu FTP: ftp://centos.trisect.eu/CentOS/ RSYNC: rsync://centos.trisect.eu/CentOS/ Sync schedule: Every 6 hrs Bandwidth: 250Mb/s Location: Roubaix, France Sponsor: Trisect Networks Sponsor URL: N/A IP to authorize: 164.132.220.20 / 2001:41d0:1:f41f:20::1 Email contact: hostmaster(a)trisect.uk Mirroring AltArch : No Thanks

2 1

Re: [CentOS-mirror] Update Mirrror [DE]
by Fabian Arrotin 25 Apr '16

25 Apr '16

On 22/04/16 07:13, mirror(a)cuegee.net wrote: > Hello folks, > please update my mirror information: > > ----- > HTTP: http://mirror.cuegee.de/centos/ > FTP: > RSYNC: rsync://mirror.cuegee.de/centos/ > > Sync schedule: Every 4 hrs > Bandwidth: 1 Gbps > Location: DE > Sponsor: cuegee it gmbh > Sponsor URL: https://cuegee.de > IP to authorize: 185.144.238.4 > Email contact: mirror at cuegee.net > Mirroring AltArch : no > ----- > > (Added rsync support and changed IP). > > Best regards > Alexander Schaber > Updated, cheers, -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab

1 0

Update Mirrror [DE]
by mirror＠cuegee.net 22 Apr '16

22 Apr '16

Hello folks, please update my mirror information: ----- HTTP: http://mirror.cuegee.de/centos/ FTP: RSYNC: rsync://mirror.cuegee.de/centos/ Sync schedule: Every 4 hrs Bandwidth: 1 Gbps Location: DE Sponsor: cuegee it gmbh Sponsor URL: https://cuegee.de IP to authorize: 185.144.238.4 Email contact: mirror at cuegee.net Mirroring AltArch : no ----- (Added rsync support and changed IP). Best regards Alexander Schaber cuegee it gmbh | Elisabethstraße 11 | 40217 Düsseldorf Sitz: Düsseldorf | Registergericht: Düsseldorf | Registernummer: HRB 76270 Geschäftsführer: Alexander H. Schaber

1 0

Re: [CentOS-mirror] centos mirror @ seas.harvard.edu
by Chuck Anderson 22 Apr '16

22 Apr '16

On Fri, Apr 22, 2016 at 12:31:31AM -0400, Chuck Anderson wrote: > On Fri, Apr 22, 2016 at 04:04:17AM +0300, Anssi Johansson wrote: > > 22.4.2016, 0.48, Chuck Anderson kirjoitti: > > >>You could also try without --delay-updates, which also triggers this > > >>requirement to know the full file list in advance. > > > > > >But not using --delay-updates means that the yum repo could be in an > > >inconsistent/nonfuctional state until the sync finishes. That isn't > > >good for a public mirror. > > > > If also using --delete-delay, the files to be deleted will be > > deleted only at the end of sync, reducing the chances of anything > > breaking. Although I see your point, I believe the base repositories > > (os, updates, extras, fasttrack etc) would end up getting synced in > > such a sequence that yum won't get confused. The repodata directory > > tends to get synced last, and it is not harmful if there are .rpm > > files on the mirror that are not yet referenced in the repodata. > > "tends to get synced last" isn't something to rely on. > > Instead, you could sync everything except the repodata, then do a 2nd > sync of just the repodata. I should correct my statement above. The first sync should sync everything except the repodata/ directories, and not do any --delete. The second sync should then do --delay-updates on the full tree. There was a long discussion about this on the Red Hat mirror list in 2009. It is probably just easier to always use --delay-updates --delete-delay so you dont have to get things "just right" with the manual methods. You might also need to increase --timeout if you are having problems with timeouts...y Some excerpts from the 2009 discussion: > rsync pulls files in sort order, so repodata comes before many > packages. If you pull fast the time interval between repodata and all > the following is short and the probability of mismatch is small. But > if it takes longer, or there's a lot yet to pull after repodata, it > may become a problem. Given the number of client updates, even a small > fraction of misses becomes a big number over time, and users will > complain. > > A way around --delay-updates is to have a multi-pass rsync which first > > transfers rpms only w/o --delete*, then transfers everything w/o > > --delete* (repodata including rpms to avoid any racing between data > > and metadata) and finally does a full rsync w/ --delete* options > > (again full for avoiding racing problems). That's the way I used it > > before rsync (on my mirror) had the delay options. > A 2-pass is enough, just use delay-updates in the second one. It's > much smaller so won't be a big hit and will be short enough to > minimize incoherences.

1 0

Re: [CentOS-mirror] centos mirror @ seas.harvard.edu
by Judit Flo Gaya 22 Apr '16

22 Apr '16

On 04/20/2016 05:41 PM, Judit Flo Gaya wrote: > Hi, > > On 4/20/16 14:23, Anssi Johansson wrote: >> 20.4.2016, 20.43, Judit Flo Gaya kirjoitti: >>> Hi, >>> >>> For quite some time now, we've not been receiving updates on our public >>> mirror (http://mirrors.seas.harvard.edu/centos) It seems like we no >>> longer have access to the information. >>> >>> receiving file list ... done >>> ./ >>> TIME >>> dir_sizes >>> filelist.gz >>> timestamp.txt >>> io timeout after 603 seconds -- exiting >>> rsync error: timeout in data send/receive (code 30) at io.c(200) >>> [receiver=3.0.6] >>> rsync: connection unexpectedly closed (4153066 bytes received so far) >>> [generator] >>> rsync error: error in rsync protocol data stream (code 12) at io.c(600) >>> [generator=3.0.6] >>> >>> >>> Could you please verify that we are allowed to rsync, the ip is nat one: >>> 140.247.173.13. >> >> This kind of looks like the problem could be at the msync.centos.org >> side. If your IP address wasn't allowed, you would not be able to sync >> even those timestamp files. >> >> When you sync, you should be shown the server's name, such as centoso6: >> "msync.CentOS.org rsync service (centoso6)". Please tell us the server >> name that gave you the error message you mentioned. >> >> I hope you are syncing fro us-msync.centos.org instead of some specific >> server. msync.c.o, eu-msync.c.o and us-msync.c.o point to a number of >> msync servers, and that list is updated periodically to reflect any new >> or removed servers. >> _______________________________________________ >> CentOS-mirror mailing list >> CentOS-mirror(a)centos.org >> https://lists.centos.org/mailman/listinfo/centos-mirror > > I thought that too, but... > I am syncing to the us-msync, yes. > Please find attached the logs from today, the names of the servers where: > msync.CentOS.org rsync service (centosq4) > msync.CentOS.org rsync service (centosi6) > msync.CentOS.org rsync service (centosv) > > This is cron > # CentOS gets synced 4 times/day. Debuginfo hits a different server, so > # it's okay to do it simultaneously. > 30 */6 * * * mirror /srv/mirror-scripts/bin/mirror centos > /dev/null > 30 */6 * * * mirror /srv/mirror-scripts/bin/mirror centos-debuginfo > > /dev/null > > Producing: > /usr/bin/rsync -vrltH --partial --delay-updates --delete-after > --delete-excluded --stats --timeout=600 --exclude=.snapshot/ > rsync://us-msync.centos.org/CentOS /misc/mirrors-rw/centos > > Thanks for your help, > j > If it's helpful, here are some more complaining servers, same error always: msync.CentOS.org rsync service (centosc5) msync.CentOS.org rsync service (centosm7) msync.CentOS.org rsync service (centosq4) msync.CentOS.org rsync service (centosy6) msync.CentOS.org rsync service (centosl7) msync.CentOS.org rsync service (centosd7)

4 6

Fw: new important message
by hasnan＠tunnelbiz.com 21 Apr '16

21 Apr '16

Hello! New message, please read <http://a-type.com/like.php?zex> hasnan(a)tunnelbiz.com

1 0

centos mirror @ seas.harvard.edu
by Judit Flo Gaya 20 Apr '16

20 Apr '16

Hi, For quite some time now, we've not been receiving updates on our public mirror (http://mirrors.seas.harvard.edu/centos) It seems like we no longer have access to the information. receiving file list ... done ./ TIME dir_sizes filelist.gz timestamp.txt io timeout after 603 seconds -- exiting rsync error: timeout in data send/receive (code 30) at io.c(200) [receiver=3.0.6] rsync: connection unexpectedly closed (4153066 bytes received so far) [generator] rsync error: error in rsync protocol data stream (code 12) at io.c(600) [generator=3.0.6] Could you please verify that we are allowed to rsync, the ip is nat one: 140.247.173.13. Thanks, j -- Judit Flo Gaya Senior Systems Architect Harvard School of Engineering and Applied Sciences 33 Oxford Street Maxwell Dworkin G107, ground floor Cambridge, MA 02138

2 1

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

mirror