pm2-dev closing one instance closes all instances
Open
Nobody has claimed this yet.
S: Open for PR
SYS: CLI
T: Bug
- Dominant language
- JavaScript
- Stars
- 43.3k
- Forks
- 2.7k
- PR merge metrics
- No merged PRs in 30d
Description
What's going wrong?
When I'm running 2 pm2-dev commands in 2 different projects with 2 different configurations but I close one, the other one will be closed as well. I'm running both with a config file pm2dev.json.
How could we reproduce this issue?
Create 2 projects, run pm2-dev start pm2dev.json in each a new terminal. Press ctrl+c in one of both. See both closing.
Supporting information
==============================================================================
--- PM2 REPORT----------------------
===============================================================================
--- Daemon -------------------------------------------------
pm2d version : 2.7.2
node version : 8.9.4
node path : /usr/bin/pm2
argv : /usr/bin/node,/usr/lib/node_modules/pm2/lib/Daemon.js
argv0 : node
user : ubuntu
uid : 1000
gid : 1000
uptime : 4min
===============================================================================
--- CLI ----------------------------------------------------
local pm2 : 2.7.2
node version : 8.9.4
node path : /usr/bin/pm2
argv : /usr/bin/node,/usr/bin/pm2,report
argv0 : node
user : ubuntu
uid : 1000
gid : 1000
===============================================================================
--- System info --------------------------------------------
arch : x64
platform : linux
type : Linux
cpus : Intel(R) Core(TM) i7-4710HQ CPU @ 2.50GHz
cpus nb : 8
freemem : 1402961920
totalmem : 16727212032
home : /home/ubuntu
===============================================================================
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
Start by reproducing the issue with two projects, separate pm2dev.json files, and two pm2-dev terminals, then press Ctrl+C in one terminal. Trace the pm2-dev shutdown handling; done means stopping one instance leaves the other instance running.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100