aliBuild fails due to timeout in G4NDL.4.5.tar.gz downloading

I encounter a problem in Nagasaki while doing aliBuild. It fails while working downloading geant4 components. When I do:

aliBuild build O2 --defaults o2

It finishes with error. In the log I see like I attach below this message. If I do by hand:


there is no problem however it takes about 30 minutes (1800 sec)! Considering ALICE is world-wide project, simply, increasing timeout value (now 1500 sec) to some other value should solve the problem.

However, probably the most beautiful solution is to allow changing timeout value in command line option.

What do you think? Some quick temporary solution is desired too.


Nagasaki Institute of Applied Science, Nagasaki, JAPAN

Here is corresponding part of the LOG

β€” LOG END β€”
error: downloading β€˜’ failed
status_code: 28
status_string: "Timeout was reached"
β€” LOG BEGIN β€”
Connected to ( port 80 (#0)
GET /support/source/G4NDL.4.5.tar.gz HTTP/1.1
User-Agent: curl/7.58.0
Accept: /

HTTP/1.1 200 OK
Date: Mon, 14 May 2018 14:02:05 GMT
Server: Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips PHP/5.4.16
Last-Modified: Tue, 19 Aug 2014 10:26:16 GMT
ETag: "1922c9d6-500f8eae02200"
Accept-Ranges: bytes
Content-Length: 421710294
Content-Type: application/x-gzip

Operation timed out after 1500000 milliseconds with 354454193 out of
421710294 bytes received
Closing connection 0

I agree we should increase the timeout globally. Allowing to change it via the environment leads to inconsistencies.

I have opened a PR that provides a quick fix. Can you try whether it works for you?

1 Like

I checked with the branch origin/increase-g4 .
Then, in my environment, with increased timeout from 1500 to 2000, the genat4 build works well.

Although I don’t know if 2000 is enough for anywhere in the world, I think we can close this issue for the moment
and the change can be merged to master branch.