pm2 not starting node app
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 43.3k
- Forks
- 2.7k
- PR merge metrics
- No merged PRs in 30d
Description
--- PM2 report ----------------------------------------------------------------
Date : Fri Feb 18 2022 07:00:52 GMT+0000 (Coordinated Universal Time)
===============================================================================
--- Daemon --------------------------------------------------------------------
pm2d version : 5.2.0
node version : 10.19.0
node path : /usr/local/bin/pm2
argv : /usr/bin/node,/usr/local/lib/node_modules/pm2/lib/Daemon.js
argv0 : node
user : root
uid : 0
gid : 0
uptime : 52min
===============================================================================
--- CLI -----------------------------------------------------------------------
local pm2 : 5.2.0
node version : 10.19.0
node path : /usr/local/bin/pm2
argv : /usr/bin/node,/usr/local/bin/pm2,report
argv0 : node
user : root
uid : 0
gid : 0
===============================================================================
--- System info ---------------------------------------------------------------
arch : x64
platform : linux
type : Linux
cpus : DO-Regular
cpus nb : 1
freemem : 70852608
totalmem : 1024368640
home : /root
===============================================================================
--- PM2 list ------------------------------------------------------------------
┌─────┬────────┬─────────────┬─────────┬─────────┬──────────┬────────┬──────┬───────────┬──────────┬──────────┬──────────┬──────────┐
│ id │ name │ namespace │ version │ mode │ pid │ uptime │ ↺ │ status │ cpu │ mem │ user │ watching │
├─────┼────────┼─────────────┼─────────┼─────────┼──────────┼────────┼──────┼───────────┼──────────┼──────────┼──────────┼──────────┤
│ 0 │ app │ default │ 1.0.0 │ fork │ 5635 │ 5m │ 7 │ online │ 0.2% │ 73.9mb │ root │ disabled │
└─────┴────────┴─────────────┴─────────┴─────────┴──────────┴────────┴──────┴───────────┴──────────┴──────────┴──────────┴──────────┘
===============================================================================
--- Daemon logs ---------------------------------------------------------------
/root/.pm2/pm2.log last 20 lines:
PM2 | 2022-02-18T06:13:14: PM2 log: Stopping app:app id:0
PM2 | 2022-02-18T06:13:14: PM2 log: App [app:0] exited with code [0] via signal [SIGINT]
PM2 | 2022-02-18T06:13:14: PM2 log: pid=4596 msg=process killed
PM2 | 2022-02-18T06:13:14: PM2 log: App [app:0] starting in -fork mode-
PM2 | 2022-02-18T06:13:14: PM2 log: App [app:0] online
PM2 | 2022-02-18T06:53:23: PM2 log: Stopping app:app id:0
PM2 | 2022-02-18T06:53:23: PM2 log: App [app:0] exited with code [0] via signal [SIGINT]
PM2 | 2022-02-18T06:53:23: PM2 log: pid=4616 msg=process killed
PM2 | 2022-02-18T06:53:23: PM2 log: App [app:0] starting in -fork mode-
PM2 | 2022-02-18T06:53:23: PM2 log: App [app:0] online
PM2 | 2022-02-18T06:53:43: PM2 log: Stopping app:app id:0
PM2 | 2022-02-18T06:53:43: PM2 log: App [app:0] exited with code [0] via signal [SIGINT]
PM2 | 2022-02-18T06:53:43: PM2 log: pid=5574 msg=process killed
PM2 | 2022-02-18T06:53:43: PM2 log: App [app:0] starting in -fork mode-
PM2 | 2022-02-18T06:53:43: PM2 log: App [app:0] online
PM2 | 2022-02-18T06:55:05: PM2 log: Stopping app:app id:0
PM2 | 2022-02-18T06:55:05: PM2 log: App [app:0] exited with code [0] via signal [SIGINT]
PM2 | 2022-02-18T06:55:05: PM2 log: pid=5601 msg=process killed
PM2 | 2022-02-18T06:55:05: PM2 log: App [app:0] starting in -fork mode-
PM2 | 2022-02-18T06:55:05: PM2 log: App [app:0] online
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 reported PM2 5.2.0 behavior with Node 10.19.0 on Linux, then inspect the supplied PM2 report and daemon logs alongside the app's startup output. Done means identifying why the app is repeatedly stopped and restarted and confirming the behavior is resolved or clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, linux, node.js
- Domain
- cli, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100