We are mirror.ratiokontakt.de and are experiencing the following problem:
$ /usr/bin/rsync -azqHP --stats --partial --progress --delete us-msync.centos.org::CentOS /var/www/vhosts/mirror.ratiokontakt.de/httpdocs/mirror/centos @ERROR: Unknown module 'CentOS' rsync error: error starting client-server protocol (code 5) at main.c(1516) [Receiver=3.0.9]
unknown module CentOS sounds weird. Has our mirror been blocked?
we are: 2: enp5s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000 link/ether 00:30:48:85:05:fe brd ff:ff:ff:ff:ff:ff inet 212.223.23.58/30 brd 212.223.23.59 scope global enp5s0 valid_lft forever preferred_lft forever inet6 2a02:708:0:35::2/64 scope global valid_lft forever preferred_lft forever
and just to make sure:
$ nmap eu-msync.centos.org
Starting Nmap 6.47 ( http://nmap.org ) at 2016-10-28 14:44 CEST Nmap scan report for eu-msync.centos.org (185.50.225.30) [...] 80/tcp open http 873/tcp open rsync
On 28/10/16 14:45, Florian Panzer - ratiokontakt GmbH wrote:
We are mirror.ratiokontakt.de and are experiencing the following problem:
$ /usr/bin/rsync -azqHP --stats --partial --progress --delete us-msync.centos.org::CentOS /var/www/vhosts/mirror.ratiokontakt.de/httpdocs/mirror/centos @ERROR: Unknown module 'CentOS' rsync error: error starting client-server protocol (code 5) at main.c(1516) [Receiver=3.0.9]
unknown module CentOS sounds weird. Has our mirror been blocked?
we are: 2: enp5s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000 link/ether 00:30:48:85:05:fe brd ff:ff:ff:ff:ff:ff inet 212.223.23.58/30 brd 212.223.23.59 scope global enp5s0 valid_lft forever preferred_lft forever inet6 2a02:708:0:35::2/64 scope global valid_lft forever preferred_lft forever
It's because you (recently ?) added ipv6 on your host but never reported that address to us, so rsync tries now ipv6 first and is refused. I've added your AAAA record in the ACL and it will work in the next ~30 minutes.
Cheers,
Am 28.10.2016 um 15:03 schrieb Fabian Arrotin:
It's because you (recently ?) added ipv6 on your host but never reported that address to us, so rsync tries now ipv6 first and is refused. I've added your AAAA record in the ACL and it will work in the next ~30 minutes.
You're right - thank you for noticing!
-
Fabian Arrotin -
Florian Panzer - ratiokontakt GmbH