Current process list is not synchronized with saved list. App Server npm differs. Type 'pm2 save' to synchronize
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 : Mon Mar 06 2023 23:49:37 GMT-0800 (GMT-08:00)
--- Daemon -------------------------------------------------
pm2d version : 5.2.2
node version : 12.22.12
node path : /usr/bin/pm2
argv : /usr/bin/node,/usr/lib/node_modules/pm2/lib/Daemon.js
argv0 : node
gid : 2000
uptime : 35515min
--- CLI ----------------------------------------------------
local pm2 : 5.2.2
node version : 12.22.12
node path : /usr/bin/pm2
argv : /usr/bin/node,/usr/bin/pm2,report
argv0 : node
gid : 2000
--- System info --------------------------------------------
arch : x64
platform : linux
type : Linux
cpus : Intel(R) Xeon(R) Platinum 8168 CPU @ 2.70GHz
cpus nb : 4
freemem : 2414460928
totalmem : 6198206464
home : /users/
--- PM2 list -----------------------------------------------
┌─────┬───────────┬─────────────┬─────────┬─────────┬──────────┬────────┬──────┬───────────┬──────────┬──────────┬──────────┬──────────┐
│ id │ name │ namespace │ version │ mode │ pid │ uptime │ ↺ │ status │ cpu │ mem │ user │ watching │
└─────┴───────────┴─────────────┴─────────┴─────────┴──────────┴────────┴──────┴───────────┴──────────┴──────────┴──────────┴──────────┘
[PM2][WARN] Current process list is not synchronized with saved list. App Server npm differs. Type 'pm2 save' to synchronize.
--- Daemon logs --------------------------------------------
/users/mallikav/.pm2/pm2.log last 20 lines:
PM2 | 2023-02-10T05:55:59: PM2 log: Stopping app:npm id:1
PM2 | 2023-02-10T05:55:59: PM2 log: App [npm:1] exited with code [0] via signal [SIGINT]
PM2 | 2023-02-10T05:55:59: PM2 log: pid=13535 msg=process killed
PM2 | 2023-02-10T05:55:59: PM2 log: Exited peacefully
PM2 | 2023-02-10T07:53:38: PM2 log: ===============================================================================
PM2 | 2023-02-10T07:53:38: PM2 log: --- New PM2 Daemon started ----------------------------------------------------
PM2 | 2023-02-10T07:53:38: PM2 log: Time : Fri Feb 10 2023 07:53:38 GMT-0800 (GMT-08:00)
PM2 | 2023-02-10T07:53:38: PM2 log: PM2 version : 5.2.2
PM2 | 2023-02-10T07:53:38: PM2 log: Node.js version : 12.22.12
PM2 | 2023-02-10T07:53:38: PM2 log: Current arch : x64
PM2 | 2023-02-10T07:53:38: PM2 log: PM2 home : /users/.pm2
PM2 | 2023-02-10T07:53:38: PM2 log: PM2 PID file : /users/.pm2/pm2.pid
PM2 | 2023-02-10T07:53:38: PM2 log: RPC socket file : /users/.pm2/rpc.sock
PM2 | 2023-02-10T07:53:38: PM2 log: BUS socket file : /users/.pm2/pub.sock
PM2 | 2023-02-10T07:53:38: PM2 log: Application log path : /users/.pm2/logs
PM2 | 2023-02-10T07:53:38: PM2 log: Worker Interval : 30000
PM2 | 2023-02-10T07:53:38: PM2 log: Process dump file : /users/.pm2/dump.pm2
PM2 | 2023-02-10T07:53:38: PM2 log: Concurrent actions : 2
PM2 | 2023-02-10T07:53:38: PM2 log: SIGTERM timeout : 1600
PM2 | 2023-02-10T07:53:39: PM2 log: ===============================================================================
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
The report shows PM2 5.2.2 warning that the current and saved process lists differ, with no reproduction steps or source file named. Start by reproducing the warning and comparing behavior before and after pm2 save; done should identify the cause and establish the expected synchronization behavior, with coverage for the corrected case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- cli, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100