Error: write EPIPE
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 43.3k
- Forks
- 2.7k
- PR merge metrics
- No merged PRs in 30d
Description
What's going wrong?
When a worker is exit via signal SIGKILL, and autorestart=false, EPIPE error is happening
How could we reproduce this issue?
Locally, you can't, but on the server side, set a pod memory to 100mb and put a load above that
Supporting information
PM2 version : 5.3 (happend on 5.0 also),
PM2 Metrics installed
Error :
Docker:
Also tried with other keymetrics/pm2:16-stretch like version 18, version alpine, buster and other typees and the same is happening.
If i configure as autorestart=true, then app will keep crashing until the kubernetes healthcheck restart it with the same error
$ pm2 report
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The report names no source file, test, or entry point. Begin with the stated Docker/Kubernetes reproduction: limit the pod to 100 MB, exceed that memory, and observe SIGKILL with autorestart=false; done means the EPIPE error is handled without repeated crashes or unintended restarts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, javascript, kubernetes, nodejs
- Domain
- cli, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100