-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot run pm2 as another user #4058
Labels
Comments
In the ecosystem.config.js, can you declare the user under the module.exports = [{
"name": "electron",
"script": "./node_modules/.bin/electron",
"args": "./electron",
"user": "envision",
"time": true,
"max_memory_restart": "1000M",
"restart_delay": "10000",
"env": {
"ENVISION_ENV": "production",
"DISPLAY": ":0"
}
}] |
You should not get this must be an integer error |
@Unitech I use latest pm2 v3.5.0 and get the same
|
@Unitech also adding |
This was referenced May 6, 2019
inerc
pushed a commit
to inerc/pm2
that referenced
this issue
Feb 11, 2020
Fix: Allow usernames in uid/gid/user again (fixes Unitech#4058, Unitech#4262)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
pm2 start ecosystem.config.js --uid node --env production has now all of a sudden given the error: uid must be an integer. I am the root user and this has been working all along.
I've also tried:
pm2 start ecosystem.config.js -u node --env production : doesn't do anything, process is owned by root.
pm2 start ecosystem.config.js --uid $(id -u node) --env production : same error uid must be an integer
pm2 start ecosystem.config.js --uid 1003 --env production : same error uid must be an integer
god daemon is running as root and PM2_HOME is set a /home/node/.pm2
The text was updated successfully, but these errors were encountered: