Hi
There is also rsync now available for mirror.spreitzer.ch
-----------------------------------------------------
HTTP: http://mirror.spreitzer.ch/centos
RSYNC: rsync://mirror.spreitzer.ch/centos
Sync schedule: Every 6 hrs
Bandwidth: 1 Gbit/s
Location: Zurich, Zurich, Switzerland
Sponsor: Sascha Spreitzer
Sponsor URL: http://spreitzer.ch
IP to authorize: 2a02:168:7a0e:5:5054:ff:fe77:b410
Email contact: sspreitz(a)redhat.com
Mirroring AltArch: no
-----------------------------------------------------
Kind regards
Sascha
HTTP: http://linux.nsu.ru/centos/
HTTP: http://mirror.nsu.ru/centos/
FTP: ftp://linux.nsu.ru/centos/
FTP: ftp://mirror.nsu.ru/centos/
Sync schedule: Every 8 hrs
Bandwidth: 1gb
Location: Russian Federation
Sponsor: Novosibirsk State University
Sponsor URL: http://nsu.ruhttp://mirror.nsu.ru
IPv4 address to authorize: 84.237.50.11
IPv6 address to authorize: no
Email contact: a.nazarov(a)nsu.ru
Best Regards,
Alex Nazarov
System engineer
Novosibirsk State University
С уважением,
Алексей Назаров
Системный администратор
Отдела Сетевых Информационных Технологий
Телефон: 52-26
e-mail: a.nazarov(a)nsu.ru
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.netMirror.de.leaseweb.netMirror.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
Hi CentOS Team,
We are receiving the below error while trying to sync from
eu-msync.centos.org:
@ERROR: Unknown module 'CentOS'
Our IP's are: 185.34.200.145 and 2a04:5ec0::20:18
Kindly ask you to whitelist our IPv6.
Thank you,
Andrei
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
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.netMirror.de.leaseweb.netMirror.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
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
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