Node: Some https://nodejs.org/dist/ builds are experiencing intermittent 500 errors
- Version: Many (see list)
- Platform: All
- Subsystem: Dist build system
See:
https://github.com/nodejs/nodejs.org/issues/3075
https://github.com/nodejs/build/issues/2263
For other node repos effected by this.
What steps will reproduce the bug?
Many /dist/ builds are giving 500 errors. Such as https://nodejs.org/dist/v0.11.15/
How often does it reproduce? Is there a required condition?
Temperamental as it currently stands. Currently 500-ing for me
What is the expected behavior?
Dist zip download
What do you see instead?
500 errors
Additional information
A number of other issues have been raised about this:
https://github.com/nodejs/node/issues/32680
https://github.com/nodejs/node/issues/32681
https://github.com/nodejs/node/issues/32682
We will probably want to flatten them into one global issue surrounding builds across all of these versions failing to properly load.
Currently building a list of effected URLS
Thus far failing builds can be found here <- Likley to change given 500 errors seem almost random at this stage
ryanolee
All 45 comments
Facing this issue as well
aabuhijleh
on 6 Apr 2020
Seems that it affects all or most builds. If you try downloading the same file multiple times then it's hit or miss, I get approximately 70% internal server error and remaining 30% it downloas dsuccesfully, probably there are some unhealthy instances in nodejs.org load balancer.
vitali-raikov
on 6 Apr 2020
This is not only happening for builds but the entire https://nodejs.org site in general is giving random 500 errors
See also:
https://github.com/nodejs/nodejs.org/issues/3075
https://github.com/nodejs/nodejs.org/issues/3076
WesleyKlop
on 6 Apr 2020
Only the v12.16.1 version is working at the moment. Seems to be an issue on Node site. I've just used the 12.16.1 version for now but its not going to be a solution for everyone.
devu4
on 6 Apr 2020
Facing same issue. Is there any workaround?
pjammula
on 6 Apr 2020
Facing same issue. Is there any workaround?
You can try to use Docker images 👍
Raul6469
on 6 Apr 2020
Same issue ..
Rayanox
on 6 Apr 2020
Same issue. https://nodejs.org/dist/v9.11.1/node-v9.11.1-linux-x64.tar.gz file is missing
mmodi
on 6 Apr 2020
Only the v12.16.1 version is working at the moment. Seems to be an issue on Node site. I've just used the 12.16.1 version for now but its not going to be a solution for everyone.
I only managed to have the xz version working, gz did not work for 12.16.1.
dalawwa
on 6 Apr 2020
We are experiencing the problems for a few hours from now?
Do you have any update on these Issues?
current stable "node-v12.16.1-linux-x64.tar.gz" is not working. ;.(
steelion
on 6 Apr 2020
Same issue... it is intermittent.
ashvin777
on 6 Apr 2020
This is blocking our deploy pipeline, how can we help here? It seems rather weird that a project as big as Node has issues reported as far back as 8 hours and there's nothing done about it..
19h
on 6 Apr 2020
Is there an update on this issue? This is blocking our build pipelines and we are closing in on a release deadline.
dominicjeremiah2020
on 6 Apr 2020
Use apt/yum to install the package for your respective distro.
aviatrix
on 6 Apr 2020
@nodejs/build-infra
AshCripps
on 6 Apr 2020
Same Issue. Blocking our release + deployment pipeline totally. Yikes
JamesBlandford
on 6 Apr 2020
You, guys, should store copies of all third-party packages in local repository to prevent such failures
MaxGsomGsom
on 6 Apr 2020
You, guys, should store copies of all third-party packages in local repository to prevent such failures
At a big corp i used to work we did that, it saved our asses few times npm has had issues. it's a good idea if you have the resources :)
edit: not in a repository per se, but a caching layer that acts as the proxy between you and npm.
This also makes downloading packages faster
aviatrix
on 6 Apr 2020
~It worked for me just now, maybe already fixed ?~
mosaadm
on 6 Apr 2020
You, guys, should store copies of all third-party packages in local repository to prevent such failures
@MaxGsomGsom Some prebuilt systems simply aren’t designed for that. In an ideal world that would be the case. But the practicality of it in many cases is unreasonable or untenable.
fishcharlie
on 6 Apr 2020
Still taking me a minute and a half or more to download a 13 Mb file which I think still shows signs of an issue.
To test I've just been downloading the binaries directly https://nodejs.org/en/download/
Could be that some of their nodes that host the downloads do work causing intermittent issues, but I don't know their infrastructure so this is merely speculation on my part.
johnny88
on 6 Apr 2020
AWS Codepipeline still having trouble downloading node 13.12.0. can't deploy my project.
EDIT: my build just succeeded, but it took 8 minutes for it to finish. i'm fairly certain the issue isn't resolved yet.
borgytan
on 6 Apr 2020
It seems to be working now.Thanks
dominicjeremiah2020
on 6 Apr 2020
Does not seam to be fixed till now. Is there anyone working on this issue from node?
tscislo
on 6 Apr 2020
still same problem for me:
14:22:56,853 [ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.6:install-node-and-yarn (frontend install node and yarn): Could not download Node.js: Got error code 500 from the server. -> [Help 1]
martonborbely84
on 6 Apr 2020
The fact that there were no single update from nodejs team is kind of suspicious.
filipgolonka
on 6 Apr 2020
It seems to be working now.Thanks
Apologies, I spoke too soon, Although Im able to download the version 11,15,0 manually but not via pipelines.
dominicjeremiah2020
on 6 Apr 2020
I made a ticket for the build team as well https://github.com/nodejs/build/issues/2263
johnny88
on 6 Apr 2020
Hi everyone, Node and Build are aware of issues people are seeing. Unfortunatly the downloads server has access limited to only @nodejs/build-infra which means we have to wait untill one of that team is available to fix the issue. Please keep telling us what you see to help diagnose (though please dont open new issues to avoid clutter) Sorry for any inconvenience caused!
AshCripps
on 6 Apr 2020
@AshCripps e.g.
node-gyp rebuild
ERR! stack Error: 500 response downloading https://nodejs.org/download/release/v6.12.3/node-v6.12.3-headers.tar.gz
chmielas
on 6 Apr 2020
Hi, I'm having this issue :
**Could not download node-linux-x64.tar.gz (org.nodejs:node:10.14.0)
Could not get resource 'https://nodejs.org/dist/v10.14.0/node-v10.14.0-linux-x64.tar.gz'.
Premature end of Content-Length delimited message body (expected: 18622101; received: 16547593**
Hope it helps to resolve the problem.
MelaFelec
on 6 Apr 2020
Please keep telling us what you see to help diagnose
We see super slow downloads or aborting downloads. From tonight:
[2020-04-06T01:42:04Z] Downloading https://nodejs.org/dist/v12.16.1/node-v12.16.1-linux-x64.tar.gz...
[2020-04-06T01:44:40Z] curl: (92) HTTP/2 stream 0 was not closed cleanly: INTERNAL_ERROR (err 2)
jgehrcke
on 6 Apr 2020
I made a ticket for the build team as well nodejs/build#2263
^
This is the relevant issue where you can expect updates. It’s not necessary to comment here with “this is happening for me too” comments – as Ash said, we’re aware of the problem.
addaleax
on 6 Apr 2020
This issue happens almost once a month and it's honestly very frustrating. :(
chingc
on 6 Apr 2020
Definitely the first time I remember experiencing this in 3 or 4 years of our builds yanking node down. Right now its working 40% of the time. When it doesn't work, it just 500s at the outset. No partial loading.
dbashford
on 6 Apr 2020
Could not download node-linux-x64.tar.gz (org.nodejs:node:10.15.0)
Could not get resource 'https://nodejs.org/dist/v10.15.0/node-v10.15.0-linux-x64.tar.gz'.
Read timed out
Hubert-Hoffman
on 6 Apr 2020
I'll go to the machine to take a look to see if I can see anything obvious as a starting point.
mhdawson
on 6 Apr 2020
Will use nodejs/build#2263 to comments.
mhdawson
on 6 Apr 2020
I'll go to the machine
Sorry for asking... the [single] machine serving all nodejs.org downloads in the world? :D
jgehrcke
on 6 Apr 2020
@jgehrcke
Sorry for asking... the [single] machine serving all nodejs.org downloads in the world? :D
Forget where I read it. But I think Cloudflare handles a lot of caching for Node. So it's very possible it is just a single machine, especially with how aggressively Cloudflare can caching stuff.
fishcharlie
on 6 Apr 2020
Sorry for asking... the [single] machine serving all nodejs.org downloads in the world? :D
I assume he meant his computer.
Since @mhdawson has pointed to https://github.com/nodejs/build/issues/2263 as the single source of truth for this discussion, I'm going to lock this discussion in favor of that one. There are already further updates there ❤️
bnb
on 6 Apr 2020
(Going to leave pinned until resolved so we don't see duplicate issues created.)
bnb
on 6 Apr 2020
@bnb is it possible to leave it open and locked? That might better reflect the situation, if technically possible.
sam-github
on 6 Apr 2020
Done ✅
bnb
on 6 Apr 2020
It's been resolved for some time now, closing.
bnoordhuis
on 7 Apr 2020
Related issues
akdor1154
·
3Comments
dfahlander
·
3Comments
willnwhite
·
3Comments
stevenvachon
·
3Comments
cong88
·
3Comments
Most helpful comment
Hi everyone, Node and Build are aware of issues people are seeing. Unfortunatly the downloads server has access limited to only @nodejs/build-infra which means we have to wait untill one of that team is available to fix the issue. Please keep telling us what you see to help diagnose (though please dont open new issues to avoid clutter) Sorry for any inconvenience caused!