pm2 shows online with pid=0, but server not start and no logs
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 43.3k
- Forks
- 2.7k
- PR merge metrics
- No merged PRs in 30d
Description
I tried pm2 reload and pm2 restart and pm2 stop && start, but none of these works, the application still got pid 0 and "online" status, but it's not online.
The only way to fix it is pm2 delete && pm2 start.
Is this a bug or not? What should I do to prevent this?
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
Reproduce the reported state where PM2 shows pid 0 and “online” after reload, restart, or stop followed by start. Compare the process status and logs before and after the reported delete-and-start workaround, using the commands and screenshots in the issue as the starting point. Done means the failure is reproducible and the process status or logs clearly reflect whether the server is running.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- cli, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100