Metadata Update from @arrfab: - Issue assigned to phsmoura - Issue tagged with: low-trouble, medium-gain, mirror-linux
Thanks !
Your mirror http://it2.mirror.vhosting-it.com/centos/ has been added to the mirrors DB
It will be listed as a public mirror (and on https://mirror-status.centos.org / https://www.centos.org/download/mirrors/ ) in the following minutes/hours. Your IP address[es] (86.105.14.235 2a0c:79c0:2:eb::4) has/have been added in the ACL and so you should be able to rsync from msync.centos.org in the next ~10min
Important : it only concerns CentOS Linux 7 and Stream 8. For Stream 9 and above, read (again) https://wiki.centos.org/HowTos/CreatePublicMirrors
Kind Regards
Metadata Update from @phsmoura: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Hi phsmoura,
[root@it2 ~]# rsync -aqzH --delay-updates --delete-after msync.centos.org::CentOS /data/centos/ rsync: failed to connect to msync.centos.org (147.75.93.107): Connection refused (111) rsync error: error in socket IO (code 10) at clientserver.c(127) [Receiver=3.1.3]
Are you sure the server is in whitelist?
Regards, L
Metadata Update from @samsteve169: - Issue status updated to: Open (was: Closed)
@samsteve169 yes, it is. You can also check it is listed as a public mirror here https://mirror-status.centos.org and here https://www.centos.org/download/mirrors/ Maybe you tried before mirror manager validate your mirror, could you try again and give us the feedback?
Metadata Update from @phsmoura: - Issue priority set to: Waiting on Reporter (was: Needs Review)
@samsteve169 : the fact that it says 'Connection refused' means it's something different than then IP in the ACL (rsync port is open). The only restrictions in place are GeoIP ipset restrictions. Are you sure that you rsync pull is coming from that specific IP ? No firewall in between doing some SNAT change for rsync traffic ? (we had that in the past)
@arrfab yes, I was sure at 100% that IPs are they. I don't know but now it works correctly.
Thanks for your support!
Metadata Update from @samsteve169: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.