Error: UNHANDLED REJECTION write EPIPE

[jack0wsky]

Description

Hello everyone!

I'm getting this error almost every time I shut down local server.

error UNHANDLED REJECTION write EPIPE


  Error: write EPIPE
  
  - child_process.js:806 ChildProcess.target._send
    internal/child_process.js:806:20
  
  - child_process.js:676 ChildProcess.send
    internal/child_process.js:676:19
  
  - develop.ts:130 ControllableScript.stop
    [ap-investment]/[gatsby]/src/commands/develop.ts:130:20
  
  - develop.ts:500 shutdownServices
    [ap-investment]/[gatsby]/src/commands/develop.ts:500:28
  
  - develop.ts:442 process.<anonymous>
    [ap-investment]/[gatsby]/src/commands/develop.ts:442:11

I've tried multiple times

gatsby clean
remove /node_modules and package-lock.json
npm install

but it solves problem only for some time. Don't know if it is related but when gatsby develop and dev server is running, after some saves, when I click Command + S to save changes, hot reload doesn't work and project isn't re-rendering.

Steps to reproduce

Expected result

Shuting down dev server without errors

Actual result

Throwing error mentioned above and hot reload not working.

Environment

  System:
    OS: macOS 10.15.7
    CPU: (4) x64 Intel(R) Core(TM) i5-7360U CPU @ 2.30GHz
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 12.14.0 - /usr/local/bin/node
    Yarn: 1.22.4 - /usr/local/bin/yarn
    npm: 6.14.8 - /usr/local/bin/npm
  Languages:
    Python: 2.7.16 - /usr/bin/python
  Browsers:
    Chrome: 86.0.4240.193
    Firefox: 82.0.3
    Safari: 14.0
  npmPackages:
    gatsby: ^2.25.3 => 2.25.4 
    gatsby-alias-imports: ^1.0.6 => 1.0.6 
    gatsby-image: ^2.4.21 => 2.4.21 
    gatsby-plugin-postcss: ^3.0.4 => 3.0.4 
    gatsby-plugin-sass: ^2.4.2 => 2.4.2 
    gatsby-plugin-sharp: ^2.7.1 => 2.7.1 
    gatsby-plugin-tinacms: ^0.32.0 => 0.32.0 
    gatsby-source-filesystem: ^2.4.2 => 2.4.2 
    gatsby-tinacms-git: ^0.32.0 => 0.32.0 
    gatsby-tinacms-json: ^0.32.0 => 0.32.0 
    gatsby-tinacms-remark: ^0.32.1 => 0.32.1 
    gatsby-transformer-remark: ^2.9.2 => 2.9.2 
    gatsby-transformer-sharp: ^2.5.21 => 2.5.21 
  npmGlobalPackages:
    gatsby-cli: 2.12.117
    gatsby: 2.25.3

[github-actions]

Hiya!

This issue has gone quiet. Spooky quiet. 👻

We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 20 days since the last update here.
If we missed this issue or if you want to keep it open, please reply here.
As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

Thanks for being a part of the Gatsby community! 💪💜

[jamo]

@jack0wsky try updating to a more recent version of gatsby (as of writing this we are at 2.28.0).
Not fully sure if the underlying issue was fully fixed but I haven't run into this for a while with a fresh gatsby version.

[github-actions]

Hiya!

This issue has gone quiet. Spooky quiet. 👻

We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 20 days since the last update here.
If we missed this issue or if you want to keep it open, please reply here.
As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request. Check out gatsby.dev/contribute for more information about opening PRs, triaging issues, and contributing!

Thanks for being a part of the Gatsby community! 💪💜

[hronchetti]

@jack0wsky try updating to a more recent version of gatsby (as of writing this we are at 2.28.0).
Not fully sure if the underlying issue was fully fixed but I haven't run into this for a while with a fresh gatsby version.

Worked for me!

[aravind-eng]

We are still seeing this issue with the latest gatsby

ERROR

UNHANDLED REJECTION write EPIPE

Error: write EPIPE

• child_process.js:806 ChildProcess.target._send
  internal/child_process.js:806:20

• child_process.js:676 ChildProcess.send
  internal/child_process.js:676:19

• develop.ts:130 ControllableScript.stop
  [bigfig]/[gatsby]/src/commands/develop.ts:130:20

• develop.ts:500 shutdownServices
  [bigfig]/[gatsby]/src/commands/develop.ts:500:28

• develop.ts:442 process.
  [bigfig]/[gatsby]/src/commands/develop.ts:442:11

npmPackages:
gatsby: ^2.26.1 => 2.26.1
gatsby-image: ^2.5.0 => 2.5.0
gatsby-plugin-manifest: ^2.6.1 => 2.6.1
gatsby-plugin-offline: ^3.4.0 => 3.4.0
gatsby-plugin-react-helmet: ^3.4.0 => 3.4.0
gatsby-plugin-sharp: ^2.8.0 => 2.8.0
gatsby-plugin-styled-components: ^3.8.0 => 3.8.0
gatsby-source-filesystem: ^2.5.0 => 2.5.0
gatsby-transformer-sharp: ^2.6.0 => 2.6.0
npmGlobalPackages:
gatsby-cli: 2.7.29

[karlhorky]

Yes, this error also happens for me every time I shut down using ctrl-C on macOS.

Demo repo:

https://github.com/upleveled/gatsby-serverside-auth0/tree/main/packages/gatsby-website

[sol-idsnake]

Same thing happens on Win10:

    "gatsby": "^2.31.1",
    "gatsby-image": "^2.10.0",
    "gatsby-plugin-google-analytics": "^2.10.0",
    "gatsby-plugin-react-helmet": "^3.9.0",
    "gatsby-plugin-sass": "^3.1.0",
    "gatsby-plugin-sharp": "^2.13.4",
    "gatsby-plugin-sitemap": "^2.11.0",
    "gatsby-source-filesystem": "^2.10.0",
    "gatsby-source-wordpress-experimental": "^7.0.3",
    "gatsby-transformer-sharp": "^2.11.0",
    "react": "^17.0.1",
    "react-dom": "^17.0.1",
    "react-helmet": "^6.1.0",

"develop": "gatsby develop -H=0.0.0.0",

Node: v14.15.4
npm: 6.14.10