What is going on with the arch mirrors?

Spinnekop · 2022-05-28 16:53:17

sudo reflector --fastest 5 --country 'United States' --sort rate --save /etc/pacman.d/mirrorlist
[2022-05-28 17:50:49] WARNING: failed to rate http(s) download (https://mirrors.rit.edu/archlinux/commu … mmunity.db): [SSL: DECRYPTION_FAILED_OR_BAD_RECORD_MAC] decryption failed or bad record mac (_ssl.c:2548)
[2022-05-28 17:50:54] WARNING: failed to rate rsync download (rsync://mirrors.rit.edu/archlinux/community/os/x86_64/community.db): Download timed out after 5 second(s).
[2022-05-28 17:51:00] WARNING: failed to rate http(s) download (http://mirror.umd.edu/archlinux/communi … mmunity.db): Download timed out after 5 second(s).
[2022-05-28 17:51:03] WARNING: failed to rate http(s) download (https://mirror.umd.edu/archlinux/commun … mmunity.db): [SSL: DECRYPTION_FAILED_OR_BAD_RECORD_MAC] decryption failed or bad record mac (_ssl.c:2548)
[2022-05-28 17:51:08] WARNING: failed to rate rsync download (rsync://mirror.umd.edu/archlinux/community/os/x86_64/community.db): Download timed out after 5 second(s).
[2022-05-28 17:51:20] WARNING: failed to rate rsync download (rsync://ftp.osuosl.org/archlinux/community/os/x86_64/community.db): Download timed out after 5 second(s).
[2022-05-28 17:51:28] WARNING: failed to rate http(s) download (http://mirrors.lug.mtu.edu/archlinux/co … mmunity.db): Download timed out after 5 second(s).
[2022-05-28 17:51:32] WARNING: failed to rate http(s) download (https://mirrors.lug.mtu.edu/archlinux/c … mmunity.db): [SSL: DECRYPTION_FAILED_OR_BAD_RECORD_MAC] decryption failed or bad record mac (_ssl.c:2548)
[2022-05-28 17:51:37] WARNING: failed to rate rsync download (rsync://mirrors.lug.mtu.edu/archlinux/community/os/x86_64/community.db): Download timed out after 5 second(s).

sudo pacman -Syu
[sudo] password for paul:
:: Synchronising package databases...
kde-unstable is up to date
testing is up to date
multilib-testing is up to date
community-testing is up to date
core is up to date
extra is up to date
community is up to date
multilib is up to date
:: Starting full system upgrade...
error: could not read db 'extra' (Damaged tar archive)
error: could not read db 'extra' (Damaged tar archive)
error: could not read db 'community' (Damaged tar archive)
error: could not read db 'community' (Damaged tar archive)

Last edited by Spinnekop (2022-05-28 16:57:16)

mpan · 2022-05-28 17:22:50

As far as I know: nothing.

The first set of messages are warnings for mirrors that could not be ranked. That does not affect valid mirrors returned by reflector.

The second set of errors indicates that you are receiving invalid data. That is usually caused by a broken mirror set in pacman configuration or, if you are not using TLS, the ISP is modifying traffic (for example by captive portals). Tell us what mirror are you using: the exact and complete Server line in your configuration. Try using curl to directly download the .db file from the mirror and use the file utility to determine its type. If it’s HTML, see its contents: it may be a hint indicating what’s happening.

Also note that you have passed the `--country` option to reflector. That will limit your choice of mirrors considerably, skipping many good candidates.

Last edited by mpan (2022-05-28 17:27:46)

Spinnekop · 2022-05-28 19:28:35

Thanks mpan

It seems, rather bizarrely, that this was due to me trying to update via my mobile hotspot. As soon as I tried on wifi it worked.... I will never understand pooters.

mpan · 2022-05-28 19:41:03

Marking the thread as solved will help others, assuming that’s solved.

If that was a situation with a mobile hotspot, I suspect a captive portal. Passing `-p https` to reflector will ensure all communication takes place on a secure channel, preventing that and other issues. What would be the reason to not use TLS in 2022?

progandy · 2022-05-28 19:56:35

mpan wrote:

preventing that and other issues. What would be the reason to not use TLS in 2022?

Only if TLS was not blocked as well, otherwise this issue would not be solved. The output does not make that clear.
Edit: Well, the damaged databases would not happen, but there would be no way to download a fresh copy either.

Last edited by progandy (2022-05-28 20:01:58)

mpan · 2022-05-28 23:02:51

For the captive portal case: yes. That would only prevent corrupted files from appearing and give a good hint that connectivity should be investigated. But if that’s content injection, TLS would block such attempts.

Arch Linux

#1 2022-05-28 16:53:17

What is going on with the arch mirrors?

#2 2022-05-28 17:22:50

Re: What is going on with the arch mirrors?

#3 2022-05-28 19:28:35

Re: What is going on with the arch mirrors?

#4 2022-05-28 19:41:03

Re: What is going on with the arch mirrors?

#5 2022-05-28 19:56:35

Re: What is going on with the arch mirrors?

#6 2022-05-28 23:02:51

Re: What is going on with the arch mirrors?

Board footer