Community
cancel
Showing results for 
Search instead for 
Did you mean: 
bor__ilya
Beginner
141 Views

Problem with apt repo (Hash Sum mismatch)

Ubuntu 16.04 (containerized env)

cd /tmp && wget https://apt.repos.intel.com/intel-gpg-keys/GPG-PUB-KEY-INTEL-SW-PRODUCTS-2019.PUB
apt-key add GPG-PUB-KEY-INTEL-SW-PRODUCTS-2019.PUB
wget https://apt.repos.intel.com/setup/intelproducts.list -O /etc/apt/sources.list.d/intelproducts.list
sh -c 'echo deb https://apt.repos.intel.com/mkl all main > /etc/apt/sources.list.d/intel-mkl.list'
apt-get update && DEBIAN_FRONTEND=noninteractive $APT_INSTALL intel-mkl-64bit-2018.4-057

Unexpected error output:

Hit:8 http://archive.ubuntu.com/ubuntu xenial-updates InRelease
Get:9 https://apt.repos.intel.com/mkl all/main amd64 Packages [83.8 kB]
Err:9 https://apt.repos.intel.com/mkl all/main amd64 Packages
  Hash Sum mismatch
Get:10 https://apt.repos.intel.com/mkl all/main all Packages [23.2 kB]
Err:10 https://apt.repos.intel.com/mkl all/main all Packages

Hit:11 http://archive.ubuntu.com/ubuntu xenial-backports InRelease
Fetched 102 kB in 1s (97.7 kB/s)
Reading package lists...
E: Failed to fetch https://apt.repos.intel.com/mkl/dists/all/main/binary-amd64/Packages.gz  Hash Sum mismatch
E: Failed to fetch https://apt.repos.intel.com/mkl/dists/all/main/binary-all/Packages.gz
E: Some index files failed to download. They have been ignored, or old ones used instead.
Removing intermediate container bfa65af9736b
The command '/bin/sh -c apt-get update &&     apt-get install -y wget &&     cd /tmp && wget https://apt.repos.intel.com/intel-gpg-keys/GPG-PUB-KEY-INTEL-SW-PRODUCTS-2019.PUB &&     apt-key add GPG-PUB-KEY-INTEL-SW-PRODUCTS-2019.PUB &&     echo deb https://apt.repos.intel.com/mkl all main > /etc/apt/sources.list.d/intel-mkl.list &&     apt-get update && DEBIAN_FRONTEND=noninteractive $APT_INSTALL intel-mkl-64bit-2018.4-057' returned a non-zero code: 100

Problem may be related to 2018 topic (#779730) i've found googling fingerprint

0 Kudos
2 Replies
Alice_H_Intel
Employee
141 Views

Hello,

Thanks for your question. from the engineer's advise. 

  1. You may try again. The issue might have gone already. And if it’s possible, try to find out the exact date and time when the issue happened.
  2. If the issue is still reproducing on the your side, pls check if you use any proxy servers for internet access. Also it would be great to download the following files manually and send us MD5 or SHA256 the checksums:
    1. https://apt.repos.intel.com/mkl/dists/all/InRelease
    2. https://apt.repos.intel.com/mkl/dists/all/Release
    3. https://apt.repos.intel.com/mkl/dists/all/Release.gpg
    4. https://apt.repos.intel.com/mkl/dists/all/main/binary-all/Packages
    5. https://apt.repos.intel.com/mkl/dists/all/main/binary-all/Packages.bz2
    6. https://apt.repos.intel.com/mkl/dists/all/main/binary-all/Packages.gz
    7. https://apt.repos.intel.com/mkl/dists/all/main/binary-amd64/Packages
    8. https://apt.repos.intel.com/mkl/dists/all/main/binary-amd64/Packages.bz2
    9. https://apt.repos.intel.com/mkl/dists/all/main/binary-amd64/Packages.gz
    10. https://apt.repos.intel.com/mkl/dists/all/main/binary-i386/Packages
    11. https://apt.repos.intel.com/mkl/dists/all/main/binary-i386/Packages.bz2
    12. https://apt.repos.intel.com/mkl/dists/all/main/binary-i386/Packages.gz

Beside this, the engineer team still do more testing on this issue to see if they can reproduce from their side. 

Thanks,

Alice

bor__ilya
Beginner
141 Views

Thank you, the problem have gone away.

And i finally see some Facebook container build pipelines (for open source projects) got finally healthy about 2-3 days ago. They are using MKL widely so i had to work using patched downstream with pre-downloaded MKL binaries several weeks. I don't know how much users were affected, but don't think there were a lot, its experimental stuff.

This is (not only) example: https://hub.docker.com/r/wav2letter/wav2letter/tags, they had a delay in image update related to commits history about a month but recently released new one.

Thank you for resolving issue again.

Reply