PM2 is showing www and npm errored
Open
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?
How could we reproduce this issue?
Supporting information
$ pm2 report
--- PM2 report ----------------------------------------------------------------
Date : Tue Mar 09 2021 04:57:27 GMT+0000 (Coordinated Universal Time)
===============================================================================
--- Daemon -------------------------------------------------
pm2d version : 4.5.5
node version : 10.23.1
node path : not found
argv : /usr/bin/node,/usr/lib/node_modules/pm2/lib/Daemon.js
argv0 : node
user : root
uid : 0
gid : 0
uptime : 6767min
===============================================================================
--- CLI ----------------------------------------------------
local pm2 : 4.5.5
node version : 10.23.1
node path : not found
argv : /usr/bin/node,/usr/bin/pm2,report
argv0 : node
user : root
uid : 0
gid : 0
===============================================================================
--- System info --------------------------------------------
arch : x64
platform : linux
type : Linux
cpus : Intel(R) Xeon(R) CPU E5-2676 v3 @ 2.40GHz
cpus nb : 2
freemem : 600387584
totalmem : 4124876800
home : /home/ubuntu
===============================================================================
--- PM2 list -----------------------------------------------
┌─────┬────────┬─────────────┬─────────┬─────────┬──────────┬────────┬──────┬───────────┬──────────┬──────────┬──────────┬──────────┐
│ id │ name │ namespace │ version │ mode │ pid │ uptime │ ↺ │ status │ cpu │ mem │ user │ watching │
├─────┼────────┼─────────────┼─────────┼─────────┼──────────┼────────┼──────┼───────────┼──────────┼──────────┼──────────┼──────────┤
│ 0 │ app │ default │ 1.0.0 │ fork │ 0 │ 0 │ 15 │ stopped │ 0% │ 0b │ root │ disabled │
│ 4 │ npm │ default │ N/A │ fork │ 0 │ 0 │ 15 │ errored │ 0% │ 0b │ root │ disabled │
│ 2 │ www │ default │ 1.0.0 │ fork │ 27964 │ 17h │ 9 │ online │ 0.2% │ 85.3mb │ root │ disabled │
│ 3 │ www │ default │ 1.0.0 │ fork │ N/A │ 0 │ 0 │ errored │ 0% │ 0b │ root │ disabled │
└─────┴────────┴─────────────┴─────────┴─────────┴──────────┴────────┴──────┴───────────┴──────────┴──────────┴──────────┴──────────┘
===============================================================================
--- Daemon logs --------------------------------------------
/home/ubuntu/.pm2/pm2.log last 20 lines:
PM2 | 2021-03-08T12:37:17: PM2 log: App [www:6] starting in -fork mode-
PM2 | 2021-03-08T12:37:17: PM2 log: App [www:6] online
PM2 | 2021-03-08T12:37:18: PM2 log: App [www:6] exited with code [1] via signal [SIGINT]
PM2 | 2021-03-08T12:37:18: PM2 log: App [www:6] starting in -fork mode-
PM2 | 2021-03-08T12:37:18: PM2 log: App [www:6] online
PM2 | 2021-03-08T12:37:19: PM2 log: App [www:6] exited with code [1] via signal [SIGINT]
PM2 | 2021-03-08T12:37:19: PM2 log: App [www:6] starting in -fork mode-
PM2 | 2021-03-08T12:37:19: PM2 log: App [www:6] online
PM2 | 2021-03-08T12:37:20: PM2 log: App [www:6] exited with code [1] via signal [SIGINT]
PM2 | 2021-03-08T12:37:20: PM2 log: App [www:6] starting in -fork mode-
PM2 | 2021-03-08T12:37:20: PM2 log: App [www:6] online
PM2 | 2021-03-08T12:37:21: PM2 log: App [www:6] exited with code [1] via signal [SIGINT]
PM2 | 2021-03-08T12:37:21: PM2 log: App [www:6] starting in -fork mode-
PM2 | 2021-03-08T12:37:21: PM2 log: App [www:6] online
PM2 | 2021-03-08T12:37:21: PM2 log: Stopping app:www id:1
PM2 | 2021-03-08T12:37:21: PM2 log: Stopping app:www id:6
PM2 | 2021-03-08T12:37:21: PM2 log: App [www:1] exited with code [0] via signal [SIGINT]
PM2 | 2021-03-08T12:37:21: PM2 log: App [www:6] exited with code [0] via signal [SIGINT]
PM2 | 2021-03-08T12:37:21: PM2 log: pid=26883 msg=process killed
PM2 | 2021-03-08T12:37:21: PM2 log: pid=16488 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
Start by reproducing the reported PM2 state and collect the output of pm2 report, then compare it with the daemon log entries shown in the issue. The report does not identify a code entry point or reproduction steps, so completion would require isolating why the www and npm processes become errored and verifying the behavior after the relevant fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100