Admins,
Whenever my host hits 2001:49f0:d071:2::10 the rysnc connection times out, but all other IPv6 hosts have worked fine. Can you check on that host?
Thanks, Adam
/usr/bin/rsync -azqH [2001:49f0:d071:2::10]::CentOS/timestamp.txt /tmp/
rsync: failed to connect to 2001:49f0:d071:2::10 (2001:49f0:d071:2::10): Connection timed out (110) rsync error: error in socket IO (code 10) at clientserver.c(122) [Receiver=3.0.9]
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Why did you point to that static IPv6? Better use msync FQDN hostname than IP address, since msync have algorithm to select nearest mirror.
$ host msync.centos.org msync.centos.org has address 202.76.233.2 msync.centos.org has IPv6 address 2605:9000:401:102::2
On 03/27/2017 07:33 PM, Adam Ring wrote:
Admins,
Whenever my host hits 2001:49f0:d071:2::10 the rysnc connection times out, but all other IPv6 hosts have worked fine. Can you check on that host?
Thanks, Adam
/usr/bin/rsync -azqH [2001:49f0:d071:2::10]::CentOS/timestamp.txt /tmp/ rsync: failed to connect to 2001:49f0:d071:2::10 (2001:49f0:d071:2::10): Connection timed out (110) rsync error: error in socket IO (code 10) at clientserver.c(122) [Receiver=3.0.9]
_______________________________________________ CentOS-mirror mailing list CentOS-mirror@centos.org https://lists.centos.org/mailman/listinfo/centos-mirror
lol, I do use DNS, but for this exact reason I spit out which IP the server is hitting prior to trying to connect or else there is just a generic error message that it couldn't connect to "us-msync.centos.org" which isn't helpful to anyone.
Adam
On Mon, Mar 27, 2017 at 8:47 AM, Dewangga Bachrul Alam < dewanggaba@xtremenitro.org> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Why did you point to that static IPv6? Better use msync FQDN hostname than IP address, since msync have algorithm to select nearest mirror.
$ host msync.centos.org msync.centos.org has address 202.76.233.2 msync.centos.org has IPv6 address 2605:9000:401:102::2
On 03/27/2017 07:33 PM, Adam Ring wrote:
Admins,
Whenever my host hits 2001:49f0:d071:2::10 the rysnc connection times out, but all other IPv6 hosts have worked fine. Can you check on that host?
Thanks, Adam
/usr/bin/rsync -azqH [2001:49f0:d071:2::10]::CentOS/timestamp.txt /tmp/ rsync: failed to connect to 2001:49f0:d071:2::10 (2001:49f0:d071:2::10): Connection timed out (110) rsync error: error in socket IO (code 10) at clientserver.c(122) [Receiver=3.0.9]
_______________________________________________ CentOS-mirror mailing list CentOS-mirror@centos.org https://lists.centos.org/mailman/listinfo/centos-mirror
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2
iQI4BAEBCAAiBQJY2QnzGxxkZXdhbmdnYWJhQHh0cmVtZW5pdHJvLm9yZwAKCRDl f9IgoCjNcBuoD/9vWZDIPhJruV9+EvJVv8MfOOtB/VHtW86s+cqJkxc68Ya5hLTE 1+WhV8lgA+ew113/t6jV3bRuW1jajudFDR+VhN0nXLWeNsXbwm7tc1d69XAZ5jLo LFbMd5bgiuG8HGuG056AME8ZcsCcrwCU/5mKfksE9OBMXqzxNQ5f5ULNXJYQI4cm SMeY5ybjenDRDi1o/rPkYhF0+YJY5n26E8sjTP4tWa8l+9dYi5uiE63/GetpGdNl 5febla6tIr/aQqSK5LFkiGMSxadLwtaFyqbL430RaNBmsw/fUQ4GfRCIKiTflAnx Xx741K6IUNGFZ0AIwLN+CnCFEQAsa/xE4Iq9+70Bq9bp2qdpL7XH0psHtHDL3uP0 rh/Jog4ibecCS+/csKlVu/1MktFLPHovpqf7X0eYToLf0pwsMEXWFn2AlZn0VA5J YnZnYhqEnavSWj0F7tf1hS4waUwEogwyuVHZMnGpDVqBjrVZ5G4GyWOTitFk9fwf XUdo89+18k+x2yJjXqHhwa+E12p5Q4+zHI/dbISkwDvGtQHheZtHDyoJWI7evAZ0 rhY2LFE5NJGVMhU3PoD+AI7fNR8jQDy0Jb9uzWtRuoyj9Zt6rxOF3pkhy6zgyFTJ FGAwFxnMxhtOq78tXChWelxdhjsBF63Rf46sRDDGLKrpykqdCj7S4s2HwA== =ddbf -----END PGP SIGNATURE----- _______________________________________________ CentOS-mirror mailing list CentOS-mirror@centos.org https://lists.centos.org/mailman/listinfo/centos-mirror
On 27/03/17 14:33, Adam Ring wrote:
Admins,
Whenever my host hits 2001:49f0:d071:2::10 the rysnc connection times out, but all other IPv6 hosts have worked fine. Can you check on that host?
Thanks, Adam
/usr/bin/rsync -azqH [2001:49f0:d071:2::10]::CentOS/timestamp.txt /tmp/ rsync: failed to connect to 2001:49f0:d071:2::10 (2001:49f0:d071:2::10): Connection timed out (110) rsync error: error in socket IO (code 10) at clientserver.c(122) [Receiver=3.0.9]
Hi,
I confirm there is an issue for ipv6 on that node (while ipv4 works fine) so in touch with DC people to investigate the routing issue. In the meantime, that AAAA record has been removed from the mirror/msync pool
Cheers,
-
Adam Ring -
Dewangga Bachrul Alam -
Fabian Arrotin