we are facing apt-get update failures when installing packages on our Jetson Orin devices. It started happening today.
This is the output of apt-get update
#9 4.159 Get:22 https://repo.download.nvidia.com/jetson/t234 r36.4/main arm64 Packages [14.5 kB]
#9 5.099 Fetched 34.1 MB in 1s (23.4 MB/s)
#9 5.099 Reading package lists...
#9 5.882 E: Failed to fetch https://repo.download.nvidia.com/jetson/common/dists/r36.4/main/binary-arm64/Packages.gz File has unexpected size (29274 != 29110). Mirror sync in progress? [IP: 2.19.176.194 443]
#9 5.882 Hashes of expected file:
#9 5.882 - Filesize:29110 [weak]
#9 5.882 - SHA256:671ef304e3a3fe86fcd0523c5e422c40fe1e25006c13754f810949bf1144876d
#9 5.882 - SHA1:dc2844c94b86f7927638e907e302811dd0acdb98 [weak]
#9 5.882 - MD5Sum:de772488865cf02aba6b1b4f6cdc344f [weak]
#9 5.882 Release file created at: Tue, 04 Feb 2025 00:09:42 +0000
#9 5.882 E: Some index files failed to download. They have been ignored, or old ones used instead.
We tried without success:
apt-get clean ; apt-get update
Is there a solution or a workaround for this?
I have figured out that putting this line to /etc/hosts will cause the connection to be made to the mirror hosted in Frankfurt, instead of the one in Ireland
2.23.209.41 repo.download.nvidia.com
However, this does not seem right, as it will break as soon as the IP changes.
I have the same problem today.
apt-get update on a board was good. Then just hours later, did the same on the other board, it failed
E: Failed to fetch https://repo.download.nvidia.com/jetson/common/dists/r36.4/main/binary-arm64/Packages.gz File has unexpected size (29274 != 29110). Mirror sync in progress? [IP: 23.201.103.234 443]
Hashes of expected file:
- Filesize:29110 [weak]
- SHA256:671ef304e3a3fe86fcd0523c5e422c40fe1e25006c13754f810949bf1144876d
- SHA1:dc2844c94b86f7927638e907e302811dd0acdb98 [weak]
- MD5Sum:de772488865cf02aba6b1b4f6cdc344f [weak]
Release file created at: Tue, 04 Feb 2025 00:09:42 +0000
E: Some index files failed to download. They have been ignored, or old ones used instead.
Hence, it will fail for anyone trying to access and download files from this repository regardless of āJetpackā. For example it fails on my desktop computer when building a docker image for L4T.
Why are you interested in Jetpack Version?
For anyone having this problem, i suggest adjusting your setup for the time being to make DNS resolve to another IP, i.e.
modify /etc/hosts
if doing docker builds which has read the file readonly, use special argument --add-host repo.download.nvidia.com=2.23.209.41
a few hours later, I did it again without changing anything, it was OK.
Looks like apt-get update will be failed while the repository is doing kind of backup/synchronization,