Hello, it's impossible to install node 10.x
Steps to reproduce with docker:
docker run -it amazonlinux sh
then
yum install -y gcc-c++ make
curl -sL https://rpm.nodesource.com/setup_10.x | bash -E
yum remove -y nodejs npm && yum install -y nodejs
Result:
sh-4.2# yum remove -y nodejs npm && yum install -y nodejs
Loaded plugins: ovl, priorities
No Match for argument: nodejs
No Match for argument: npm
No Packages marked for removal
Loaded plugins: ovl, priorities
nodesource | 2.5 kB 00:00:00
nodesource/x86_64/primary_db | 46 kB 00:00:00
Resolving Dependencies
--> Running transaction check
---> Package nodejs.x86_64 2:10.22.0-1nodesource will be installed
--> Finished Dependency Resolution
Dependencies Resolved
====================================================================================================================================================================================================
Package Arch Version Repository Size
====================================================================================================================================================================================================
Installing:
nodejs x86_64 2:10.22.0-1nodesource nodesource 20 M
Transaction Summary
====================================================================================================================================================================================================
Install 1 Package
Total download size: 20 M
Installed size: 61 M
Downloading packages:
nodejs-10.22.0-1nodesource.x86 FAILED 98% [=======================================================================- ] 3.0 MB/s | 20 MB 00:00:00 ETA
https://rpm.nodesource.com/pub_10.x/el/7/x86_64/nodejs-10.22.0-1nodesource.x86_64.rpm: [Errno -1] Package does not match intended download. Suggestion: run yum --enablerepo=nodesource clean metadata
Trying other mirror.
Error downloading packages:
2:nodejs-10.22.0-1nodesource.x86_64: [Errno 256] No more mirrors to try.
My website was down for 3hours because of this :'(
Experiencing the same issue - preventing deployments from AWS in several environments due to the repo being broken.
@mattcharlton you can replace to setup_12.x to install nodejs 12 instead (not broken) but you have to be sure all your dependencies works with node 12
We're not in a position to do that sadly because of our development lifecycle and because of multiple dependencies. It was a struggle to get the developers to upgrade from nodejs 8 ;)
Same here.
I tried 12.x and got: https://rpm.nodesource.com/pub_12.x/el/7/x86_64/nodejs-10.22.0-1nodesource.x86_64.rpm: [Errno 14] HTTPS Error 404 - Not Found
We also got this error yesterday. The error appears to be fixed temporarily yesterday but resurfaced again this morning. Is nodejs-10.22.0-1nodesource.x86_64.rpm that got released yesterday somehow got corrupted? We also cannot upgrade to node 12 at this time due to incompatibilities in our ecosystem.
I have a Amazon Linux 2 server in Virginia that successfully downloads nodejs 10.x as demonstrated above:
curl -sL https://rpm.nodesource.com/setup_10.x | bash -E
However, the Amazon Linux 2 server in Paris is experiencing the same error as indicated in the above issue. Perhaps the problem is regional. I also notice that @hbouhadji is based in France, adding more to my thinking that this failure to download is a regional problem.
Yeah we鈥檙e in the UK deploying to EU-West-2 so it does sound regional.
Still seeing this issue this morning, Not in EU-West-1. Only in EU-West-2.
EU-West-1 doesn't have the Nodesource gpg key in place.
EU-West-2 does, and fails.
I've found that If we run:
rm -f /etc/pki/rpm-gpg/NODESOURCE-GPG-SIGNING-KEY-EL
prior to trying installation, this works. Adjust your scripts using the above and hopefully it'll get you past the blocker whilst the issue with that key is resolved.
I'll raise a support ticket with AWS as its obviously something on the AMI.
Look my first post @mattcharlton, with the docker image amazonlinux (you can try locally) there is not any NODESOURCE-GPG-SIGNING-KEY-EL file but still failing at the download of the package.
Downloading packages:
nodejs-10.22.0-1nodesource.x86 FAILED 53% [====================================== ] 0.0 B/s | 11 MB --:--:-- ETA
https://rpm.nodesource.com/pub_10.x/el/7/x86_64/nodejs-10.22.0-1nodesource.x86_64.rpm: [Errno -1] Package does not match intended download. Suggestion: run yum --enablerepo=nodesource clean metadata
Trying other mirror.
Error downloading packages:
2:nodejs-10.22.0-1nodesource.x86_64: [Errno 256] No more mirrors to try.
(I have a UK London IP)
Look my first post @mattcharlton, with the docker image amazonlinux (you can try locally) there is not any NODESOURCE-GPG-SIGNING-KEY-EL file but still failing at the download of the package.
Downloading packages: nodejs-10.22.0-1nodesource.x86 FAILED 53% [====================================== ] 0.0 B/s | 11 MB --:--:-- ETA https://rpm.nodesource.com/pub_10.x/el/7/x86_64/nodejs-10.22.0-1nodesource.x86_64.rpm: [Errno -1] Package does not match intended download. Suggestion: run yum --enablerepo=nodesource clean metadata Trying other mirror. Error downloading packages: 2:nodejs-10.22.0-1nodesource.x86_64: [Errno 256] No more mirrors to try.(I have a UK London IP)
I replicated on a brand new EC2 instance in London, couldn't download the package, deleted the GPG key, was able to download and install the package.
Spun up another one and replicated and tested the same. Either way - I've logged a support request with AWS.
The more we look into this, the more it feels like an issue with an upstream mirror somewhere.
Hit and miss as to whether it works or not.
Still looking into things here - if I find something that definitely fixes it until whoever is responsible fixes it properly, I'll share.
Is there any update on this? This is causing a fair amount of disruption to our builds (and we cannot currently upgrade to Node 12).
The CDN provider has had problems updating the cache of some locations in Europe. We are actively working to fix it.
We ended up putting in an install of nodeJS 12 in the user data for the build ec2 instances. This means that node12 was already in place when node10 tries to install (and would fail) but as a newer version is already in place, it skips installation.
Appreciate this won鈥檛 work for anyone who can鈥檛 upgrade to node 12 but we were lucky that our temporary ec2 instances we use for deployment had no dependencies.
Other than this we found no reliable workaround as the issue was hit and miss.
@hbouhadji can you confirm that this was stabilized?
Hello @igsu,
Nope still failing:
Dependencies Resolved
============================================================================================================================================================================================================================
Package Arch Version Repository Size
============================================================================================================================================================================================================================
Installing:
nodejs x86_64 2:10.22.0-1nodesource nodesource 20 M
Transaction Summary
============================================================================================================================================================================================================================
Install 1 Package
Total download size: 20 M
Installed size: 61 M
Downloading packages:
nodejs-10.22.0-1nodesource.x86 FAILED 97% [=================================================================================== ] 5.6 MB/s | 19 MB 00:00:00 ETA
https://rpm.nodesource.com/pub_10.x/el/7/x86_64/nodejs-10.22.0-1nodesource.x86_64.rpm: [Errno -1] Package does not match intended download. Suggestion: run yum --enablerepo=nodesource clean metadata 19 MB 00:00:00 ETA
Trying other mirror.
Error downloading packages:
2:nodejs-10.22.0-1nodesource.x86_64: [Errno 256] No more mirrors to try.
Most helpful comment
The CDN provider has had problems updating the cache of some locations in Europe. We are actively working to fix it.