Deploy fails on timeout

Support
,
1

Trying to do a deploy to prod the first issue I was having was a syntax error but I think it was due to a test and also my site being on an old version of npm and node. I have recently set my npm and node to match what is currently being used in netlify because when I tried to use the latest

npm - 8.15.0
node - 16.16.0

it would time out installing now that its set to

npm - 8.11.0
node - 16.16.0

the build below keeps timing out

Site name: naughty-ritchie-3030d6

Build Log:
12:30:45 PM: Waiting for other deploys from your team to complete. Check the queue: Netlify App
12:39:49 PM: Build ready to start
12:39:53 PM: build-image version: d7b3dbfb0846505993c9a131894d1858074c90b4 (focal)
12:39:53 PM: build-image tag: v4.10.1
12:39:53 PM: buildbot version: 37262c48b1f3cfa88c6caed707d29b19aef6a5a7
12:39:53 PM: Building without cache
12:39:53 PM: Starting to prepare the repo for build
12:39:54 PM: No cached dependencies found. Cloning fresh repo
12:39:54 PM: git clone GitHub - tairemad/tai: New website for tairemadailey.com
12:39:55 PM: Preparing Git Reference refs/heads/main
12:39:55 PM: Parsing package.json dependencies
12:39:56 PM: Starting build script
12:39:56 PM: Installing dependencies
12:39:56 PM: Python version set to 2.7
12:39:56 PM: v16.16.0 is already installed.
12:39:57 PM: Now using node v16.16.0 (npm v8.11.0)
12:39:57 PM: Started restoring cached build plugins
12:39:57 PM: Finished restoring cached build plugins
12:39:57 PM: Attempting ruby version 2.6.2, read from environment
12:39:57 PM: Required ruby-2.6.2 is not installed - installing.
12:39:57 PM: Searching for binary rubies, this might take some time.
12:39:57 PM: Found remote file https://rvm_io.global.ssl.fastly.net/binaries/ubuntu/20.04/x86_64/ruby-2.6.2.tar.bz2
12:39:57 PM: Checking requirements for ubuntu.
12:39:58 PM: Requirements installation successful.
12:39:58 PM: ruby-2.6.2 - #configure
12:39:58 PM: ruby-2.6.2 - #download
12:39:58 PM: ruby-2.6.2 - #validate archive
12:40:01 PM: ruby-2.6.2 - #extract
12:40:04 PM: ruby-2.6.2 - #validate binary
12:40:04 PM: ruby-2.6.2 - #setup
12:40:05 PM: ruby-2.6.2 - #gemset created /opt/buildhome/.rvm/gems/ruby-2.6.2@global
12:40:05 PM: ruby-2.6.2 - #importing gemset /opt/buildhome/.rvm/gemsets/global.gems…
12:40:05 PM: ruby-2.6.2 - #generating global wrappers…
12:40:05 PM: ruby-2.6.2 - #gemset created /opt/buildhome/.rvm/gems/ruby-2.6.2
12:40:05 PM: ruby-2.6.2 - #importing gemsetfile /opt/buildhome/.rvm/gemsets/default.gems evaluated to empty gem list
12:40:05 PM: ruby-2.6.2 - #generating default wrappers…
12:40:06 PM: Using /opt/buildhome/.rvm/gems/ruby-2.6.2
12:40:06 PM: Using ruby version 2.6.2
12:40:06 PM: Using PHP version 8.0
12:40:06 PM: No npm workspaces detected
12:40:06 PM: Started restoring cached node modules
12:40:06 PM: Finished restoring cached node modules
12:40:07 PM: Installing NPM modules using NPM version 8.11.0
12:40:07 PM: npm WARN config tmp This setting is no longer used. npm stores temporary files in a special
12:40:07 PM: npm WARN config location in the cache, and they are managed by
12:40:07 PM: npm WARN config cacache.
12:40:07 PM: npm WARN config tmp This setting is no longer used. npm stores temporary files in a special
12:40:07 PM: npm WARN config location in the cache, and they are managed by
12:40:07 PM: npm WARN config cacache.
12:49:03 PM: npm ERR! code ETIMEDOUT
12:49:03 PM: npm ERR! syscall connect
12:49:03 PM: npm ERR! errno ETIMEDOUT
12:49:03 PM: npm ERR! network request to https://nexus.common-build.gcp.oreilly.com/repository/npm-group/yargs-parser/-/yargs-parser-20.2.9.tgz failed, reason: connect ETIMEDOUT 35.222.138.145:443
12:49:03 PM: npm ERR! network This is a problem related to network connectivity.
12:49:03 PM: npm ERR! network In most cases you are behind a proxy or have bad network settings.
12:49:03 PM: npm ERR! network
12:49:03 PM: npm ERR! network If you are behind a proxy, please make sure that the
12:49:03 PM: npm ERR! network ‘proxy’ config is set properly. See: ‘npm help config’
12:49:03 PM: npm ERR! A complete log of this run can be found in:
12:49:03 PM: npm ERR! /opt/buildhome/.npm/_logs/2022-09-11T16_40_07_676Z-debug-0.log
12:49:03 PM: Error during NPM install
12:49:03 PM: Build was terminated: Build script returned non-zero exit code: 1
12:49:03 PM: Creating deploy upload records
12:49:03 PM: Failing build: Failed to build site
12:49:03 PM: Failed during stage ‘building site’: Build script returned non-zero exit code: 1 (Search results for '"non-zero exit code: 1"' - Netlify Support Forums)
12:49:03 PM: Finished processing build request in 9m9.886707318s

2

Hi @tairemad

The build seems to be unable to reach the endpoint of:

12:49:03 PM: npm ERR! network request to https://nexus.common-build.gcp.oreilly.com/repository/npm-group/yargs-parser/-/yargs-parser-20.2.9.tgz failed, reason: connect ETIMEDOUT 35.222.138.145:443

Is this working locally?

3

Yes this is…I believe this is on of those packages apart of create react app.

I dont have it as a direct dependency

"dependencies": {
    "@fortawesome/fontawesome-svg-core": "^6.2.0",
    "@fortawesome/free-brands-svg-icons": "^6.2.0",
    "@fortawesome/free-regular-svg-icons": "^6.2.0",
    "@fortawesome/free-solid-svg-icons": "^6.2.0",
    "@fortawesome/react-fontawesome": "^0.2.0",
    "@testing-library/jest-dom": "^5.16.5",
    "@testing-library/react": "^13.4.0",
    "@testing-library/user-event": "^13.5.0",
    "react": "^18.2.0",
    "react-dom": "^18.2.0",
    "react-scripts": "5.0.1",
    "web-vitals": "^2.1.4"
  },
4

Hi @tairemad

I am unable to connect to https://nexus.common-build.gcp.oreilly.com/repository/npm-group/yargs-parser/-/yargs-parser-20.2.9.tgz locally either, so I don’t believe this is a Netlify issue.

5

I don’t know what package is using that. I posted all I am using in my package.json above

6

Are there any devDependencies?

Can you share the repository?

7

Here is the repo GitHub - tairemad/tai: New website for tairemadailey.com it’s a basic create react app so dev dependencies are hidden

8

Thanks @tairemad.

If you look through the package-lock.json in the repository, you’ll see that all packages are coming from that source (nexus.common-build.gcp.oreilly.com.)

I suggest removing the package-lock.json from the repository.

9

Thank you I didn’t catch that

10

Thank you soo much @coelmay that fixed the issue…I didnt realize my other computer is set with a different nexxus account that could changed the package lock

2 Likes