Help with site deployment

[jomarcenter-MJM]

hello I am having trouble deploying my site

it giving me a build errors

marvin mendoza / mjm creative works web · GitLab

with the following errors: failed during stage ‘building site’: Build script returned non-zero exit code: 127

build result

9:16:03 PM: Build ready to start
9:16:05 PM: build-image version: 9cade8af58c2cf3a17a1e9433d2e979149488837
9:16:05 PM: build-image tag: v3.3.5
9:16:05 PM: buildbot version: 2d05064ce3dd2eb95d282a24602ab707dd9581e8
9:16:05 PM: Fetching cached dependencies
9:16:06 PM: Failed to fetch cache, continuing with build
9:16:06 PM: Starting to prepare the repo for build
9:16:06 PM: No cached dependencies found. Cloning fresh repo
9:16:06 PM: git clone git@gitlab.com:jomarcenter-MJM/mjmcreativeworksweb
9:16:07 PM: Preparing Git Reference refs/heads/master
9:16:08 PM: Starting build script
9:16:08 PM: Installing dependencies
9:16:10 PM: Downloading and installing node v10.18.0...
9:16:10 PM: Downloading https://nodejs.org/dist/v10.18.0/node-v10.18.0-linux-x64.tar.xz...
9:16:10 PM: 
##########################################
9:16:10 PM: #################               83.1%
9:16:10 PM: 
#############################################################
9:16:10 PM: ########### 100.0%
9:16:10 PM: Computing checksum with sha256sum
9:16:10 PM: Checksums matched!
9:16:13 PM: Now using node v10.18.0 (npm v6.13.4)
9:16:13 PM: Attempting ruby version 2.6.2, read from environment
9:16:14 PM: Using ruby version 2.6.2
9:16:15 PM: Using PHP version 5.6
9:16:15 PM: Started restoring cached node modules
9:16:15 PM: Finished restoring cached node modules
9:16:15 PM: Installing NPM modules using NPM version 6.13.4
9:16:51 PM: > sharp@0.23.4 install /opt/build/repo/node_modules/sharp
9:16:51 PM: > (node install/libvips && node install/dll-copy && prebuild-install) || (node-gyp rebuild && node install/dll-copy)
9:16:51 PM: info
9:16:51 PM:  sharp Downloading https://github.com/lovell/sharp-libvips/releases/download/v8.8.1/libvips-8.8.1-linux-x64.tar.gz
9:16:55 PM: > node-sass@4.13.0 install /opt/build/repo/node_modules/node-sass
9:16:55 PM: > node scripts/install.js
9:16:56 PM: Downloading binary from https://github.com/sass/node-sass/releases/download/v4.13.0/linux-x64-64_binding.node
9:16:56 PM: Download complete
9:16:56 PM: Binary saved to /opt/build/repo/node_modules/node-sass/vendor/linux-x64-64/binding.node
9:16:56 PM: Caching binary to /opt/buildhome/.npm/node-sass/4.13.0/linux-x64-64_binding.node
9:16:57 PM: > core-js@2.6.11 postinstall /opt/build/repo/node_modules/core-js
9:16:57 PM: > node -e "try{require('./postinstall')}catch(e){}"
9:16:57 PM: Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!
9:16:57 PM: The project needs your help! Please consider supporting of core-js on Open Collective or Patreon: 
9:16:57 PM: > https://opencollective.com/core-js 
9:16:57 PM: > https://www.patreon.com/zloirock 
9:16:57 PM: Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)
9:16:57 PM: > core-js-pure@3.6.2 postinstall /opt/build/repo/node_modules/core-js-pure
9:16:57 PM: > node -e "try{require('./postinstall')}catch(e){}"
9:16:57 PM: > gatsby-telemetry@1.1.46 postinstall /opt/build/repo/node_modules/gatsby-telemetry
9:16:57 PM: > node src/postinstall.js || true
9:16:58 PM: > cwebp-bin@5.1.0 postinstall /opt/build/repo/node_modules/cwebp-bin
9:16:58 PM: > node lib/install.js
9:16:58 PM:   ✔ cwebp pre-build test passed successfully
9:16:58 PM: > mozjpeg@6.0.1 postinstall /opt/build/repo/node_modules/mozjpeg
9:16:58 PM: > node lib/install.js
9:16:59 PM:   ✔ mozjpeg pre-build test passed successfully
9:16:59 PM: > pngquant-bin@5.0.2 postinstall /opt/build/repo/node_modules/pngquant-bin
9:16:59 PM: > node lib/install.js
9:16:59 PM:   ✔ pngquant pre-build test passed successfully
9:16:59 PM: > gatsby-cli@2.8.23 postinstall /opt/build/repo/node_modules/gatsby/node_modules/gatsby-cli
9:16:59 PM: > node scripts/postinstall.js
9:16:59 PM: > gatsby@2.18.18 postinstall /opt/build/repo/node_modules/gatsby
9:16:59 PM: > node scripts/postinstall.js
9:17:00 PM: > node-sass@4.13.0 postinstall /opt/build/repo/node_modules/node-sass
9:17:00 PM: > node scripts/build.js
9:17:00 PM: Binary found at /opt/build/repo/node_modules/node-sass/vendor/linux-x64-64/binding.node
9:17:00 PM: Testing binary
9:17:00 PM: Binary is fine
9:17:00 PM: > catalyst-coin-website@ postinstall /opt/build/repo
9:17:00 PM: > npm rebuild node-sass
9:17:04 PM: > node-sass@4.13.0 install /opt/build/repo/node_modules/node-sass
9:17:04 PM: > node scripts/install.js
9:17:05 PM: node-sass build Binary found at /opt/build/repo/node_modules/node-sass/vendor/linux-x64-64/binding.node
9:17:05 PM: > node-sass@4.13.0 postinstall /opt/build/repo/node_modules/node-sass
9:17:05 PM: > node scripts/build.js
9:17:05 PM: Binary found at /opt/build/repo/node_modules/node-sass/vendor/linux-x64-64/binding.node
9:17:05 PM: Testing binary
9:17:05 PM: Binary is fine
9:17:05 PM: node-sass@4.13.0 /opt/build/repo/node_modules/node-sass
9:17:08 PM: npm
9:17:08 PM:  WARN catalyst-coin-website@ No repository field.
9:17:08 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.11 (node_modules/fsevents):
9:17:08 PM: npm
9:17:08 PM: WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.11: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
9:17:08 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.2 (node_modules/chokidar/node_modules/fsevents):
9:17:08 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
9:17:08 PM: added 2271 packages from 1095 contributors and audited 26034 packages in 51.823s
9:17:11 PM: 54 packages are looking for funding
9:17:11 PM:   run `npm fund` for details
9:17:11 PM: found 0 vulnerabilities
9:17:11 PM: NPM modules installed
9:17:11 PM: Started restoring cached go cache
9:17:11 PM: Finished restoring cached go cache
9:17:11 PM: unset GOOS;
9:17:11 PM: unset GOARCH;
9:17:11 PM: export GOROOT='/opt/buildhome/.gimme/versions/go1.12.linux.amd64';
9:17:11 PM: export PATH="/opt/buildhome/.gimme/versions/go1.12.linux.amd64/bin:${PATH}";
9:17:11 PM: go version >&2;
9:17:11 PM: export GIMME_ENV='/opt/buildhome/.gimme/env/go1.12.linux.amd64.env';
9:17:11 PM: go version go1.12 linux/amd64
9:17:11 PM: Installing missing commands
9:17:11 PM: Verify run directory
9:17:11 PM: Executing user command: gatsby build
9:17:14 PM: success open and validate gatsby-configs - 0.078s
9:17:15 PM: error Error in "/opt/build/repo/gatsby-node.js": ENOENT: no such file or directory, open './content/docs/master/nav.yml'
9:17:15 PM: 
9:17:15 PM:   Error: ENOENT: no such file or directory, open './content/docs/master/nav.yml'  
9:17:15 PM:   - create-docs-pages.js:18 versions.forEach.version
9:17:15 PM:     /opt/build/repo/src/actions/create-pages/create-docs-pages.js:18:5
9:17:15 PM:   
9:17:15 PM:   - Array.forEach
9:17:15 PM:   
9:17:15 PM:   - create-docs-pages.js:15 Object.<anonymous>
9:17:15 PM:     /opt/build/repo/src/actions/create-pages/create-docs-pages.js:15:10
9:17:15 PM:   
9:17:15 PM:   - v8-compile-cache.js:178 Module._compile
9:17:15 PM:     [repo]/[v8-compile-cache]/v8-compile-cache.js:178:30
9:17:15 PM:   
9:17:15 PM:   - loader.js:789 Object.Module._extensions..js
9:17:15 PM:     internal/modules/cjs/loader.js:789:10
9:17:15 PM:   
9:17:15 PM:   - loader.js:653 Module.load
9:17:15 PM:     internal/modules/cjs/loader.js:653:32
9:17:15 PM:   
9:17:15 PM:   - loader.js:593 tryModuleLoad
9:17:15 PM:     internal/modules/cjs/loader.js:593:12
9:17:15 PM:   
9:17:15 PM:   - loader.js:585 Function.Module._load
9:17:15 PM:     internal/modules/cjs/loader.js:585:3
9:17:15 PM:   
9:17:15 PM:   - loader.js:692 Module.require
9:17:15 PM:     internal/modules/cjs/loader.js:692:17
9:17:15 PM:   
9:17:15 PM:   - v8-compile-cache.js:159 require
9:17:15 PM:     [repo]/[v8-compile-cache]/v8-compile-cache.js:159:20
9:17:15 PM:   
9:17:15 PM:   - create-pages.js:1 Object.<anonymous>
9:17:15 PM:     /opt/build/repo/src/actions/create-pages.js:1:87
9:17:15 PM:   
9:17:15 PM:   - v8-compile-cache.js:178 Module._compile
9:17:15 PM:     [repo]/[v8-compile-cache]/v8-compile-cache.js:178:30
9:17:15 PM:   
9:17:15 PM:   - loader.js:789 Object.Module._extensions..js
9:17:15 PM:     internal/modules/cjs/loader.js:789:10
9:17:15 PM:   
9:17:15 PM:   - loader.js:653 Module.load
9:17:15 PM:     internal/modules/cjs/loader.js:653:32
9:17:15 PM:   
9:17:15 PM: 
9:17:15 PM: not finished load plugins - 1.109s
9:17:15 PM: Skipping functions preparation step: no functions directory set
9:17:15 PM: Caching artifacts
9:17:15 PM: Started saving node modules
9:17:15 PM: Finished saving node modules
9:17:15 PM: Started saving pip cache
9:17:15 PM: Finished saving pip cache
9:17:15 PM: Started saving emacs cask dependencies
9:17:15 PM: Finished saving emacs cask dependencies
9:17:15 PM: Started saving maven dependencies
9:17:15 PM: Finished saving maven dependencies
9:17:15 PM: Started saving boot dependencies
9:17:15 PM: Finished saving boot dependencies
9:17:15 PM: Started saving go dependencies
9:17:15 PM: Finished saving go dependencies
9:17:19 PM: Error running command: Build script returned non-zero exit code: 1
9:17:19 PM: Failing build: Failed to build site
9:17:19 PM: failed during stage 'building site': Build script returned non-zero exit code: 1
9:17:19 PM: Finished processing build request in 1m14.276711734s

IDK if I missed something or something else

And also I am planning to install forestry CMS on it as well.

[perry]

hi there, welcome!

question 1: does it build locally - always the first thing to check.
question 2: is the file ./content/docs/master/nav.yml the build system is complaining about in the repo? Do keep in mind the system is case sensitive.

this post contains a lot of helpful information.

[Support Guide] Debugging Netlify site builds

Last reviewed by Netlify Support - August, 2023 Note: This article is only about builds within Netlify’s Continuous Integration (CI) environment, as triggered from git commits or from incoming build webhooks. You can learn more in depth about how Netlify builds your site in this article about how our build bots build sites. Some background There are a fair number of reasons that a build could fail in Netlify’s CI environment, even if building works locally. Testing locally is always the place …

good luck - let us know if you can’t make any progress.