Port is occupied,pm2 Can still start
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?
Port is occupied,pm2 Can still start,And will not give an error message!Regardless of any errors in the project, PM2 can still start,
Windows operating system
$ pm2 report
PM2 | 2021-09-27T16:10:37: PM2 log: App name:nebula-api-platform id:13 disconnected
PM2 | 2021-09-27T16:10:37: PM2 log: App [nebula-api-platform:13] exited with code [1] via signal [SIGINT]
PM2 | 2021-09-27T16:10:37: PM2 log: pid=14920 msg=process killed
PM2 | 2021-09-27T16:10:37: PM2 log: Stopping app:nebula-api-platform id:14
PM2 | 2021-09-27T16:10:37: PM2 log: pid=13644 msg=process killed
PM2 | 2021-09-27T16:10:37: PM2 log: Stopping app:nebula-api-platform id:15
PM2 | 2021-09-27T16:10:37: PM2 log: App name:nebula-api-platform id:14 disconnected
PM2 | 2021-09-27T16:10:37: PM2 log: App [nebula-api-platform:14] exited with code [1] via signal [SIGINT]
PM2 | 2021-09-27T16:10:38: PM2 log: pid=13980 msg=process killed
PM2 | 2021-09-27T16:10:38: PM2 log: App name:nebula-api-platform id:15 disconnected
PM2 | 2021-09-27T16:10:38: PM2 log: Stopping app:nebula-api-platform id:16
PM2 | 2021-09-27T16:10:38: PM2 log: App [nebula-api-platform:15] exited with code [1] via signal [SIGINT]
PM2 | 2021-09-27T16:10:38: PM2 log: pid=5884 msg=process killed
PM2 | 2021-09-27T16:10:38: PM2 log: Stopping app:nebula-api-platform id:17
PM2 | 2021-09-27T16:10:38: PM2 log: App name:nebula-api-platform id:16 disconnected
PM2 | 2021-09-27T16:10:38: PM2 log: App [nebula-api-platform:16] exited with code [1] via signal [SIGINT]
PM2 | 2021-09-27T16:10:38: PM2 log: pid=6804 msg=process killed
PM2 | 2021-09-27T16:10:38: PM2 log: App name:nebula-api-platform id:17 disconnected
PM2 | 2021-09-27T16:10:38: PM2 log: App [nebula-api-platform:17] exited with code [1] via signal [SIGINT]
PM2 | 2021-09-27T16:10:38: PM2 log: pid=14700 msg=process killed
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
No source files or tests are named. Start by reproducing the occupied-port case on Windows and reviewing the pm2 report output; then locate the relevant process-start and error-handling entry points. Done means PM2 reports the startup failure instead of appearing to start despite the port conflict.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, 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