Gatsby v4 works locally, but timed out on Netlify

Support
,
22

I tried with v4.1.3 but it did not work for me either :frowning: Same EPIPE error

I was on v4.2.0 when I upgraded to v4 in November and everything was fine until mid-Feb. More inclined to think something changed on Netlify’s side

23

What about trying an even lower number in GATSBY_CONCURRENT_DOWNLOAD ?
You could also try to search for big files in your project, I’ve seen issues about this too.

2 Likes
24

GATSBY_CONCURRENT did not work.
Found a fix here.
TLDR: moved back from 4.9.3 to “gatsby”: “4.6.2”

25

Thanks so much for letting us know!

27

I tried adjusting GATSBY_CONCURRENT_DOWNLOAD and it seemed to get one deploy to work. But then Ive tried over 10 more since then and each one has had the EPIPE error. Is this a Netlify plugin issue? Can the Netlify team give us some advice on this? I have found alot of people in different forums are getting this error on Netlify.

1 Like
28

I just had the same error minutes ago, but my deploy worked when I set GATSBY_CONCURRENT_DOWNLOAD to 8

2 Likes
29

I just had the error again. The only thing that changed was some React app coded since last successful deploy, not NPM, not Gatsby Version, not static content. The main variable I have found is what time of day I’m doing it. Off hours seem to work best. I am on free plan. I think we are all trying changing GATSBY_CONCURRENT_DOWNLOAD, Gatsby version, amount of static content, and keep trying until it succeeds while behind the scenes it is probably just the Netlify build env being throttled during heavy build traffic time of day. I’ll let you know, I’m going for a walk then I’ll try again. If that doesnt work, I’ll try again in the evening (West Coast).

Update 1: Waited about an hour, (maybe about 4PM west coast) hit “try again”, failed again.

Update 2: SUCCESS! I just hit “try again” at about 11PM west coast time and it worked! I did not change anything. Netlify should at least respond here if its the official policy to throttle free (or low) tiers at peak traffic OR they don’t realize its happening and need to look at their configs, etc.

30

Hey folks!

Thanks for following up here. “Off hours” is hard to define, as working hours on one side of the globe and off hours on the other. In short, you might be getting 6 GB RAM sometimes and 3 GB the other times. When you get 6GB, your build works, and fails the other times.

I recognize how this is not an optimal experience for you, and I think this support guide might offer some good insights here about using resources when building:

More specifically, our suggestions for this specific Gatsby V4 situation have been the following:

  1. Try using Gatsby <= 4.7
  2. Try disabling AVIF and WEBP in gatsby.config.js
  3. Try reducing the size of the source images
  4. If nothing works, deploy via CLI
32

Hello everyone. I have good news! It turns out it was not a memory issue after all, but was a bug in Gatsby. It doesn’t appear when building locally because most people are using multi-core machines and the bug only appears when using a single worker, which builds do on Netlify. We worked with the Gatsby team to release a fix which went out today. If you update your site to gatsby@4.13.1 then it should fix the problem.

2 Likes
Automatically trigger a build when a build fails
33

FWIW. I found a link reporting that this error has been resolved with version of 4.13. I tried updating to:

    "gatsby": "^4.13.1",
    "gatsby-cli": "^4.13.0",

I had 5 straight failures over the last few days using older versions of Gatsby. I tried this and got past the EPIPE error on the first try. Posting here for anyone who might be following this issue.

1 Like
34

thanks for confirming that, dean. appreciated!