PM2 Unable to start API with Cluster mode and interpreter
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?
sudo node version
6.10.0
node version
13.14.0
I am using ecosystem.config.js for run my application
name: api,
script: 'bin/www_ssl',
cwd: projectPath,
exec_mode: "cluster",
instances: 4,
interpreter: "/home/ubuntu/.nvm/versions/node/v13.14.0/bin/node",
log_date_format: 'YYYY-MM-DD HH:mm:ss.SSS',
enable: true
NOTE: This is Production Server and Running other application as well, So I can't change node version or can't remove any node version both the version I am using it in different application
using below command to run
sudo pm2 start ecosystem.config.js
In desc command I can able to see interpreter path is correct but picking wrong node version rather than choose 13.14.0 version pm2 using older version 6.10.0 version
Can you please help me to solve this as soon as.
How could we reproduce this issue?
You can easily reproduce this using above config
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 with the provided ecosystem.config.js and reproduce the issue using sudo pm2 start ecosystem.config.js on a system with both Node 6.10.0 and 13.14.0 installed. Compare the interpreter selected in fork and cluster modes; done means the configured Node 13.14.0 interpreter is used consistently without changing other applications.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nodejs
- Domain
- cli, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100