11ty build suddenly fails and returns exit code 127

Support
1

Hi

I’m trying to figure out why my build for [condescending-keller-2d7116] is suddenly failing.

It is an 11ty install which used to work. But (together with some of my other installs) it stopped working on june 8th this year.

The log for [condescending-keller-2d7116] is here:

1:20:03 PM: Build ready to start
1:20:05 PM: build-image version: 30f629161c0736b1a3ecd8b418e5eeffab5c0faf
1:20:05 PM: build-image tag: v3.3.14
1:20:05 PM: buildbot version: a383ed3390159974f55f285b04457b44cb49efb0
1:20:05 PM: Fetching cached dependencies
1:20:05 PM: Starting to download cache of 172.8MB
1:20:07 PM: Finished downloading cache in 2.353545652s
1:20:07 PM: Starting to extract cache
1:20:16 PM: Finished extracting cache in 8.784922617s
1:20:16 PM: Finished fetching cache in 11.21088725s
1:20:16 PM: Starting to prepare the repo for build
1:20:17 PM: Preparing Git Reference refs/heads/master
1:20:23 PM: Starting build script
1:20:23 PM: Installing dependencies
1:20:24 PM: Started restoring cached node version
1:20:28 PM: Finished restoring cached node version
1:20:29 PM: v10.21.0 is already installed.
1:20:30 PM: Now using node v10.21.0 (npm v6.14.4)
1:20:30 PM: Started restoring cached build plugins
1:20:30 PM: Finished restoring cached build plugins
1:20:30 PM: Attempting ruby version 2.6.2, read from environment
1:20:32 PM: Using ruby version 2.6.2
1:20:32 PM: Using PHP version 5.6
1:20:32 PM: 5.2 is already installed.
1:20:32 PM: Using Swift version 5.2
1:20:32 PM: Started restoring cached node modules
1:20:32 PM: Finished restoring cached node modules
1:20:33 PM: Installing NPM modules using NPM version 6.14.4
1:20:41 PM: npm WARN dashboard@1.0.0 No repository field.
1:20:41 PM: npm
1:20:41 PM:  WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.2 (node_modules/chokidar/node_modules/fsevents):
1:20:41 PM: npm
1:20:41 PM: WARN notsup
1:20:41 PM:  SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
1:20:41 PM: npm
1:20:41 PM:  WARN optional
1:20:41 PM:  SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.3 (node_modules/rollup/node_modules/fsevents):
1:20:41 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
1:20:41 PM: npm
1:20:41 PM: WARN
1:20:41 PM: optional
1:20:41 PM:  SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.12 (node_modules/fsevents):
1:20:41 PM: npm
1:20:41 PM: WARN
1:20:41 PM: notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.12: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
1:20:41 PM: audited 1113 packages in 7.879s
1:20:42 PM: 32 packages are looking for funding
1:20:42 PM:   run `npm fund` for details
1:20:42 PM: found 13 vulnerabilities (4 low, 4 moderate, 5 high)
1:20:42 PM:   run `npm audit fix` to fix them, or `npm audit` for details
1:20:42 PM: NPM modules installed
1:20:42 PM: Started restoring cached go cache
1:20:42 PM: Finished restoring cached go cache
1:20:43 PM: go version go1.12 linux/amd64
1:20:43 PM: go version go1.12 linux/amd64
1:20:43 PM: Installing missing commands
1:20:43 PM: Verify run directory
1:20:44 PM: ​
1:20:44 PM: ┌─────────────────────────────┐
1:20:44 PM: │        Netlify Build        │
1:20:44 PM: └─────────────────────────────┘
1:20:44 PM: ​
1:20:44 PM: ❯ Version
1:20:44 PM:   @netlify/build 1.0.16
1:20:44 PM: ​
1:20:44 PM: ❯ Flags
1:20:44 PM:   mode: buildbot
1:20:44 PM: ​
1:20:44 PM: ❯ Current directory
1:20:44 PM:   /opt/build/repo
1:20:44 PM: ​
1:20:44 PM: ❯ Config file
1:20:44 PM:   No config file was defined: using default values.
1:20:44 PM: ​
1:20:44 PM: ❯ Context
1:20:44 PM:   production
1:20:45 PM: ​
1:20:45 PM: ┌────────────────────────────────┐
1:20:45 PM: │ 1. Build command from settings │
1:20:45 PM: └────────────────────────────────┘
1:20:45 PM: ​
1:20:45 PM: $ prod
1:20:45 PM: bash: prod: command not found
1:20:45 PM: ​
1:20:45 PM: ┌─────────────────────────────┐
1:20:45 PM: │   "build.command" failed    │
1:20:45 PM: └─────────────────────────────┘
1:20:45 PM: ​
1:20:45 PM:   Error message
1:20:45 PM:   Command failed with exit code 127: prod
1:20:45 PM: ​
1:20:45 PM:   Error location
1:20:45 PM:   In Build command from settings:
1:20:45 PM:   prod
1:20:45 PM: ​
1:20:45 PM:   Resolved config
1:20:45 PM:   build:
1:20:45 PM:     command: prod
1:20:45 PM:     publish: /opt/build/repo/dist
1:20:45 PM: Caching artifacts
1:20:45 PM: Started saving node modules
1:20:45 PM: Finished saving node modules
1:20:45 PM: Started saving build plugins
1:20:45 PM: Finished saving build plugins
1:20:45 PM: Started saving pip cache
1:20:46 PM: Finished saving pip cache
1:20:46 PM: Started saving emacs cask dependencies
1:20:46 PM: Finished saving emacs cask dependencies
1:20:46 PM: Started saving maven dependencies
1:20:46 PM: Finished saving maven dependencies
1:20:46 PM: Started saving boot dependencies
1:20:46 PM: Finished saving boot dependencies
1:20:46 PM: Started saving go dependencies
1:20:46 PM: Finished saving go dependencies
1:20:46 PM: Error running command: Build script returned non-zero exit code: 1
1:20:46 PM: Failing build: Failed to build site
1:20:46 PM: Failed during stage 'building site': Build script returned non-zero exit code: 1
1:20:46 PM: Finished processing build request in 41.343136068s

And here is my build settings from package.json

And this is my build settings from package.json

{
  "name": "dashboard",
  "version": "1.0.0",
  "description": "A simple dashboard to show datafrom projects with all api rolled up when static sites are generated = pure static and fast for the end user",
  "main": "index.js",
  "scripts": {
    "prod": "cross-env NODE_ENV=production npm-run-all clean -p prod:*",
    "prod:11ty": "eleventy --quiet",
    "prod:rollup": "rollup -c",
    "clean": "rimraf dist",
    "dev": "npm-run-all clean build:* -p dev:*",
    "dev:11ty": "eleventy --serve --quiet",
    "dev:rollup": "rollup -c -w"
  },
  "author": "Mark Buskbjerg",
  "license": "ISC",
}
// I removed depencies since those with @ in the depencyname counted as mentions :)

I’ve tried reverting to earlier commits where builds were succesful. But this doesn’t help me.

Also tried renaming build script from build to prod (was mentioned in your docs I shouldn’t use build)

I’ve been through the other topics with this error. But I’m not getting a solution.

The weirdest part seems to me that it just stopped working withoug me introducing new stuff to the git repo of either of my sites.

3

The only thing you can’t do is have a script named literally the word build. npm run build works fine. I think you might need npm run prod since you’ve made that change to package.json though! What do you use to build locally? Same command should be used here :slight_smile:

4

Thanks @fool!

I was sure I’ve already tried npm run prod - but appears I didn’t.

npm run prod was the solution :slight_smile: The deploy is working and I’m back to fixing other bugs again :smiley: