Kernel version | Linux rocketeer 6.1.21-v7+ #1642 SMP Mon Apr 3 17:20:52 BST 2023 armv7l GNU/Linux
Architecture | armhf
SBC model | RPI2
Power supply used | (EG: 5V 1A RAVpower)
SD card used | (EG: SanDisk ultra)
Additional Information (if applicable)
Software title | Docker, Vaultwarden (docker container), Argon2
Steps to reproduce
$ apt update
Expected behaviour
Should update package repository
Actual behaviour
Expected file size failes
Extra details
E: Could not get https://dietpi.com/apt/dists/bookworm/main/binary-armhf/Packages.xz File has unexpected size (2232 != 2292). Mirror sync in progress? [IP: 188.114.96.0 443]
Hashes of expected file:
- Filesize:2292 [weak]
- SHA256:df2870e384ee3eaa9249b1c1e9d401198e9ce9c0ed8aec5dba27086cb62fc799
Release file created at: Wed, 20 Nov 2024 01:36:13 +0000
I have no problem downloading the file with eg. wget, but when I do a get update, the file has an unexpected size.
Maybe itās af wrong SHA256 checksumā¦?
I updated my RPI1, RPI3 and RPI4 without any errors
Hey, @Joulinar . Iām still getting the same issue after 4h.
I know you mentioned it as a Cloudflare cache, but I see you getting the Packages.xz around 2.5k, Iām only getting 2.2k of the file. Iām able to get the package no problem using wget, so I donāt think itās a network problem.
Thanks for the help!
root@DietPi:/tmp/DietPi-Software# apt update
Hit:1 https://deb.debian.org/debian bookworm InRelease
Hit:2 https://deb.debian.org/debian bookworm-updates InRelease
Hit:3 https://deb.debian.org/debian-security bookworm-security InRelease
Get:4 https://dietpi.com/apt bookworm InRelease [3529 B]
Hit:5 https://deb.debian.org/debian bookworm-backports InRelease
Hit:6 https://dietpi.com/apt all InRelease
Hit:7 https://archive.raspberrypi.com/debian bookworm InRelease
Get:8 https://dietpi.com/apt bookworm/main arm64 Packages [2172 B]
Err:8 https://dietpi.com/apt bookworm/main arm64 Packages
File has unexpected size (2300 != 2172). Mirror sync in progress? [IP: 172.67.193.183 443]
Hashes of expected file:
- Filesize:2172 [weak]
- SHA256:aa1df998374cafc8b442f90522c050764bf915a07bc3bb1f49e8063f3fbdd81a
Release file created at: Sat, 12 Oct 2024 14:44:36 +0000
Get:9 https://dietpi.com/apt bookworm/rpi3 arm64 Packages [656 B]
Fetched 4185 B in 5s (922 B/s)
Reading package lists... Done
E: Failed to fetch https://dietpi.com/apt/dists/bookworm/main/binary-arm64/Packages.xz File has unexpected size (2300 != 2172). Mirror sync in progress? [IP: 172.67.193.183 443]
Hashes of expected file:
- Filesize:2172 [weak]
- SHA256:aa1df998374cafc8b442f90522c050764bf915a07bc3bb1f49e8063f3fbdd81a
Release file created at: Sat, 12 Oct 2024 14:44:36 +0000
E: Some index files failed to download. They have been ignored, or old ones used instead.
root@DietPi:/tmp/DietPi-Software# wget https://dietpi.com/apt/dists/bookworm/main/binary-arm64/Packages.xz
--2024-11-22 02:40:25-- https://dietpi.com/apt/dists/bookworm/main/binary-arm64/Packages.xz
Resolving dietpi.com (dietpi.com)... 172.67.193.183, 104.21.12.65, 2606:4700:3035::6815:c41, ...
Connecting to dietpi.com (dietpi.com)|172.67.193.183|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2300 (2.2K) [application/x-xz]
Saving to: āPackages.xz.1ā
Packages.xz.1 100%[=========================================================================================================================================================================>] 2.25K --.-KB/s in 0s
2024-11-22 02:40:25 (5.29 MB/s) - āPackages.xz.1ā saved [2300/2300]
I have the same issue when fresh installing the RPI 2/3/4/Zero 2 img onto a raspberry pi zero 2w. The first boot fails when it tries to run āapt-get -y -eany updateā, and says unexpected file size 2300 != 2236
We would need to check with Cloudflare why these happen to Packages.xz files. It looks like cache is not correctly cleared, even if we trigger this actively. Could be a challenge with some edge locations. In worst case we might need to disable caching for these files.
ok now I know why wget download has been working while it fails on apt
Problem is the InRelease file being outdated and containing the wrong old size for Packages.xz. Therefore apt is complaining.
Release file created at: Sat, 12 Oct 2024
Also you see the very old date of the Release file from October, while it should be from yesterday.
We disabled the cache for the InRelease files now. In parallel we will check back with Cloudflare community, which reasons can be for cache entries to remain in some edge servers, despite ordering their removal via Cloudflare API.
