Continual hash mismatch errors on download

Getting Started
1

I have had a docker container that builds our tool chain including G4 for months working great, but after trying to rebuild it this week, I continually get the following error:

#16 99.45 -- [download 98% complete]
#16 100.2 -- [download 99% complete]
#16 100.2 -- [download 100% complete]
#16 101.4 CMake Error at /home/software/geant4.10.00.p02-build/Externals/G4NDL-4.4/src/G4NDL-stamp/download-G4NDL.cmake:9 (file):
#16 101.4   file DOWNLOAD HASH mismatch
#16 101.4 
#16 101.4     for file: [/home/software/geant4.10.00.p02-build/Externals/G4NDL-4.4/src/G4NDL.4.4.tar.gz]
#16 101.4       expected hash: [cd8cc1d96aeb9b9ed37189edda26f5ad]
#16 101.4         actual hash: [bc000aeac7f8c669b2f3f7a292dc8c76]
#16 101.4 
#16 101.4 
#16 101.4 
#16 101.4 make[2]: *** [Externals/G4NDL-4.4/src/G4NDL-stamp/G4NDL-download] Error 1
#16 101.4 make[1]: *** [CMakeFiles/G4NDL.dir/all] Error 2
#16 101.4 make: *** [all] Error 2

I saw in previous posts that this would happen if there was a timeout when the download wouldn’t complete, but as you can see this is not the case here and was wondering if something is wrong on the server side or if there is anything I can try to resolve this?

Thank you!

2

There was an update to the server(s) over the last week or so, and that could have affected this. I’ve checked now that the file as-is downloaded from the server matches the required hash:

$ curl -OL http://geant4.cern.ch/support/source/G4NDL.4.4.tar.gz

If you’re still seeing the error, are you able to check the content of the downloaded /home/software/geant4.10.00.p02-build/Externals/G4NDL-4.4/src/G4NDL.4.4.tar.gz file to see if it’s a partially downloaded tar.gz or something else? The only other things I can think of are that the timeout is right on the cusp of the download completing, or that the download isn’t redirected.

3

Thanks for the information! That definitely explains it (I also had issues even visiting the website).

I was able to rebuild successfully today, so the issue has been resolved. Cheers!