Unitech / Unitech/pm2

Ram and CPU are not shown

Open
#5,671 1 comment 0 reactions 0 assignees View on GitHub

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?

If I send pm2 ls or pm2 describe the cpu and memory are not shown

How could we reproduce this issue?

pm2 ls

Supporting information

--- Daemon logs --------------------------------------------
/root/.pm2/pm2.log last 20 lines:
PM2        | 2023-09-06T14:56:03: PM2 log: App [biscotto:31] starting in -fork mode-
PM2        | 2023-09-06T14:56:03: PM2 log: App [biscotto:31] online
PM2        | 2023-09-06T14:56:04: PM2 error: Error caught while calling pidusage
PM2        | 2023-09-06T14:56:04: PM2 error: TypeError: One of the pids provided is invalid
PM2        | 2023-09-06T14:56:05: PM2 error: Error caught while calling pidusage
PM2        | 2023-09-06T14:56:05: PM2 error: TypeError: One of the pids provided is invalid
PM2        | 2023-09-06T14:56:05: PM2 error: Error caught while calling pidusage
PM2        | 2023-09-06T14:56:05: PM2 error: TypeError: One of the pids provided is invalid
PM2        | 2023-09-06T14:56:06: PM2 error: Error caught while calling pidusage
PM2        | 2023-09-06T14:56:06: PM2 error: TypeError: One of the pids provided is invalid
PM2        | 2023-09-06T14:56:06: PM2 log: App [biscotto2:36] exited with code [0] via signal [SIGINT]
PM2        | 2023-09-06T14:56:06: PM2 log: App [biscotto2:36] starting in -fork mode-
PM2        | 2023-09-06T14:56:06: PM2 log: App [biscotto2:36] online
PM2        | 2023-09-06T14:56:06: PM2 log: App [biscotto:31] exited with code [0] via signal [SIGINT]
PM2        | 2023-09-06T14:56:06: PM2 log: App [biscotto:31] starting in -fork mode-
PM2        | 2023-09-06T14:56:06: PM2 log: App [biscotto:31] online
PM2        | 2023-09-06T14:56:07: PM2 error: Error caught while calling pidusage
PM2        | 2023-09-06T14:56:07: PM2 error: TypeError: One of the pids provided is invalid
PM2        | 2023-09-06T14:56:07: PM2 error: Error caught while calling pidusage
PM2        | 2023-09-06T14:56:07: PM2 error: TypeError: One of the pids provided is invalid

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue with pm2 ls and pm2 describe <process>, then trace the CPU and memory collection path associated with the logged pidusage errors. Use the daemon logs as the initial diagnostic evidence; done means both commands show CPU and memory values without repeated invalid-PID errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, nodejs
Domain
cli, observability
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.