Failed to install node version '12.18.0'

Question

Failed to install node version '12.18.0'

Closed this issue 4 years ago · 43 comments

mahmoud-abdallah863 commented 4 years ago

Describe the bug
It was working fine few days ago, until today.
I made some changes in the app (nothing related to npm) and it fail to deploy.

DEPLOY LOG:

1:57:42 PM: Build ready to start
1:57:44 PM: build-image version: b0258b965567defc4a2d7e2f2dec2e00c8f73ad6
1:57:44 PM: build-image tag: v3.4.1
1:57:44 PM: buildbot version: fcbc7a79f7372e5995cf02954ef19fc48d20c871
1:57:44 PM: Fetching cached dependencies
1:57:44 PM: Starting to download cache of 111.6MB
1:57:45 PM: Finished downloading cache in 931.829534ms
1:57:45 PM: Starting to extract cache
1:57:50 PM: Finished extracting cache in 5.155362108s
1:57:50 PM: Finished fetching cache in 6.12420572s
1:57:50 PM: Starting to prepare the repo for build
1:57:51 PM: Preparing Git Reference refs/heads/master
1:57:52 PM: Different publish path detected, going to use the one specified in the Netlify configuration file: 'build' versus 'build/' in the Netlify UI
1:57:52 PM: Starting build script
1:57:52 PM: Installing dependencies
1:57:52 PM: Python version set to 2.7
1:57:53 PM: Started restoring cached node version
1:57:56 PM: Finished restoring cached node version
1:58:12 PM: Version '12.18.0' not found - try `nvm ls-remote` to browse available versions.
1:58:12 PM: Failed to install node version '12.18.0'
1:58:12 PM: Error running command: Build script returned non-zero exit code: 1
1:58:12 PM: Failing build: Failed to build site
1:58:12 PM: Failed during stage 'building site': Build script returned non-zero exit code: 1
1:58:12 PM: Finished processing build request in 28.285263389s

emilyliu1223 commented 4 years ago

Same

GrzesiekMusial commented 4 years ago

same

Perrottarichard commented 4 years ago

same

Answer 1 · 2020-08-30T11:57:45.000Z

I have the same problem

Answer 2 · 2020-08-30T11:58:52.000Z

Same issue here. Local build works fine and project was working fine yesterday.

Answer 3 · 2020-08-30T11:59:33.000Z

I have the same problem

Answer 4 · 2020-08-30T11:59:45.000Z

I have the same problem

Answer 5 · 2020-08-30T12:00:03.000Z

Same here, just created an account and tried to deploy my website. Works fine on gh-pages.

Answer 6 · 2020-08-30T12:00:54.000Z

it certainly comes from netlify

Answer 7 · 2020-08-30T12:01:05.000Z

this is a bug... I have the same issue, they might fix it soon

Answer 8 · 2020-08-30T12:04:57.000Z

Plus one here, was working fine an hour or so ago

Answer 9 · 2020-08-30T12:07:33.000Z

same problem here

Answer 10 · 2020-08-30T12:11:14.000Z

It's Sunday afternoon, they may be doing some maintenance, everything was working fine an hour ago.

Answer 11 · 2020-08-30T12:11:51.000Z

Plus one here, was working fine an hour or so ago

everything was working fine an hour ago

Answer 12 · 2020-08-30T12:16:49.000Z

same here :D let's just wait an keep working on a project

Answer 13 · 2020-08-30T12:16:51.000Z

Same here, just made a PR to the branch i deploy from and shows that error

Answer 14 · 2020-08-30T12:19:09.000Z

Same issue here. Working fine on vercel.

Answer 15 · 2020-08-30T12:20:13.000Z

Same issue here.

Answer 16 · 2020-08-30T12:21:11.000Z

I guess we just need to wait them to fix it.

Answer 17 · 2020-08-30T12:23:46.000Z

Or someone can fixes it and sends PR for them???

Answer 18 · 2020-08-30T12:25:46.000Z

Same here !!!!!!!! I hope they fix it soon

Answer 19 · 2020-08-30T12:29:28.000Z

Same here, still not working...

Answer 20 · 2020-08-30T12:29:46.000Z

Is it possible to set node version in package.json engine field? Does it work?

Answer 21 · 2020-08-30T12:29:46.000Z

Same here, still not working...

Answer 22 · 2020-08-30T12:32:26.000Z

Is it possible to set node version in package.json engine field? Does it work?

I tried changing node version in package.json, it didn't work

Answer 23 · 2020-08-30T12:32:32.000Z

Is it possible to set node version in package.json engine field? Does it work?

I tried to set the NODE_VERSION = '10.18.0' in the environment variable in the netlify.toml and in the GUI, but it did not work.

Answer 24 · 2020-08-30T12:33:00.000Z

They're investigating - https://www.netlifystatus.com/incidents/sbl67cwypcf0

Answer 25 · 2020-08-30T12:33:28.000Z

They're investigating - https://www.netlifystatus.com/incidents/sbl67cwypcf0

Thanks @cat-street, was just going to post that.

Answer 26 · 2020-08-30T12:34:34.000Z

I'm surprised at how fast google indexed this as the first result.

Btw #metoo

Answer 27 · 2020-08-30T12:36:05.000Z

Ah! developers! 🤣

Answer 28 · 2020-08-30T12:38:59.000Z

and i thought i am the only one have done something messy

Answer 29 · 2020-08-30T12:56:37.000Z

Setting NODE_ENV to 14 worked for me

Answer 30 · 2020-08-30T13:00:03.000Z

Setting NODE_ENV to 14 worked for me

Worked for me

Answer 31 · 2020-08-30T13:00:21.000Z

Setting NODE_ENV to 14 worked for me

Worked for me too

Answer 32 · 2020-08-30T13:06:39.000Z

or make : npm run build
npm install netlify-cli -g
netlify deploy

Answer 33 · 2020-08-30T13:10:56.000Z

They fixed the bug...

Answer 34 · 2020-08-30T13:21:59.000Z

Thanks for the follow up @mahmoud-abdallah863.
Cloudflare hasn't declared the incident resolved yet https://www.cloudflarestatus.com/, but we're seeing normal build error levels as reported here https://www.netlifystatus.com/incidents/sbl67cwypcf0

Answer 35 · 2020-09-16T20:45:17.000Z

I don't think this is fixed. We just encountered what looks to be the same build failure today at 2:15 PM:

2:15:42 PM: Build ready to start
2:15:44 PM: build-image version: b0258b965567defc4a2d7e2f2dec2e00c8f73ad6
2:15:44 PM: build-image tag: v3.4.1
2:15:44 PM: buildbot version: 8c957a6d09a03023cea4239847cc73a9cb64eeb7
2:15:44 PM: Fetching cached dependencies
2:15:44 PM: Failed to fetch cache, continuing with build
2:15:44 PM: Starting to prepare the repo for build
2:15:45 PM: No cached dependencies found. Cloning fresh repo
2:15:45 PM: git clone https://github.com/RangeMPLS/Stouse-White-Label
2:15:48 PM: Preparing Git Reference refs/heads/master
2:15:50 PM: Different build dir detected, going to use the one specified in the Netlify configuration file: 'front-end' versus 'front-end/' in the Netlify UI
2:15:50 PM: Different publish path detected, going to use the one specified in the Netlify configuration file: 'front-end/build' versus 'build/' in the Netlify UI
2:15:50 PM: Detected ignore command in Netlify configuration file. Proceeding with the specified command: '/bin/false'
2:15:51 PM: Starting build script
2:15:51 PM: Installing dependencies
2:15:51 PM: Python version set to 2.7
2:20:52 PM: Version '12.18.0' not found - try `nvm ls-remote` to browse available versions.
2:20:52 PM: Failed to install node version '12.18.0'
2:20:52 PM: Error running command: Build script returned non-zero exit code: 1
2:20:52 PM: Failing build: Failed to build site
2:20:52 PM: Failed during stage 'building site': Build script returned non-zero exit code: 1
2:20:52 PM: Finished processing build request in 5m8.533233305s

Is there something we need to do to prevent this error? For some reason, when I manually triggered a redeploy, it succeeded! Regarding the node version, here's what the redeploy logged:

3:21:28 PM: v12.18.0 is already installed.
3:21:29 PM: Now using node v12.18.0 (npm v6.14.4)

But we really need to figure out how to get our programmatic deployments working again, so any info on this issue would be greatly appreciated! Thanks!

Answer 36 · 2020-09-16T20:50:50.000Z

Hi @noerbot,

Thanks for reporting.
This was due to a problem with npm itself, which has now been fixed.

Answer 37 · 2020-11-21T03:50:32.000Z

I'm still getting the same problem

11:26:00 AM: Build ready to start
11:26:02 AM: build-image version: 09c2cdcdf242cf2f57c9ee0fcad9d298fad9ad41
11:26:02 AM: build-image tag: v3.5.0
11:26:02 AM: buildbot version: 172aa31cb336bae73f9eb30159b9f95fe46f2e63
11:26:02 AM: Building without cache
11:26:02 AM: Starting to prepare the repo for build
11:26:02 AM: No cached dependencies found. Cloning fresh repo
11:26:02 AM: git clone https://github.com/cjl12377/Jeng-Blog
11:26:04 AM: Preparing Git Reference refs/heads/master
11:26:05 AM: Starting build script
11:26:05 AM: Installing dependencies
11:26:05 AM: Python version set to 2.7
11:27:10 AM: Version '12.18.0' not found - try nvm ls-remote to browse available versions.
11:27:10 AM: Failed to install node version '12.18.0'
11:27:10 AM: Build was terminated: Build script returned non-zero exit code: 1
11:27:10 AM: Failing build: Failed to build site
11:27:10 AM: Failed during stage 'building site': Build script returned non-zero exit code: 1
11:27:10 AM: Finished processing build request in 1m8.114190186s

Answer 38 · 2020-11-22T00:20:10.000Z

I'm still getting the same problem

11:26:00 AM: Build ready to start
11:26:02 AM: build-image version: 09c2cdcdf242cf2f57c9ee0fcad9d298fad9ad41
11:26:02 AM: build-image tag: v3.5.0
11:26:02 AM: buildbot version: 172aa31cb336bae73f9eb30159b9f95fe46f2e63
11:26:02 AM: Building without cache
11:26:02 AM: Starting to prepare the repo for build
11:26:02 AM: No cached dependencies found. Cloning fresh repo
11:26:02 AM: git clone https://github.com/cjl12377/Jeng-Blog
11:26:04 AM: Preparing Git Reference refs/heads/master
11:26:05 AM: Starting build script
11:26:05 AM: Installing dependencies
11:26:05 AM: Python version set to 2.7
11:27:10 AM: Version '12.18.0' not found - try nvm ls-remote to browse available versions.
11:27:10 AM: Failed to install node version '12.18.0'
11:27:10 AM: Build was terminated: Build script returned non-zero exit code: 1
11:27:10 AM: Failing build: Failed to build site
11:27:10 AM: Failed during stage 'building site': Build script returned non-zero exit code: 1
11:27:10 AM: Finished processing build request in 1m8.114190186s

This issue is happening from time to time, everytime they fix it but for somereason it breaks again

Answer 39 · 2020-11-23T15:28:30.000Z

Hi @cjl12377 and @mahmoud-abdallah863,
This seems to be a problem with npm.
Are you still experiencing this problem today?

Answer 40 · 2020-11-23T15:42:07.000Z

Hi @cjl12377 and @mahmoud-abdallah863,
This seems to be a problem with npm.
Are you still experiencing this problem today?

I just made a build and their is no problems.