PM2 autodump:false is not working
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 43.3k
- Forks
- 2.7k
- PR merge metrics
- No merged PRs in 30d
Description
v5.1.2, ubuntu 20.04
Even though we have autodump set to false, killing PM2 still dumps the processlist:
PM2 log: pm2 has been killed by signal, dumping process list before exit...
Is this expected? Is there no way to completely disable this feature?
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
Reproduce the reported behavior using PM2 v5.1.2 on Ubuntu 20.04, with autodump set to false, and observe the shutdown log. Trace the autodump configuration and the signal-handling path to determine why the process list is saved; done means the documented setting reliably prevents the dump or the limitation is clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- cli, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100