- Status Closed
- Percent Complete
- Task Type Bug Report
- Category Packages
- Assigned To No-one
- Operating System pentium4
- Severity Low
- Priority Very Low
- Reported Version
- Due in Version Undecided
-
Due Date
Undecided
- Votes
- Private
Opened by Peter Tirsek - 06.01.2021
Last edited by Andreas Baumann - 08.01.2021
FS#120 - Princeton ArchLinux32 mirror has been out of date; question about upstream mirror target
The ArchLinux32 mirror at http[s]://mirror.math.princeton.edu/pub/archlinux32/ appears to have stopped syncing properly in October. I contacted web@math.princeton.edu on January 1 to alert them to the problem, and received the following response from a Princeton sysadmin:
Here is the configuration I am using:
archlinux32:
remotesrc: “rsync://mirror.archlinux32.org/archlinux32/”
localdest: “/var/www/html/pub/archlinux32”
extraopts: “–port=22873”
Looks like at some point this stopped working from upstream:
Raw standard error:
rsync: failed to connect to mirror.archlinux32.org (85.10.198.216): Connection refused (111)
rsync: failed to connect to mirror.archlinux32.org (2a01:4f8:a0:5264::2): Network is unreachable (101)
rsync error: error in socket IO (code 10) at clientserver.c(125) [Receiver=3.1.2]
Can you recommend a better upstream target I can use? And if there are additional constraints on checkin time or frequency.
I informed him that I am not an official member of the ArchLinux32 team, but suggested that using the regular rsync port of 873 might work as mirror.archlinux32.org appears to accept connections to that port from the Internet. As of the time of this writing, it appears that the mirror is now again up to date (although it has other issues returning HTTP error 403 for some of its files), but I promised to bring his additional questions to the official team.
So, to iterate, is this the appropriate target to mirror, or should they use some other parameters?
Thank you.