PM2 Process delete automatically on exit from terminal
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 43.3k
- Forks
- 2.7k
- PR merge metrics
- No merged PRs in 30d
Description
PM2 | 2023-01-19T01:59:20: PM2 log: SIGTERM timeout : 1600
PM2 | 2023-01-19T01:59:20: PM2 log: ===============================================================================
PM2 | 2023-01-19T02:00:00: PM2 log: App [creditRepair:0] starting in -fork mode-
PM2 | 2023-01-19T02:00:00: PM2 log: App [creditRepair:0] online
PM2 | 2023-01-19T02:04:35: PM2 log: ===============================================================================
PM2 | 2023-01-19T02:04:35: PM2 log: --- New PM2 Daemon started ----------------------------------------------------
PM2 | 2023-01-19T02:04:35: PM2 log: Time : Thu Jan 19 2023 02:04:35 GMT-0500 (Eastern Standard Time)
PM2 | 2023-01-19T02:04:35: PM2 log: PM2 version : 5.2.2
PM2 | 2023-01-19T02:04:35: PM2 log: Node.js version : 14.21.2
PM2 | 2023-01-19T02:04:35: PM2 log: Current arch : x64
PM2 | 2023-01-19T02:04:35: PM2 log: PM2 home : /home/atifdev/.pm2
PM2 | 2023-01-19T02:04:35: PM2 log: PM2 PID file : /home/atifdev/.pm2/pm2.pid
PM2 | 2023-01-19T02:04:35: PM2 log: RPC socket file : /home/atifdev/.pm2/rpc.sock
PM2 | 2023-01-19T02:04:35: PM2 log: BUS socket file : /home/atifdev/.pm2/pub.sock
PM2 | 2023-01-19T02:04:35: PM2 log: Application log path : /home/atifdev/.pm2/logs
PM2 | 2023-01-19T02:04:35: PM2 log: Worker Interval : 30000
PM2 | 2023-01-19T02:04:35: PM2 log: Process dump file : /home/atifdev/.pm2/dump.pm2
PM2 | 2023-01-19T02:04:35: PM2 log: Concurrent actions : 2
PM2 | 2023-01-19T02:04:35: PM2 log: SIGTERM timeout : 1600
PM2 | 2023-01-19T02:04:35: PM2 log: ===============================================================================
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 by reproducing the behavior with PM2 5.2.2 and Node.js 14.21.2, using the provided daemon and SIGTERM logs as clues. Trace what happens when the terminal exits and define done as keeping the process managed as expected, with a regression test for that exit scenario.
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