Hi Team,
We have an existing CentOS mirror, but I'm not sure if you've moved to a new system or the like recently? I can't find any documentation on our side on any login details etc, so I've just created a new account, and I'll put all the info for the existing mirror below incase it's just easier for you to create it as a new record. It looks like our mirror stopped syncing around November 15th. We are getting the following error when running rsync:
rsync --address=27.50.85.3 -rltgoDvCvzH --delete us-msync.centos.org::CentOS /home/centos/www opening tcp connection to us-msync.centos.org port 873 sending daemon args: --server --sender -vvlHogDtrCze.iLsfxCIvu . CentOS/ (5 args) @ERROR: Unknown module 'CentOS' rsync error: error starting client-server protocol (code 5) at main.c(1817) [Receiver=3.2.3]
Thanks,
Damien
This template can be used to ask for a new mirror for CentOS Linux 7 and CentOS Stream 8. For CentOS Stream 9 mirror request, see the other template (for which you'll need to be registered in mirrormanager)
Also, I meant to ask - is there an officially-suggested way to monitor that the mirror is up to date that I can add to our xymon for this mirror?
Metadata Update from @zlopez: - Issue tagged with: mirror-linux
Metadata Update from @arrfab: - Issue assigned to phsmoura - Issue tagged with: low-trouble, medium-gain
Hi @serversau ,
I checked and your mirror wasn't there so your mirror http://centos.mirror.serversaustralia.com.au/ 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] (27.50.85.3 2400:d400:9898:2503::2) 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)
Log in to comment on this ticket.