AlmaLinux 9.4 and Red Hat Enterprise Linux release 8.9 (Ootpa) How to solve this chronic problem

--- PM2 report ----------------------------------------------------------------
Date : Sun Nov 03 2024 20:02:31 GMT-0300 (Brasilia Standard Time)

--- Daemon -------------------------------------------------
pm2d version : 5.1.2
node version : 16.20.2
node path : /root/.nvm/versions/node/v16.20.2/bin/pm2
argv : /root/.nvm/versions/node/v16.20.2/bin/node,/root/.nvm/versions/node/v16.20.2/lib/node_modules/pm2/lib/Daemon.js
argv0 : node
user : root
uid : 0
gid : 0
uptime : 2min

--- CLI ----------------------------------------------------
local pm2 : 5.1.2
node version : 16.20.2
node path : /root/.nvm/versions/node/v16.20.2/bin/pm2
argv : /root/.nvm/versions/node/v16.20.2/bin/node,/root/.nvm/versions/node/v16.20.2/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 E3-1240 v5 @ 3.50GHz
cpus nb : 1
freemem : 7435120640
totalmem : 8021286912
home : /root

--- 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 VirtualHost SamosAdmin ApiSamos differs. Type 'pm2 save' to synchronize.

--- Daemon logs --------------------------------------------
/root/.pm2/pm2.log last 20 lines:
PM2 | 2024-11-03T19:58:40: PM2 log: App [ApiSamos:2] exited with code [0] via signal [SIGINT]
PM2 | 2024-11-03T19:58:40: PM2 error: Cancelling versioning data parsing
PM2 | 2024-11-03T19:58:40: PM2 log: pid=1662 msg=process killed
PM2 | 2024-11-03T19:58:40: PM2 log: Exited peacefully
PM2 | 2024-11-03T20:00:30: PM2 log: ===============================================================================
PM2 | 2024-11-03T20:00:30: PM2 log: --- New PM2 Daemon started ----------------------------------------------------
PM2 | 2024-11-03T20:00:30: PM2 log: Time : Sun Nov 03 2024 20:00:30 GMT-0300 (Brasilia Standard Time)
PM2 | 2024-11-03T20:00:30: PM2 log: PM2 version : 5.1.2
PM2 | 2024-11-03T20:00:30: PM2 log: Node.js version : 16.20.2
PM2 | 2024-11-03T20:00:30: PM2 log: Current arch : x64
PM2 | 2024-11-03T20:00:30: PM2 log: PM2 home : /root/.pm2
PM2 | 2024-11-03T20:00:30: PM2 log: PM2 PID file : /root/.pm2/pm2.pid
PM2 | 2024-11-03T20:00:30: PM2 log: RPC socket file : /root/.pm2/rpc.sock
PM2 | 2024-11-03T20:00:30: PM2 log: BUS socket file : /root/.pm2/pub.sock
PM2 | 2024-11-03T20:00:30: PM2 log: Application log path : /root/.pm2/logs
PM2 | 2024-11-03T20:00:30: PM2 log: Worker Interval : 30000
PM2 | 2024-11-03T20:00:30: PM2 log: Process dump file : /root/.pm2/dump.pm2
PM2 | 2024-11-03T20:00:30: PM2 log: Concurrent actions : 2
PM2 | 2024-11-03T20:00:30: PM2 log: SIGTERM timeout : 1600
PM2 | 2024-11-03T20:00:30: PM2 log: ===============================================================================

Start with the PM2 report and daemon log excerpt in the issue, focusing on PM2 5.1.2, Node.js 16.20.2, and the AlmaLinux 9.4 and RHEL 8.9 environments. Reproduce the reported process-list and daemon behavior, then verify that the investigation explains the warning and provides a confirmed resolution for both environments.