Unitech / Unitech/pm2

[PM2] [v] All Applications Stopped

Open
#5,920 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?

I've deployed several applications using pm2, but at noon today I suddenly found a business exception, and using the pm2 list, I found that none of the applications in the list were present.
Check the logs:

journalctl -xe | grep pm2
Nov 20 09:54:00 localhost.localdomain pm2[106811]: [PM2] Spawning PM2 daemon with pm2_home=/root/.pm2
Nov 20 09:54:00 localhost.localdomain pm2[106811]: [PM2] PM2 Successfully daemonized
Nov 20 09:54:00 localhost.localdomain pm2[106811]: [PM2][Module] Starting NPM module pm2-logrotate
Nov 20 09:54:00 localhost.localdomain pm2[106811]: [PM2][WARN] Applications pm2-logrotate not running, starting...
Nov 20 09:54:00 localhost.localdomain pm2[106811]: [PM2] App [pm2-logrotate] launched (1 instances)
Nov 20 09:54:00 localhost.localdomain pm2[106811]: [PM2] [v] Modules Stopped
Nov 20 09:54:00 localhost.localdomain pm2[106811]: [PM2] Applying action deleteProcessId on app [all](ids: [ 0 ])
Nov 20 09:54:00 localhost.localdomain pm2[106811]: [PM2] pm2-logrotate
Nov 20 09:54:00 localhost.localdomain pm2[106811]: [PM2] [v] All Applications Stopped
Nov 20 09:54:01 localhost.localdomain pm2[106811]: [PM2] [v] PM2 Daemon Stopped

What should I do to troubleshoot?

How could we reproduce this issue?

Supporting information

# Run the following commands
$ pm2 report

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

Start with the reported journalctl -xe | grep pm2 output and run pm2 report as requested. Trace why the PM2 daemon starts, deletes process id 0, stops all applications, and exits; the issue is complete only when the cause is identified and a reproducible troubleshooting path or fix is established.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, nodejs
Domain
backend, cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
18/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.