mirror

mirror@lists.centos.org

4577 discussions

Re: [CentOS-mirror] Access to us-msync.centos.org
by Don Sizemore 07 Jun '16

07 Jun '16

Hello, Could we also reinstate jobbot1.ibiblio.org aka 152.19.134.30 aka 2610:28:3090:3000:0:bad:cafe:30 ? It populates distro.ibiblio.org and is getting the same error, though we're synchronising from a nearby mirror. Thank you! Donald

2 1

Access to eu-msync.centos.org revoked & all LeaseWeb mirrors removed from mirror list
by LeaseWeb - Mirror Administrators 05 Jun '16

05 Jun '16

Hi centos-mirror list, Since around May 30 our distribution mirror no longer appears to have access to eu-msync.centos.org::CentOS, we’re seeing the following message: @ERROR: Unknown module ‘CentOS' Could you please reinstate access to the msync service for us? The outgoing IP’s are 94.75.223.121 and 2001:1af8:4030:1:0:dead:beef:cafe This box is responsible for feeding our entire mirror network, consisting of the following: Mirror.nl.leaseweb.net Mirror.de.leaseweb.net Mirror.us.leaseweb.net (which is used by mirror.sfo12.us.leaseweb.net and mirror.dal10.us.leaseweb.net as its source for syncing) 2 private mirrors in Singapore and Hong Kong Also i noticed that all of our mirrors have been removed from the official mirror list, which might be related to why we don’t have access anymore :) Do we need to re-register? Kind regards, Hans Rakers LeaseWeb Global Services BV Amsterdam, The Netherlands

1 0

Unreachable IPv6 backbone mirror
by Sascha Spreitzer 02 Jun '16

02 Jun '16

Hi From my end (Zurich, CH) of the internet can not reach one of the IPv6 backbone mirrors. [..] [root@mirror ~]# /usr/bin/rsync -6avzH --delete msync.centos.org::CentOS /var/www/html/centos rsync: failed to connect to msync.centos.org (2001:1af8:4060:a006:223:7dff:feaa:426f): Connection timed out (110) rsync error: error in socket IO (code 10) at clientserver.c(122) [Receiver=3.0.9] [..] [..] [root@mirror ~]# mtr -nr 2001:1af8:4060:a006:223:7dff:feaa:426f Start: Thu Jun 2 08:20:11 2016 HOST: mirror Loss% Snt Last Avg Best Wrst StDev 1.|-- 2a02:168:7a0e:5::1 0.0% 10 0.2 0.2 0.1 0.2 0.0 2.|-- 2a02:168:2000:1d::1 0.0% 10 0.5 0.6 0.5 0.9 0.0 3.|-- 2001:1620:2::1cd 0.0% 10 0.5 1.7 0.5 12.0 3.5 4.|-- 2001:1620:2::1ad 0.0% 10 0.8 0.7 0.6 1.0 0.0 5.|-- 2001:1620:2::196 0.0% 10 0.7 1.8 0.7 8.0 2.2 6.|-- 2001:1620:2::159 0.0% 10 0.5 2.0 0.5 7.4 2.4 7.|-- 2001:1620:2::c5 0.0% 10 6.1 7.5 0.5 23.1 7.1 8.|-- 2001:1620:2::2b6 0.0% 10 6.0 6.0 5.8 7.6 0.5 9.|-- 2001:1620:2::dd 0.0% 10 16.4 16.5 16.4 17.0 0.0 10.|-- 2001:1620:1000::15e 0.0% 10 19.6 19.9 17.9 21.3 0.9 11.|-- 2a03:2280:38::23 0.0% 10 17.4 17.6 17.4 17.8 0.0 12.|-- 2001:1af8:4060:0:81:17:32 0.0% 10 102.3 45.6 17.2 214.8 65.1 13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 [..] PS.: If in the case that endpoint is firewalled, please mind that ICMPv6 is a vital part of the IPv6 protocol and shall not be dropped but rather be answered accordingly (rejected, prohibited, etc..) This is part of the IPv6 RFC. Kind regards Sascha

2 1

discussion about ipv6 availability for msync.centos.org
by Fabian Arrotin 31 May '16

31 May '16

Just a status update about ipv6 for msync.centos.org As of today, we now have 30 nodes (out of 69) having ipv6 connectivity on the nodes behind msync.centos.org Instead of just advertising the AAAA record for msync I'd like to implement it through a specific record (maybe like msync-v6.centos.org) The reason is that if you have ipv6 and that we don't have your ipv6 address in the whitelist, I'm afraid that rsync will try over ipv6 directly, and so would be blocked as long as we don't have the proper ACL in place for ipv6 mirrors So the idea would be to have something like msync-v6.centos.org::CentOS-v6, and ask you to provide us the ipv6 address for your mirror (we can already do that in advance if you advertise AAAA record on your side for your mirror) and so it would be an "opt-in" thing (at least as a start) Then, we can decide to merge the ACLs and also have AAAA record for msync , after enough people will have confirmed that everything works. Ideas, comments, suggestions ? -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab

13 24

CentOS 6.8 release and mirror status
by Fabian Arrotin 26 May '16

26 May '16

Hi Mirrors Admins, As you probably know, CentOS 6.8 is now built. So expect to see some traffic when it will be released - very soon - (when the whole tree/isos will land on your mirror, and when people will then start downloading/rsyncing from your mirror). Just to let you know also that expected size is ~31Gb. After some time we'll remove the 6.7 folder and will archive it to vault.centos.org, so you'll get back that space. If you have questions, feel free to discuss that on the centos-mirror list, or in #centos-mirror, on irc.freenode.net Kind Regards, -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab

2 1

Mirror closing.
by Marco Galicia 26 May '16

26 May '16

Mirros in jellyfish.lol is closig due to the lack of funding. Sorry! Please remove from the list, too much bandwidth. -- *Por favor, evite enviarme documentos adjuntos en formato Word Excel o PowerPoint.Como alternativa puede enviarme documentos en formato odt, odx u ods, además de documentos en formato pdfSi realmente es necesario enviarme un documento en formato Word, por favor utilize el formato .doc en lugar de .docx Vea http://www.gnu.org/philosophy/no-word-attachments.html <http://www.gnu.org/philosophy/no-word-attachments.html>http://es.libreoffice.org/ <http://es.libreoffice.org/>http://getgnulinux.org/es <http://getgnulinux.org/es>*

1 0

Fwd: IPv6 Update
by Todd Crane 25 May '16

25 May '16

Please see attached Thank you, Todd Crane Founder/CEO N5 Tech todd.crane(a)n5tech.com <mailto:todd.crane@n5tech.com> > Begin forwarded message: > > From: N5 Tech NOC <noc(a)n5tech.com> > Subject: IPv6 Update > Date: May 25, 2016 at 2:16:19 AM MST > To: centos-mirror(a)centos.org > > Please update our IPv6 record in the ACL for mirror.n5tech.com: > > 2607:880:ffff:1:baae:edff:fe78:9590 > > Thank you > > > -N5 Tech NOC

2 1

Mirror listing request for global CDN backed mirror.
by hydn 25 May '16

25 May '16

HTTP: http://mirrors.evowise.com/centos/ Sync schedule: Every 6 hrs Bandwidth: 10 Gbps connection (multiple tier 1 upstreams + local peerings). Location: (For US : NY & LA) Sponsor: Evowise Sponsor URL: https://www.evowise.com/ IP to authorize: 89.44.100.220 Email contact: hayden(a)evowise.com Mirroring AltArch : no We are a tech company with global presence of web servers and would love to contribute by becoming an official CentOS mirror. We've deployed mirrors.evowise.com within our own CDN. These are the specs that we are using: CPU : 2 X Intel Xeon E5-2630 v3 64 Gb Ram 22T usable space (raid5) This mirror is sync'd over our CDN: Bucharest, Romania London, UK Italy, Milan Spain, Madrid US, LA US, New York We would like to list: http://mirrors.evowise.com/centos/ ...mirrors.evowise.com is on an anycast network and it has <50 ms ping from most global locations using those backend CDN locations. Thanks, Hayden James

3 5

IPv6 whitelist
by Logan Best 24 May '16

24 May '16

getting away from the messy discussion thread… Please make sure 2604:9e00:e::200/125 is whitelisted on us-msync.centos.org We already had v6 on mirrors.centos.webair.com originally and it was added to the directory then. Logan Best | Senior Infrastructure Engineer @Webair.com <http://webair.com/> Webair Internet Development Inc. | 501 Franklin Ave | Garden City, NY 11530 Office 516.938.4100, ext. 223 | Fax 516.938.5100 logan.best(a)webair.com <mailto:logan.best@webair.com> ********************************************************************** This email and any files transmitted with it may contain privileged or confidential information. Use, disclosure, copying or distribution of this message by anyone other than the intended recipient is strictly prohibited. If you have received this email in error please notify the sender by reply email and destroy all copies of this message in your possession, custody or control. **********************************************************************

2 2

[infra] : availability of msync.centos.org over IPv6 (please read)
by Fabian Arrotin 24 May '16

24 May '16

Dear Mirrors Admins, Recently we worked with the various sponsors hosting nodes for our msync network, and we were able to have enough IPv6 connectivity to publicly announce the availability of msync.centos.oorg over IPv6. Actually we have ~50% ipv6 coverage in the msync network to open it up to you. What does that mean ? if you have native ipv6 connectivity, you'll be able to automatically sync from us over ipv6 instead of ipv4, using the same rsync url ( msync.centos.org::CentOS/ - see https://wiki.centos.org/HowTos/CreatePublicMirrors) We decided to make it transparent, so we just added AAAA record[s] in our GeoIP pdns backend for msync.centos.org. Worth knowing that we're still using the same rsync target as before, and so also doing IP check for incoming connections (see initial announce mail for this : https://lists.centos.org/pipermail/centos-mirror-announce/2014-June/000015.…) This so remains in place but we'll add ipv6 addresses in the same ACL (already working and confirmed by some testers on the centos-mirror list,or #centos-mirror) What do you have to do ? normally nothing as if you advertise AAAA record for your public mirror, we have added it in the ACL already (and instead of just adding it, we added the whole /48 subnet around it, in case you're using a different IPv6 address for the outgoing connection) What if it doesn't work anymore ? feel free to answer to that thread (on the centos-mirror list only, not on the moderated centos-mirror-announce list) or reach us in #centos-mirror on irc.freenode.net and we'll verify your IPv6 address/subnet block in the ACL. What if you have IPv6 but still want to enforce rsync over IPv4 ? you can just do that at the rsync level through the "-4" parameter (man rsync) Should you encounter an issue, or should you have questions, feel free to reach us directly. -- on behalf of the CentOS sysadmin/infra team, Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

mirror