- Arch-mirrors - lists.archlinux.org

mirror.premi.st shutting down
by Minku Lee 16 Feb '24

16 Feb '24

Hello, I manage mirror.premi.st <http://mirror.premi.st/>, and I’m writing to inform that the mirror.premi.st <http://mirror.premi.st/> is shutting down in 30 days — please remove the mirror from the official list. The timeline can be extended as I monitor the traffic and minimize disruption for existing users. Thanks for all your efforts on managing Arch Linux distribution and mirroring infrastructure. Regards, Minku Lee

2 1

Notice: Hacking & Coffee mirror termination in 2024
by Tails Hon1nbo 16 Feb '24

16 Feb '24

It pains me to post these notices, but H&C is shutting it's DC operations later this year. We will file a ticket on the tracker once we have a firm timeline. All servers are maintained until we finalise the timeline, so action is not currently required. We have had the pleasure of giving back to the community for so many projects over the years, and this one has always been closest to me as a heavy arch user and knowing how well these mirrors performed to people I have interacted with both locally and at travel events Quite a few people I've met even hard coded this mirror. Even though it's a terrible idea to hard coded a mirror, I can't help but admit it fed my ego a little bit. I wish the community the best, and am happy to see how healthy the mirror list is. I hope the new changes in the process create an even better experience for operators and users on top of an already exceptional platform that is the Arch mirror system. Cheers, ~Hon1nbo, proprietor Hacking & Coffee, LLC -- This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.

2 1

Are there any SLA requirements?
by Gentry Deng 14 Feb '24

14 Feb '24

Hello, I noticed that the mirrors provided by some Chinese mainland universities stopped working, and I learnt from other sources that it was due to school holidays and hence the schools shut down the power supply. So I was wondering if archlinux has any SLA requirements for mirror? Best regards, Gentry

1 1

"Could not parse time from lastsync" - asking for help
by Jeremy Kescher 02 Feb '24

02 Feb '24

I run the mirrors at https://archlinux.org/mirrors/kescher.at/ and unfortunately, I keep seeing a rather rare "Could not parse time from lastsync" on the Arch mirror status site, curiously on both rsync and https. This prevents completion from reaching 100%, which is rather annoying to me, and presumably some folks that depend on the mirror's existence. I have my own monitoring set up to check lastsync, and I have no recorded failure. Same goes for error logs I have set up specifically to debug this. Does anyone here have experience in debugging this? I have no idea what could be causing this anymore.

4 5

New Arch Linux RFC - Proposal for new mirror administration routines and mirror requirements
by pitastrudl 24 Jan '24

24 Jan '24

Hi all, This is a new RFC ( Request for comment ) that was put together by the Arch Linux mirror team and is now open for discussion. The proposal better defines what a mirror within Arch Linux is, how it is operated, better, clearer guidelines for becoming a mirror and decommissioning. To view and participate in the discussion, you can check it out here: https://gitlab.archlinux.org/archlinux/rfcs/-/merge_requests/29/ . For more information about what is an RFC and how it operates you can view the README.rst in the root of the repo: https://gitlab.archlinux.org/archlinux/rfcs. Best regards, Arun Arch Linux mirror team

3 2

shutdown of arch.mirror.zachlge.org
by Georg Zachl 09 Jan '24

09 Jan '24

Hi everyone, arch.mirror.zachlge.org will be shut down in the next days. Best regards, Georg

2 1

mirrors.xtom.de issue
by Amin Vakil 17 Sep '23

17 Sep '23

Hi, I'm just a normal user using mirrors.xtom.de, in the past few days there have been some problems with this mirror. It just timed out or returned 503 for a few days, and now it's been almost 12 hours which it has been out of sync. As it's a tier 1 mirror, I'm sending this email to see if administrator of the mirror replies if there's a issue and do they have a guess when it will be fixed, or if someone from archlinux staff knows about this. I can understand you may find this too much to report for a single mirror and why I haven't just switched to another one, but Internet is very bad in my country and this mirror is the only one which is accessible all the time, has good speed and it has been reliable on all ISPs in the past few years. Best Regards, Amin Vakil

3 2

tier 1 23m.com seems out of date
by ave 17 Sep '23

17 Sep '23

Hello, The tier 1 mirror that we pull from, 23m.com, seems to be having issues (connection issues, low completion): https://archlinux.org/mirrors/23m.com/ Can the operator please fix it? Thanks. Best, ave

2 1

pacman cannot handle HTTP 304 returned by nginx?
by Jing Luo 06 Sep '23

06 Sep '23

Hi all, I don't know if this is an intended behavior for pacman. Today I ran `pacman -Syyu` against the mirror hosted by me, and pacman output 404 for all the packages: ``` Total Download Size: 395.48 MiB Total Installed Size: 2273.64 MiB Net Upgrade Size: 133.43 MiB :: Proceed with installation? [Y/n] :: Retrieving packages... noto-fonts-cjk-20230817-1-any is up to date linux-6.4.12.arch1-1-x86_64 is up to date ktuberling-23.08.0-1-x86_64 is up to date marble-common-23.08.0-1-x86_64 is up to date klettres-23.08.0-1-x86_64 is up to date linux-headers-6.4.12.arch1-1-x86_64 is up to date minuet-23.08.0-1-x86_64 is up to date kalzium-23.08.0-1-x86_64 is up to date linux-docs-6.4.12.arch1-1-x86_64 is up to date archlinux-appstream-data-20230827-2-any is up to date Total ( 10/217) 395.5 MiB 22.7 GiB/s 00:00 [#######################################################################################] 100% error: failed retrieving file 'noto-fonts-cjk-20230817-1-any.pkg.tar.zst.sig' from repo.jing.rocks : The requested URL returned error: 404 error: failed retrieving file 'linux-6.4.12.arch1-1-x86_64.pkg.tar.zst.sig' from repo.jing.rocks : The requested URL returned error: 404 error: failed retrieving file 'archlinux-appstream-data-20230827-2-any.pkg.tar.zst.sig' from repo.jing.rocks : The requested URL returned error: 404 warning: too many errors from repo.jing.rocks, skipping for the remainder of this transaction error: failed retrieving file 'ktuberling-23.08.0-1-x86_64.pkg.tar.zst.sig' from repo.jing.rocks : The requested URL returned error: 404 error: failed retrieving file 'linux-headers-6.4.12.arch1-1-x86_64.pkg.tar.zst.sig' from repo.jing.rocks : The requested URL returned error: 404 error: failed retrieving file 'marble-common-23.08.0-1-x86_64.pkg.tar.zst.sig' from repo.jing.rocks : The requested URL returned error: 404 error: failed retrieving file 'kalzium-23.08.0-1-x86_64.pkg.tar.zst.sig' from repo.jing.rocks : The requested URL returned error: 404 error: failed retrieving file 'klettres-23.08.0-1-x86_64.pkg.tar.zst.sig' from repo.jing.rocks : The requested URL returned error: 404 error: failed retrieving file 'minuet-23.08.0-1-x86_64.pkg.tar.zst.sig' from repo.jing.rocks : The requested URL returned error: 404 error: failed retrieving file 'linux-docs-6.4.12.arch1-1-x86_64.pkg.tar.zst.sig' from repo.jing.rocks : The requested URL returned error: 404 warning: failed to retrieve some files error: failed to commit transaction (failed to retrieve some files) Errors occurred, no packages were upgraded. ``` I thought my mirror was out of date at first, so I ran the syncrepo script manually, but it looks like only the file lists were transferred. I searched on the arch forum, but in their cases, they have out-of-date package index or they change the mirrorlist to solve this problem. Not exactly my case. So I looked at the nginx access.log: ``` - - - [29/Aug/2023:08:06:42 +0900] "GET /archlinux/core/os/x86_64/core.db HTTP/2.0" 304 0 "-" "pacman/6.0.2 (Linux x86_64) libalpm/13.0.2" - - - [29/Aug/2023:08:06:42 +0900] "GET /archlinux/multilib/os/x86_64/multilib.db HTTP/2.0" 304 0 "-" "pacman/6.0.2 (Linux x86_64) libalpm/13.0.2" - - - [29/Aug/2023:08:06:42 +0900] "GET /archlinux/extra/os/x86_64/extra.db HTTP/2.0" 304 0 "-" "pacman/6.0.2 (Linux x86_64) libalpm/13.0.2" - - - [29/Aug/2023:08:06:43 +0900] "GET /archlinux/extra/os/x86_64/noto-fonts-cjk-20230817-1-any.pkg.tar.zst HTTP/2.0" 304 0 "-" "pacman/6.0.2 (Linux x86_64) libalpm/13.0.2" - - - [29/Aug/2023:08:06:43 +0900] "GET /archlinux/core/os/x86_64/linux-6.4.12.arch1-1-x86_64.pkg.tar.zst HTTP/2.0" 304 0 "-" "pacman/6.0.2 (Linux x86_64) libalpm/13.0.2" - - - [29/Aug/2023:08:06:43 +0900] "GET /archlinux/extra/os/x86_64/ktuberling-23.08.0-1-x86_64.pkg.tar.zst HTTP/2.0" 304 0 "-" "pacman/6.0.2 (Linux x86_64) libalpm/13.0.2" - - - [29/Aug/2023:08:06:43 +0900] "GET /archlinux/extra/os/x86_64/marble-common-23.08.0-1-x86_64.pkg.tar.zst HTTP/2.0" 304 0 "-" "pacman/6.0.2 (Linux x86_64) libalpm/13.0.2" - - - [29/Aug/2023:08:06:43 +0900] "GET /archlinux/extra/os/x86_64/klettres-23.08.0-1-x86_64.pkg.tar.zst HTTP/2.0" 304 0 "-" "pacman/6.0.2 (Linux x86_64) libalpm/13.0.2" - - - [29/Aug/2023:08:06:43 +0900] "GET /archlinux/core/os/x86_64/linux-headers-6.4.12.arch1-1-x86_64.pkg.tar.zst HTTP/2.0" 304 0 "-" "pacman/6.0.2 (Linux x86_64) libalpm/13.0.2" - - - [29/Aug/2023:08:06:43 +0900] "GET /archlinux/extra/os/x86_64/minuet-23.08.0-1-x86_64.pkg.tar.zst HTTP/2.0" 304 0 "-" "pacman/6.0.2 (Linux x86_64) libalpm/13.0.2" - - - [29/Aug/2023:08:06:43 +0900] "GET /archlinux/extra/os/x86_64/kalzium-23.08.0-1-x86_64.pkg.tar.zst HTTP/2.0" 304 0 "-" "pacman/6.0.2 (Linux x86_64) libalpm/13.0.2" - - - [29/Aug/2023:08:06:43 +0900] "GET /archlinux/core/os/x86_64/linux-docs-6.4.12.arch1-1-x86_64.pkg.tar.zst HTTP/2.0" 304 0 "-" "pacman/6.0.2 (Linux x86_64) libalpm/13.0.2" - - - [29/Aug/2023:08:06:43 +0900] "GET /archlinux/extra/os/x86_64/archlinux-appstream-data-20230827-2-any.pkg.tar.zst HTTP/2.0" 304 0 "-" "pacman/6.0.2 (Linux x86_64) libalpm/13.0.2" ``` After a little bit of research, I found that nginx seems to conform to the standard according to my setup: gzip off, telling the browser (in this case, pacman) to use the client side local cache, returning a 304. Note that my mirror site is set up like this: a load-balancer/reverse proxy (repo.jing.rocks) in front of two web servers (repo1 and repo2) connected to the same NFS storage backend. Caching to disk is not enabled in nginx. After that I decided to put these three lines into my location block so that nginx always returns 200: ``` add_header Cache-Control "no-cache"; etag off; if_modified_since off; ``` It looks all good now, except I can't reproduce this pacman bug (?) anymore. Now that arch's gitlab closed new account registration, I thought I should probably look for experienced mirror operators' input before submitting a bug report. What do y'all think? Is this a bug? (Also my mirror hasn't been accepted after 2 months https://bugs.archlinux.org/task/78991 looks like the mirror admin team is taking their sweet sweet time?) BR, -- Jing Luo About me: https://jing.rocks/about/ PGP Fingerprint: 4E09 8D19 00AA 3F72 1899 2614 09B3 316E 13A1 1EFC

4 3

Docker Image for Mirrors
by port19 28 Aug '23

28 Aug '23

Hi all, in my limited research into hosting a public mirror, I have not found a way to do so via a preexisting docker image. Wiki page in question: https://wiki.archlinux.org/title/DeveloperWiki:NewMirrors A publicly available and officially endorsed docker image has several advantages in easing administration, especially in regard to first setup. To be more percise: - Specified rsync options can be preconfigured - Random sync delay can be preconfigured - A default sync interval (I propose 6 hours) can be preconfigured, with optional override - Included synced repositories can be configured via a config file - Persistent storage should be done via a docker volume. The scope of the container would include a small entrypoint script to provide the mentioned configurability. If I get positive feedback on the matter I can start development immediately. Kind Regards, port19

2 1