PM2 unable to spawn daemon with Node.js snap installation
Open
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 have installed Node.js via snap
node --version
v8.16.0
I installed pm2 via npm
sudo npm i -g pm2
For any command I run with pm2(even for sudo pm2 --version), I get this
[PM2] Spawning PM2 daemon with pm2_home=/home/vishnudev/.pm2
How could we reproduce this issue?
Install Node.js provided by snap and then install pm2 using npm. You'll head straight to this issue.
sudo snap install node --channel=10/stable --classic
sudo npm i -g pm2
sudo pm2 --version
[PM2] Spawning PM2 daemon with pm2_home=/home/vishnudev/.pm2
Supporting information
$ sudo pm2 report
[PM2] Spawning PM2 daemon with pm2_home=/home/vishnudev/.pm2
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 failure with the documented snap installation, npm installation, and sudo pm2 --version or sudo pm2 report commands. Trace the PM2 daemon startup path involved after the “Spawning PM2 daemon” message; done means these commands complete successfully with Node.js installed through snap.
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
- Mostly clear
- Newbie friendliness
- 35/100