ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
DevOps & observability · #pm2
Error: No process found with name 'app' – Accessibility Concern Goal Improve how pm2’s command line communicates failures and live updates to users who rely on screen readers or high‑contrast terminals. Current Behavior When a non‑existent process name is supplied to pm2 start or pm2 restart , pm2 emits the exact text “Error: No process found with name ''”.
PM2 provides the max_memory_restart option to automatically reboot a process when it exceeds a specific memory threshold. This is often used as a safeguard against gradual memory leaks in Node.js applications. In a production environment using PM2 v5.x, there is uncertainty regarding which specific memory metric the process manager monitors to trigger this r
PM2 Cluster Mode utilizes the Node.js cluster module to distribute incoming connections across multiple worker processes. When the instances property is set to max in an ecosystem file, PM2 spawns a process for every logical CPU core detected on the host machine. While this maximizes CPU utilization, each worker operates as a separate process with its own me
When a deployment introduces a database schema change, the expectation is that rolling back the application code with pm2 deploy revert also returns the database to its previous compatible state. However, the revert command only restores the released source code and Node modules; it does not automatically invoke any migration down scripts, and there is no do
nodejs