pm2 list is empty
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
--- Daemon logs --------------------------------------------
/home/pdt_dev_jiangrui/.pm2/pm2.log last 20 lines:
PM2 | 2020-12-04T18:51:41: PM2 log: App [koomallop-nuxt:0] online
PM2 | 2020-12-04T18:51:44: PM2 log: App [koomallop-nuxt:0] exited with code [1] via signal [SIGINT]
PM2 | 2020-12-04T18:51:44: PM2 log: App [koomallop-nuxt:0] starting in -fork mode-
PM2 | 2020-12-04T18:51:44: PM2 log: App [koomallop-nuxt:0] online
PM2 | 2020-12-04T18:51:47: PM2 log: App [koomallop-nuxt:0] exited with code [1] via signal [SIGINT]
PM2 | 2020-12-04T18:51:47: PM2 log: App [koomallop-nuxt:0] starting in -fork mode-
PM2 | 2020-12-04T18:51:47: PM2 log: App [koomallop-nuxt:0] online
PM2 | 2020-12-04T18:51:50: PM2 log: App [koomallop-nuxt:0] exited with code [1] via signal [SIGINT]
PM2 | 2020-12-04T18:51:50: PM2 log: App [koomallop-nuxt:0] starting in -fork mode-
PM2 | 2020-12-04T18:51:50: PM2 log: App [koomallop-nuxt:0] online
PM2 | 2020-12-04T18:51:50: PM2 log: App [koomallop-nuxt:0] exited with code [7] via signal [SIGINT]
PM2 | 2020-12-04T18:51:50: PM2 log: App [koomallop-nuxt:0] starting in -fork mode-
PM2 | 2020-12-04T18:51:50: PM2 log: App [koomallop-nuxt:0] online
PM2 | 2020-12-04T18:51:50: PM2 error: Error: spawn node ENOENT
PM2 | at Process.ChildProcess._handle.onexit (internal/child_process.js:267:19)
PM2 | at onErrorNT (internal/child_process.js:469:16)
PM2 | at processTicksAndRejections (internal/process/task_queues.js:84:21)
PM2 | 2020-12-04T18:51:50: PM2 error: Cancelling versioning data parsing
PM2 | 2020-12-04T18:53:35: PM2 log: Stopping app:koomallop-nuxt id:0
PM2 | 2020-12-04T18:53:35: PM2 error: app=koomallop-nuxt id=0 does not have a pid
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
Start by running the requested pm2 report command and reviewing the daemon log at /home/pdt_dev_jiangrui/.pm2/pm2.log. Investigate the reported spawn node ENOENT error and the app process without a pid. Done means the reproduction is understood and pm2 list reliably shows the managed app or the issue is documented as an environment problem.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100