Pm2 restart error
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 43.3k
- Forks
- 2.7k
- PR merge metrics
- No merged PRs in 30d
Description
PM2 | at Process.ChildProcess._handle.onexit (internal/child_process.js:277:19)
PM2 | at onErrorNT (internal/child_process.js:472:16)
PM2 | at processTicksAndRejections (internal/process/task_queues.js:82:21)
PM2 | 2024-07-02T12:42:27: PM2 log: App [ajax-be-002:1] online
PM2 | 2024-07-02T12:42:27: PM2 error: Error: spawn node ENOENT
PM2 | at Process.ChildProcess._handle.onexit (internal/child_process.js:277:19)
PM2 | at onErrorNT (internal/child_process.js:472:16)
PM2 | at processTicksAndRejections (internal/process/task_queues.js:82:21)
PM2 | 2024-07-02T12:42:27: PM2 log: App [ajax-be-003:2] starting in -fork mode-
PM2 | 2024-07-02T12:42:27: PM2 log: Stopping app:ajax-mongo-watch id:3
PM2 | 2024-07-02T12:42:27: PM2 log: App [ajax-be-003:2] online
PM2 | 2024-07-02T12:42:27: PM2 error: Error: spawn node ENOENT
PM2 | at Process.ChildProcess._handle.onexit (internal/child_process.js:277:19)
PM2 | at onErrorNT (internal/child_process.js:472:16)
PM2 | at processTicksAndRejections (internal/process/task_queues.js:82:21)
PM2 | 2024-07-02T12:42:27: PM2 log: App [ajax-mongo-watch:3] exited with code [0] via signal [SIGINT]
PM2 | 2024-07-02T12:42:27: PM2 log: pid=2712578 msg=process killed
PM2 | 2024-07-02T12:42:27: PM2 log: App [ajax-mongo-watch:3] starting in -fork mode-
PM2 | 2024-07-02T12:42:27: PM2 log: App [ajax-mongo-watch:3] online
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
The report only provides PM2 restart logs showing repeated “spawn node ENOENT” errors and names no files, tests, environment details, or expected behavior. Start by reproducing the restart with the affected PM2 applications and inspect the restart path and Node.js executable environment. Done is not defined by the report, so clarify the expected restart behavior and the intended fix before implementing anything.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100