[ci] [R-package] Miktex installation failing: "Timeout was reached"

[jameslamb]

Description

R Windows CI jobs on multiple PRs and master with the following error.

Setting up MiKTeX
miktexsetup_standalone: Timeout was reached
miktexsetup_standalone: Data: code="28", url="https://api2.miktex.org/hello"
Error: Process completed with exit code -1.

Reproducible example

Example recent build from #5396: https://github.com/microsoft/LightGBM/actions/runs/3528457186/jobs/5918579958

Environment info

Four CI jobs are failing regularly with this error:

• r-package (windows-latest, MINGW, R 3.6, cran)
• r-package (windows-latest, MINGW, R 4.2, cran)
• r-package (windows-latest, MINGW, R 3.6, cmake)
• r-package (windows-latest, MINGW, R 4.2, cmake)

Additional Comments

In the past, we've seen MikTeX issues like this with minimal error messages resolve themselves after 12-48 hours 🙃

• [ci] [R-package] windows-latest CI jobs are broken: "initexmf.exe" failing #5562
• MiKTeX setup error at CI in master #4005
• [R-package] [ci] miktex downloads failing #3454
• [R-package] [ci] R CI jobs failed with to download MiKTeX #3198

[jameslamb]

I tried that URL listed in the error message from two different machines, and found that it's returning 429s from both.

curl -I https://api2.miktex.org/hello

HTTP/1.1 429 Too Many Requests
Server: nginx/1.18.0 (Ubuntu)
Date: Wed, 23 Nov 2022 04:49:15 GMT
Connection: keep-alive

It looks like api2.miktex.org is completely down.

curl -I https://api2.miktex.org/

HTTP/1.1 404 Not Found
Server: nginx/1.18.0 (Ubuntu)
Date: Wed, 23 Nov 2022 04:52:23 GMT
Connection: keep-alive

[jameslamb]

I've opened MiKTeX/miktex#1228 asking about this. Otherwise, hopefully waiting a few more hours will resolve this 😕

[jameslamb]

Found some more related threads, but none of them have a resolution.

• CURLCode 56 - error receiving network data MiKTeX/miktex#793
• Cannot update MiKTeX: code 56 MiKTeX/miktex#628
• Command line installation fails MiKTeX/miktex#336

[github-actions]

This issue has been automatically locked since there has not been any recent activity since it was closed.
To start a new related discussion, open a new issue at https://github.com/microsoft/LightGBM/issues
including a reference to this.