Error caught while calling pid usage
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 43.3k
- Forks
- 2.7k
- PR merge metrics
- No merged PRs in 30d
Description
--- Daemon logs --------------------------------------------
/home/tomas/.pm2/pm2.log last 20 lines:
PM2 | 2026-07-19T15:46:23: PM2 error: Error caught while calling pidusage
PM2 | 2026-07-19T15:46:23: PM2 error: TypeError: One of the pids provided is invalid
PM2 | 2026-07-19T15:46:32: PM2 error: Error caught while calling pidusage
PM2 | 2026-07-19T15:46:32: PM2 error: TypeError: One of the pids provided is invalid
PM2 | 2026-07-19T15:46:43: PM2 error: Error caught while calling pidusage
PM2 | 2026-07-19T15:46:43: PM2 error: TypeError: One of the pids provided is invalid
PM2 | 2026-07-19T15:47:13: PM2 error: Error caught while calling pidusage
PM2 | 2026-07-19T15:47:13: PM2 error: TypeError: One of the pids provided is invalid
PM2 | 2026-07-19T15:47:43: PM2 error: Error caught while calling pidusage
PM2 | 2026-07-19T15:47:43: PM2 error: TypeError: One of the pids provided is invalid
PM2 | 2026-07-19T15:47:53: PM2 error: Error caught while calling pidusage
PM2 | 2026-07-19T15:47:53: PM2 error: TypeError: One of the pids provided is invalid
PM2 | 2026-07-19T15:47:53: PM2 error: Error caught while calling pidusage
PM2 | 2026-07-19T15:47:53: PM2 error: TypeError: One of the pids provided is invalid
PM2 | 2026-07-19T15:48:09: PM2 error: Error caught while calling pidusage
PM2 | 2026-07-19T15:48:09: PM2 error: TypeError: One of the pids provided is invalid
PM2 | 2026-07-19T15:48:13: PM2 error: Error caught while calling pidusage
PM2 | 2026-07-19T15:48:13: PM2 error: TypeError: One of the pids provided is invalid
PM2 | 2026-07-19T15:48:19: PM2 error: Error caught while calling pidusage
PM2 | 2026-07-19T15:48:19: PM2 error: TypeError: One of the pids provided is invalid
Please copy/paste the above report in your issue on https://github.com/Unitech/pm2/issues
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 file or test is named. Start by reproducing the daemon's repeated pidusage error and tracing PM2's process-usage entry point to determine which PID is invalid. Done means identifying the triggering condition, preventing the repeated error, and adding coverage for the failure case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs
- Domain
- cli, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100