Shyam
December 1, 2023, 12:55pm
1
Hello, my netlify site name is timely-sable-93a263.netlify.app
The build fails with the below error
failed Validating Rendering Engines - 3.298s
4:46:32 PM: error Built Rendering Engines failed validation.
4:46:32 PM: Please open an issue with a reproduction at Sign in to GitHub Β· GitHub for more help.
4:46:32 PM:
4:46:32 PM:
4:46:32 PM: Error: Worker exited before finishing task
4:46:32 PM:
4:46:32 PM: - index.js:205 ChildProcess.
4:46:32 PM: [repo]/[gatsby-worker]/dist/index.js:205:41
4:46:32 PM:
4:46:32 PM:
4:46:32 PM: not finished Running gatsby.IMAGE_CDN jobs - 2155.590s
4:46:33 PM: β
4:46:33 PM: βbuild.commandβ failed
4:46:33 PM: ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
4:46:33 PM: β
4:46:33 PM: Error message
4:46:33 PM: Command failed with exit code 1: gatsby build (Search results for '"non-zero exit code: 1"' - Netlify Support Forums )
4:46:33 PM: β
4:46:33 PM: Error location
4:46:33 PM: In Build command from Netlify app:
4:46:33 PM: gatsby build
4:46:33 PM: β
4:46:33 PM: Resolved config
4:46:33 PM: build:
4:46:33 PM: base: /opt/build/repo
4:46:33 PM: command: gatsby build
4:46:33 PM: commandOrigin: ui
4:46:33 PM: publish: /opt/build/repo/public
4:46:33 PM: publishOrigin: ui
4:46:34 PM: Failed during stage βbuilding siteβ: Build script returned non-zero exit code: 2
4:46:34 PM: Build failed due to a user error: Build script returned non-zero exit code: 2
4:46:34 PM: Failing build: Failed to build site
Have tried all the steps mentioned in the article but no help Unexpected Rendering Engines validation failure (Gatsby v4) Β· Issue #34293 Β· gatsbyjs/gatsby Β· GitHub
Any other directions would be helpful. Below is the full build log
Thanks in Advance!
If youβre using image CDN, can you try not using it to see if it helps?
1 Like
Shyam
December 4, 2023, 1:27pm
4
Hello Hrishikesh!
Thank you for your suggestion, FYI I have not enabled image_cdn ,
Nevertheless, I have tried to set the configuration in netlify.toml file with below snippet
[build.environment]
NETLIFY_IMAGE_CDN = βfalseβ
No luck yet, still the same error. Do you know how to confirm if the configuration is set properly? Is there any way to check if the netlify.toml file is read properly?
I have added it in the root folder as mentioned in
Shyam
December 6, 2023, 6:01am
5
This is also reported as open issue in github
opened 01:05AM - 22 Aug 23 UTC
type: bug
status: triage needed
### Preliminary Checks
- [X] This issue is not a duplicate. Before opening a ne⦠w issue, please search existing issues: https://github.com/gatsbyjs/gatsby/issues
- [X] This issue is not a question, feature request, RFC, or anything other than a bug report directly related to Gatsby. Please post those things in GitHub Discussions: https://github.com/gatsbyjs/gatsby/discussions
### Description
Hello,
I am in the process of bringing my Gatsby v3 site up to v5, and unfortunately I am running into some issues when executing `gatsby build`. After a `gatsby clean` and `gatsby build --verbose`, I receive the following nondescript error:
```
failed Validating Rendering Engines - 3.372s
ERROR #98001 ENGINE.VALIDATION
Built Rendering Engines failed validation.
Please open an issue with a reproduction at https://gatsby.dev/new-issue for more help.
Error: Worker exited before finishing task
- index.js:205 ChildProcess.<anonymous>
[daniely.im-gatsby]/[gatsby-worker]/dist/index.js:205:41
not finished Running gatsby.IMAGE_CDN jobs - 75.170s
```
My repo works without issue when running `gatsby develop`.
### Reproduction Link
(In progress)
### Steps to Reproduce
1. `gatsby build --verbose`
2. See error
### Expected Result
I expected a successful build
### Actual Result
Build fails with `ERROR #98001 ENGINE.VALIDATION`
### Environment
```shell
System:
OS: macOS 12.6.3
CPU: (8) x64 Intel(R) Core(TM) i7-6920HQ CPU @ 2.90GHz
Shell: 5.8.1 - /bin/zsh
Binaries:
Node: 18.15.0 - ~/.nvm/versions/node/v18.15.0/bin/node
Yarn: 1.22.5 - ~/.yarn/bin/yarn
npm: 9.5.0 - ~/.nvm/versions/node/v18.15.0/bin/npm
Browsers:
Chrome: 116.0.5845.96
Firefox: 115.0.2
Safari: 15.6.1
npmPackages:
gatsby: ^5.11.0 => 5.11.0
gatsby-core-utils: ^4.11.0 => 4.11.0
gatsby-image: ^3.1.0 => 3.1.0
gatsby-plugin-fontawesome-css: ^1.2.0 => 1.2.0
gatsby-plugin-gtag: ^1.0.13 => 1.0.13
gatsby-plugin-offline: ^6.11.0 => 6.11.0
gatsby-plugin-postcss: ^6.11.0 => 6.11.0
gatsby-plugin-react-helmet: ^6.11.0 => 6.11.0
gatsby-plugin-react-svg: ^3.3.0 => 3.3.0
gatsby-plugin-sharp: ^5.11.0 => 5.11.0
gatsby-plugin-sitemap: ^6.11.0 => 6.11.0
gatsby-plugin-styled-components: ^6.11.0 => 6.11.0
gatsby-plugin-typescript: ^5.11.0 => 5.11.0
gatsby-plugin-web-font-loader: ^1.0.4 => 1.0.4
gatsby-source-filesystem: ^5.11.0 => 5.11.0
gatsby-source-wordpress: ^7.11.0 => 7.11.0
gatsby-transformer-sharp: ^5.11.0 => 5.11.0
npmGlobalPackages:
gatsby-core-utils: 4.8.0
gatsby: 5.8.0
```
### Config Flags
None
tried all suggestion of downgrading the gatsby-source-wordpress plugin to various version mentioned in the issue. No luck!
Hey there,
Thanks for following up, and apologies again for the hassle! Are you seeing this error in local builds as well? If so, for the next steps, youβll want to:
In your node_modules
directory, navigate to: node_modules/gatsby/dist/utils/validate-engines/index.js
.
Change silent: true
to silent: false
.
Re-run the build
This wonβt resolve the build errors but should output a more actionable error message that points to the root cause of the failed builds. Please reach out with any questions!
Shyam
December 11, 2023, 3:16pm
8
Hello @marcus.little ,
We have cleared the webpages from the test site and started setting the pages one by one, (built the site from scratch) thus we eliminated the issue. So this can be closed. Thank you for the followup.
Thatβs great to hear - thanks for following up and confirming!