Hello,
we at Consortium GARR already have a public mirror for CentOS and altarch but we are having trouble connecting to the rsync server as of 10/06/25.
We are connecting to msync.centos.org::CentOS from IPs 90.147.160.197 and 90.147.203.10 (for altarch as well), while the first ip one can sync without problems the second one returns the error: Unknown module 'CentOS'.
It worked before the 10th, did it got blacklisted?
Thanks
Metadata Update from @arrfab: - Issue assigned to arrfab
Metadata Update from @arrfab: - Issue tagged with: centos-7-8s-eol, mirror-linux, need-more-info
Can you elaborate please ? msync.centos.org doesn't carry any content anymore for one year as centos linux 7 reached EOL. (mirror.centos.org is an empty structure now)
The process to rsync Stream content is described on https://www.centos.org/download/mirrors/ So what are you trying to do ? you were mirroring empty content set ? We haven't changed the legacy IP ACL for legacy msync.centos.org but there is nothing to change as nothing to mirror from there anymore either.
Metadata Update from @arrfab: - Issue priority set to: Waiting on Reporter (was: Needs Review)
we where mirroring from eu-msync.centos.org that looks like it still has up to centos 8 but i guess we didn't get the memo that synching those is not needed anymore.
Anyway we are having the same problem while synching CentOS Stream from rsync.stream.centos.org::CentOS-Stream-All, it worked before the 10th of june from both of our IPs (90.147.160.197 and 90.147.203.10) but now the first one is able to sync and the second one is not with
ERROR: Unknown module 'CentOS-Stream-All'
Can you help us with that?
I looked at original ticket https://pagure.io/centos-infra/issue/1155 and all IP listed there are still listed for rsync.stream.centos.org ACL But you mention a new one that was never reported before, so I added it (but is there also another chance that you forget an ipv6 one for the corresponding ipv4 address 90.147.203.10 ? ) 90.147.203.10 is now added and it should be working for you in the next ~5min (please verify for ipv6 though)
Metadata Update from @arrfab: - Issue untagged with: mirror-linux, need-more-info - Issue tagged with: centos-stream, low-trouble, medium-gain, mirrormanager
Thank you, i was not aware of the previous ticket, same account different person :)
Yes, this ipv4 is new as we had some infrastructure changes a while ago
As for ipv6 we don't use it for synching, it was probably confusion from our part as those are the ipv6 our users can use to connect to our mirrors, also the ipv4 90.147.160.70, 90.147.160.72, 90.147.160.73 are the analogus v4 for our users so it should be safe for you to remove them.
So we should be ok with 90.147.160.196, 90.147.160.197 and 90.147.203.10 open. (can confirm 90.147.203.10 is working now) Thank you
Thanks for the feedback ... :) Closing as you confirmed it's now working
Metadata Update from @arrfab: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.