Gatsby Failed Build on Netlify

Question

I'm using gatsby wordpress experimental and have a build error when I try to upload to Netlify.

Netlify has told me that it's not an issue with Netlify, but with the build process. However, I cant find my error.

When I clone my git repository, the build works fine locally. It just cant get pushed through to Netlify. Netlify support says when he cloned the github repo, he saw the same error as what I'm seeing in my Netlify deploy log, which makes me wonder if I have some global package installed on my computer that isn't going Netlify and causing this error.

I cant re-create the error on my computer tho. The build works for me.

Public Repo: https://github.com/RyanPinPB/pdm-gatsby

The error that I'm stumped on:

success write out redirect data - 0.018s
⠁ vips_value_hash: no case for NULL
    type 64, gchararray
    generic 53, GParamString
vips_value_hash: no case for 0.000000
    type 60, gdouble
    generic 109, GParamDouble
vips_value_hash: no case for FALSE
    type 20, gboolean
    generic 76, GParamBoolean
vips_value_hash: no case for ((VipsAccess) VIPS_ACCESS_RANDOM)
    type 73595104, VipsAccess
    generic 80, GParamEnum
vips_value_hash: no case for FALSE
    type 20, gboolean
    generic 76, GParamBoolean
Segmentation fault (core dumped)

Any idea what this error actually means?

Here's the full build log from Netlify:

11:01:43 AM: Build ready to start
11:01:45 AM: build-image version: 09c2cdcdf242cf2f57c9ee0fcad9d298fad9ad41
11:01:45 AM: build-image tag: v3.5.0
11:01:45 AM: buildbot version: 8df8a50b1177b0b57364d20e0ea150448924cebf
11:01:45 AM: Fetching cached dependencies
11:01:45 AM: Starting to download cache of 244.2MB
11:01:47 AM: Finished downloading cache in 1.566800161s
11:01:47 AM: Starting to extract cache
11:01:56 AM: Finished extracting cache in 9.099291187s
11:01:56 AM: Finished fetching cache in 10.772692856s
11:01:56 AM: Starting to prepare the repo for build
11:01:56 AM: Preparing Git Reference refs/heads/master
11:01:59 AM: Different publish path detected, going to use the one specified in the Netlify configuration file: 'public' versus 'public/' in the Netlify UI
11:02:00 AM: Starting build script
11:02:00 AM: Installing dependencies
11:02:00 AM: Python version set to 2.7
11:02:00 AM: Started restoring cached node version
11:02:03 AM: Finished restoring cached node version
11:02:04 AM: v12.18.0 is already installed.
11:02:05 AM: Now using node v12.18.0 (npm v6.14.4)
11:02:05 AM: Started restoring cached build plugins
11:02:05 AM: Finished restoring cached build plugins
11:02:05 AM: Attempting ruby version 2.7.1, read from environment
11:02:06 AM: Using ruby version 2.7.1
11:02:06 AM: Using PHP version 5.6
11:02:06 AM: Started restoring cached node modules
11:02:06 AM: Finished restoring cached node modules
11:02:07 AM: Installing NPM modules using NPM version 6.14.4
11:02:30 AM: > [email protected] install /opt/build/repo/node_modules/gatsby-plugin-manifest/node_modules/sharp
11:02:30 AM: > (node install/libvips && node install/dll-copy && prebuild-install) || (node-gyp rebuild && node install/dll-copy)
11:02:31 AM: info sharp Downloading https://github.com/lovell/sharp-libvips/releases/download/v8.10.0/libvips-8.10.0-linux-x64.tar.br
11:02:33 AM: > [email protected] install /opt/build/repo/node_modules/gatsby-plugin-sharp/node_modules/sharp
11:02:33 AM: > (node install/libvips && node install/dll-copy && prebuild-install) || (node-gyp rebuild && node install/dll-copy)
11:02:34 AM: info sharp Using cached /opt/buildhome/.npm/_libvips/libvips-8.10.0-linux-x64.tar.br
11:02:36 AM: > [email protected] postinstall /opt/build/repo/node_modules/core-js-pure
11:02:36 AM: > node -e "try{require('./postinstall')}catch(e){}"
11:02:36 AM: > [email protected] postinstall /opt/build/repo/node_modules/gatsby/node_modules/core-js
11:02:36 AM: > node -e "try{require('./postinstall')}catch(e){}"
11:02:36 AM: > [email protected] postinstall /opt/build/repo/node_modules/gatsby-telemetry
11:02:36 AM: > node src/postinstall.js || true
11:02:36 AM: > [email protected] postinstall /opt/build/repo/node_modules/gatsby/node_modules/gatsby-cli
11:02:36 AM: > node scripts/postinstall.js
11:02:36 AM: > [email protected] postinstall /opt/build/repo/node_modules/gatsby
11:02:36 AM: > node scripts/postinstall.js
11:02:39 AM: npm WARN @reach/[email protected] requires a peer of react@^16.8.0 but none is installed. You must install peer dependencies yourself.
11:02:39 AM: npm WARN @reach/[email protected] requires a peer of react-dom@^16.8.0 but none is installed. You must install peer dependencies yourself.
11:02:39 AM: npm WARN @reach/[email protected] requires a peer of react@^16.8.0 but none is installed. You must install peer dependencies yourself.
11:02:39 AM: npm WARN @reach/[email protected] requires a peer of react-dom@^16.8.0 but none is installed. You must install peer dependencies yourself.
11:02:39 AM: npm WARN @reach/[email protected] requires a peer of [email protected] || 16.x || 16.4.0-alpha.0911da3 but none is installed. You must install peer dependencies yourself.
11:02:39 AM: npm WARN @reach/[email protected] requires a peer of [email protected] || 16.x || 16.4.0-alpha.0911da3 but none is installed. You must install peer dependencies yourself.
11:02:39 AM: npm WARN @reach/[email protected] requires a peer of react@^16.8.0 but none is installed. You must install peer dependencies yourself.
11:02:39 AM: npm WARN @reach/[email protected] requires a peer of react-dom@^16.8.0 but none is installed. You must install peer dependencies yourself.
11:02:39 AM: npm WARN @reach/[email protected] requires a peer of react@^16.8.0 but none is installed. You must install peer dependencies yourself.
11:02:39 AM: npm WARN @reach/[email protected] requires a peer of react-dom@^16.8.0 but none is installed. You must install peer dependencies yourself.
11:02:39 AM: npm WARN [email protected] requires a peer of react@^0.14.0 || ^15.0.0 || ^16.0.0 but none is installed. You must install peer dependencies yourself.
11:02:39 AM: npm WARN [email protected] requires a peer of react@^16.8 but none is installed. You must install peer dependencies yourself.
11:02:39 AM: npm WARN [email protected] requires a peer of react-dom@^16.8 but none is installed. You must install peer dependencies yourself.
11:02:39 AM: npm WARN [email protected] requires a peer of react@^15.3.0 || ^16.0.0 but none is installed. You must install peer dependencies yourself.
11:02:39 AM: npm WARN [email protected] requires a peer of react@^16.8.0 but none is installed. You must install peer dependencies yourself.
11:02:39 AM: npm WARN [email protected] requires a peer of react@^16.0.0 but none is installed. You must install peer dependencies yourself.
11:02:39 AM: npm WARN [email protected] requires a peer of react@^16.8.0 but none is installed. You must install peer dependencies yourself.
11:02:39 AM: npm WARN [email protected] requires a peer of react@^16.8.0 but none is installed. You must install peer dependencies yourself.
11:02:39 AM: npm WARN [email protected] requires a peer of react@^16.3.0 but none is installed. You must install peer dependencies yourself.
11:02:39 AM: npm WARN [email protected] requires a peer of react@^16.8.0 but none is installed. You must install peer dependencies yourself.
11:02:39 AM: npm WARN [email protected] requires a peer of typescript@>=2.7 but none is installed. You must install peer dependencies yourself.
11:02:39 AM: npm WARN [email protected] requires a peer of typescript@>=2.8.0 || >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta but none is installed. You must install peer dependencies yourself.
11:02:39 AM: npm WARN [email protected] requires a peer of react@^16.8.0 but none is installed. You must install peer dependencies yourself.
11:02:39 AM: npm WARN [email protected] requires a peer of react@^16.8.0 but none is installed. You must install peer dependencies yourself.
11:02:39 AM: npm WARN [email protected] No repository field.
11:02:39 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents):
11:02:39 AM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
11:02:39 AM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/chokidar/node_modules/fsevents):
11:02:39 AM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
11:02:39 AM: added 132 packages from 208 contributors, removed 196 packages, updated 169 packages and audited 2539 packages in 31.091s
11:02:40 AM: 147 packages are looking for funding
11:02:40 AM:   run `npm fund` for details
11:02:40 AM: found 0 vulnerabilities
11:02:40 AM: NPM modules installed
11:02:41 AM: Started restoring cached go cache
11:02:41 AM: Finished restoring cached go cache
11:02:41 AM: go version go1.14.4 linux/amd64
11:02:41 AM: go version go1.14.4 linux/amd64
11:02:41 AM: Installing missing commands
11:02:41 AM: Verify run directory
11:02:42 AM: 
11:02:42 AM: ────────────────────────────────────────────────────────────────
11:02:42 AM:   Netlify Build                                                 
11:02:42 AM: ────────────────────────────────────────────────────────────────
11:02:42 AM: 
11:02:42 AM: ❯ Version
11:02:42 AM:   @netlify/build 5.3.3
11:02:42 AM: 
11:02:42 AM: ❯ Flags
11:02:42 AM:   deployId: 5fbeaa17e73bf00007ce6dab
11:02:42 AM:   mode: buildbot
11:02:42 AM: 
11:02:42 AM: ❯ Current directory
11:02:42 AM:   /opt/build/repo
11:02:42 AM: 
11:02:42 AM: ❯ Config file
11:02:42 AM:   No config file was defined: using default values.
11:02:42 AM: 
11:02:42 AM: ❯ Context
11:02:42 AM:   production
11:02:42 AM: 
11:02:42 AM: ────────────────────────────────────────────────────────────────
11:02:42 AM:   1. Build command from Netlify app                             
11:02:42 AM: ────────────────────────────────────────────────────────────────
11:02:42 AM: 
11:02:42 AM: $ gatsby build
11:02:46 AM: success open and validate gatsby-configs - 0.043s
11:02:47 AM: success load plugins - 1.200s
11:02:47 AM: plugin-netlify-cache: Restoring 46 cached files for .cache directory with 0 already existing files.
11:02:48 AM: plugin-netlify-cache: Netlify cache restored
11:02:48 AM: success onPreInit - 1.074s
11:02:48 AM: success delete html and css files from previous builds - 0.003s
11:02:48 AM: info We've detected that the Gatsby cache is incomplete (the .cache directory existsbut the public directory does not). As a precaution, we're deleting your site's
11:02:48 AM: cache to ensure there's no stale data.success initialize cache - 0.166s
11:02:49 AM: success copy gatsby files - 0.036s
11:02:49 AM: success onPreBootstrap - 0.014s
11:02:52 AM: ⠀
11:02:52 AM: info  gatsby-source-wordpress 
11:02:52 AM:    This is either your first build or the cache was cleared.
11:02:52 AM:    Please wait while your WordPress data is synced to your Gatsby cache.
11:02:52 AM:    Maybe now's a good time to get up and stretch? :D
11:02:54 AM: success  gatsby-source-wordpress  writing GraphQL queries to disk at ./WordPress/GraphQL/ - 0.234s
11:02:54 AM: success  gatsby-source-wordpress  ingest WPGraphQL schema - 2.765s
11:02:54 AM: success createSchemaCustomization - 5.075s
11:02:55 AM: success  gatsby-source-wordpress  Comment - 0.806s - fetched 1
11:02:56 AM: success  gatsby-source-wordpress  User - 2.085s - fetched 1
11:02:57 AM: success  gatsby-source-wordpress  fetch root fields - 2.642s
11:02:57 AM: success  gatsby-source-wordpress  Menu - 2.830s - fetched 2
11:02:57 AM: success  gatsby-source-wordpress  ContentType - 2.884s - fetched 3
11:02:57 AM: success  gatsby-source-wordpress  Category - 2.914s - fetched 1
11:02:57 AM: success  gatsby-source-wordpress  MenuItem - 2.973s - fetched 10
11:02:57 AM: success  gatsby-source-wordpress  UserRole - 3.277s - fetched 0
11:02:57 AM: success  gatsby-source-wordpress  PostFormat - 3.282s - fetched 0
11:02:57 AM: success  gatsby-source-wordpress  Tag - 3.299s - fetched 0
11:02:57 AM: success  gatsby-source-wordpress  Taxonomy - 3.316s - fetched 3
11:02:57 AM: success  gatsby-source-wordpress  Post - 3.368s - fetched 2
11:02:57 AM: success  gatsby-source-wordpress  Page - 3.395s - fetched 6
11:02:59 AM: success  gatsby-source-wordpress  MediaItem - 1.148s - fetched 1
11:02:59 AM: success  gatsby-source-wordpress  creating nodes - 1.149s
11:02:59 AM: success  gatsby-source-wordpress  fetching nodes - 4.550s - 30 total
11:02:59 AM: success Downloading remote files - 0.400s - 1/1 2.50/s
11:02:59 AM: success Checking for changed pages - 0.000s
11:02:59 AM: success source and transform nodes - 4.942s
11:02:59 AM: success building schema - 0.674s
11:02:59 AM: info Total nodes: 149, SitePage nodes: 9 (use --verbose for breakdown)
11:02:59 AM: success createPages - 0.090s
11:02:59 AM: success Checking for changed pages - 0.000s
11:02:59 AM: success createPagesStatefully - 0.092s
11:03:00 AM: success update schema - 0.036s
11:03:00 AM: success onPreExtractQueries - 0.001s
11:03:01 AM: success extract queries from components - 1.046s
11:03:01 AM: success write out redirect data - 0.001s
11:03:01 AM: vips_value_hash: no case for NULL
11:03:01 AM:    type 64, gchararray
11:03:01 AM:    generic 53, GParamString
11:03:01 AM: vips_value_hash: no case for 0.000000
11:03:01 AM:    type 60, gdouble
11:03:01 AM:    generic 109, GParamDouble
11:03:01 AM: vips_value_hash: no case for FALSE
11:03:01 AM:    type 20, gboolean
11:03:01 AM:    generic 76, GParamBoolean
11:03:01 AM: vips_value_hash: no case for ((VipsAccess) VIPS_ACCESS_RANDOM)
11:03:01 AM:    type 82052320, VipsAccess
11:03:01 AM:    generic 80, GParamEnum
11:03:01 AM: vips_value_hash: no case for FALSE
11:03:01 AM:    type 20, gboolean
11:03:01 AM:    generic 76, GParamBoolean
11:03:02 AM: 
11:03:02 AM: ────────────────────────────────────────────────────────────────
11:03:02 AM:   "build.command" failed                                        
11:03:02 AM: ────────────────────────────────────────────────────────────────
11:03:02 AM: 
11:03:02 AM:   Error message
11:03:02 AM:   Command was killed with SIGSEGV (Segmentation fault): gatsby build
11:03:02 AM: 
11:03:02 AM:   Error location
11:03:02 AM:   In Build command from Netlify app:
11:03:02 AM:   gatsby build
11:03:02 AM: 
11:03:02 AM:   Resolved config
11:03:02 AM:   build:
11:03:02 AM:     command: gatsby build
11:03:02 AM:     commandOrigin: ui
11:03:02 AM:     publish: /opt/build/repo/public
11:03:02 AM: Caching artifacts
11:03:02 AM: Started saving node modules
11:03:02 AM: Finished saving node modules
11:03:02 AM: Started saving build plugins
11:03:02 AM: Finished saving build plugins
11:03:02 AM: Started saving pip cache
11:03:02 AM: Finished saving pip cache
11:03:02 AM: Started saving emacs cask dependencies
11:03:02 AM: Finished saving emacs cask dependencies
11:03:02 AM: Started saving maven dependencies
11:03:02 AM: Finished saving maven dependencies
11:03:02 AM: Started saving boot dependencies
11:03:02 AM: Finished saving boot dependencies
11:03:02 AM: Started saving go dependencies
11:03:02 AM: Finished saving go dependencies
11:03:02 AM: Build failed due to a user error: Build script returned non-zero exit code: 2
11:03:02 AM: Failing build: Failed to build site
11:03:02 AM: Failed during stage 'building site': Build script returned non-zero exit code: 2
11:03:02 AM: Finished processing build request in 1m16.889531876s

Here's a screenshot of my Netlify deploy settings:

@DarioRega I've added a screenshot of the settings in my post above. Not sure if you're looking for something specific. Since the Netlify support rep said it's not something on Netlify's end, I wasn't even checking Netlify deploy settings — RyanPinPB
– RyanPinPB, Commented Nov 25, 2020 at 21:00
Is this a hosted WordPress solution? Some hosts put rate limits on API calls, and if it works on your machine, it could be that you still work on a cached version from a.time where the rate limit wasn't reached. — ddprrt
– ddprrt, Commented Nov 25, 2020 at 21:05
@ddprrt yes it is a headless WordPress setup, but unlike some of the other answers I've found after googling this problem, mine was not a "time out error" due to too many requests or "rate limits". (at least I don't think). I think that a different error message mentioning "timeout" would have displayed if that was the case, but I am by no means an expert, and got lucky with my answer below. — RyanPinPB
– RyanPinPB, Commented Nov 26, 2020 at 0:34

RyanPinPB · Accepted Answer · 2020-11-26 00:32:33Z

1

So I've changed nothing in my project, or the gitHub page, but just setting up Netlify's CLI and using "netlify deploy" instead of the auto-deploy on git push setting solved it

Thanks @DarioRega for getting me to think about that.

So something between github and netlify might have caused the issue? I'm not sure

Using Netlify's CLI was way faster for deploying too (compared to pushing to github and triggering an auto-deploy)

answered Nov 26, 2020 at 0:32

RyanPinPB

738 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Sez · Accepted Answer · 2022-04-03 07:03:41Z

0

I'm a complete idiot.

I had set up a /etc/hosts definition for my remote Wordpress headless instance that I was using with Gatsby; and of course it worked just fine on my local.

And of course Netlify could not see the definition for the IP address that I had created in my laptop's /etc/hosts file.

So I was getting a timeout error from Netlify.

Creating an entry in my DNS (I use Google Domains at present) to point to the headless wordpress fixed the problem.

:facepalm:

answered Apr 3, 2022 at 7:03

Sez

1,31311 silver badges26 bronze badges

Collectives™ on Stack Overflow

Gatsby Failed Build on Netlify

2 Answers 2

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related