Unitech / Unitech/pm2

EPIPE error

Open
#5,168 0 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
43.3k
Forks
2.7k
PR merge metrics
No merged PRs in 30d

Description

2021-09-07T12:23:16: PM2 error: Error: write EPIPE
at ChildProcess.target._send (internal/child_process.js:839:20)
at ChildProcess.target.send (internal/child_process.js:710:19)
at sendHelper (internal/cluster/utils.js:27:15)
at send (internal/cluster/master.js:357:10)
at internal/cluster/master.js:323:5
at done (internal/cluster/round_robin_handle.js:55:7)
at RoundRobinHandle.add (internal/cluster/round_robin_handle.js:64:12)
at queryServer (internal/cluster/master.js:317:10)
at Worker.onmessage (internal/cluster/master.js:257:5)
at ChildProcess.onInternalMessage (internal/cluster/utils.js:48:5)
events.js:377
throw er; // Unhandled 'error' event
^

Error: write EPIPE
at ChildProcess.target._send (internal/child_process.js:839:20)
at ChildProcess.target.send (internal/child_process.js:710:19)
at sendHelper (internal/cluster/utils.js:27:15)
at send (internal/cluster/master.js:357:10)
at Worker.disconnect (internal/cluster/master.js:363:3)
at Worker.destroy (internal/cluster/master.js:376:10)
at Worker. (/app/.heroku/node/lib/node_modules/pm2/lib/God.js:258:30)
at Object.onceWrapper (events.js:520:26)
at Worker.emit (events.js:400:28)
at Worker.emit (domain.js:470:12)
Emitted 'error' event on Worker instance at:
at ChildProcess. (internal/cluster/worker.js:30:12)
at ChildProcess.emit (events.js:400:28)
at ChildProcess.emit (domain.js:470:12)
at internal/child_process.js:843:39
at processTicksAndRejections (internal/process/task_queues.js:77:11) {
errno: -32,
code: 'EPIPE',
syscall: 'write'
}

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Use the reported stack trace as the starting point, then inspect pm2/lib/God.js around line 258 and the Node cluster worker-disconnect path on the reported Heroku setup. Done means the EPIPE failure is explained and addressed, with regression coverage for the affected worker lifecycle.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js
Domain
cli, devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.