How to run pm2 so other server users are able to access the process?

**When I start my Nodejs app with [pm2][1], other server users are not able to access the process.**

Even if I start pm2 from a custom directory (not current user's `~/`, what pm2 is using by default):

HOME=/var/www pm2 start app.js

*Directory is accessible by any user* (comparing to `~/`, but there's still no way other server user is able to access the process.

When other server user does `pm2 list`, it shows him 0 processes are running – but there are (started by another user). And when other user tries `HOME=/var/www pm2 list`, CLI throws an error:

events.js:72
throw er; // Unhandled 'error' event
^
Error: connect EACCES
at errnoException (net.js:905:11)
at Object.afterConnect [as oncomplete] (net.js:896:19)

So I am wondering how to make sure users are able to access pm2 processes run by other server users? Or it shall be approached differently?


----------


I am wondering why every server user is able to make `git pull` to deploy latest source code from a Git repository, but can't restart `pm2` process afterwards? Only the user that started `pm2` process is able to restart it… Weird.

[1]:

[To see links please register here]

It seems that PM2 saves data under user's '~/.pm2' folder, so other users can not see your PM2 process with 'pm2 status'.

I created a new linux user for PM2, and all users use 'su pm2user' before starting Pm2 process:

$ sudo su pm2user
$ sudo pm2 start app.js

It's a stupid way, but it is simple and works well. Hope this would help :)

Here's how we bypassed this.

Just create a group

- Create a new group `pm2` or whatever name works for you

`$ groupadd pm2`

- Change the `/var/www/` folder group owner to group `pm2`

`$ chgrp -R pm2 /var/www`


- Add the other user, let's say bob, to pm2

`$ usermod -aG pm2 bob`

Now bob can run pm2 commands by changing $HOME to */var/www*

`$ env HOME=/var/www pm2 list`

Or (better still) create an alias as @jcollum suggested

`$ alias pm2='env HOME=/var/www pm2'`

I've faced a similar issue. The reason may be that you do not have the required permissions, or you do not own the pid and sock files created by pm2. In my case, it was working fine when I started the pm2 from commandline instead of startup. When I used startup, it was running as root user by default. So root was the owner of the pid, sock files

Assuming you run pm2 as `www-data`. To have access to that pm2 instance, I do: `sudo -u www-data HOME=/var/www pm2 list` for example. You can, of course, create a script (e.g. `supm2`) that does that for you so you can just do `supm2 list` instead.

I know that I am late to the party, but this is how I did it:


PM2="/usr/share/nodejs/pm2"
USER="me"
useradd $USER
groupadd pm2
chgrp -R pm2 $PM2
usermod -aG pm2 $USER
setfacl -Rdm g:pm2:rwx $PM2

**/etc/bash.bashrc etc**

export PM2_HOME=$PM2;

Ok, here is my solution for same problem:

```bash
# 1. Create user PM2 and set his password
sudo useradd -d /opt/pm2 -m -s /bin/bash pm2
sudo passwd pm2

# 2. Add users you want to provide the access to PM2 to PM2 group
sudo usermod -aG pm2 <username>

# Note: if you added yourself to pm2 group, perform logout and login back to the host machine

# 3. Set the PM2_HOME variable
sudo touch /etc/profile.d/pm2.sh
sudo sh -c 'echo "export PM2_HOME=\"/opt/pm2/.pm2\"" > /etc/profile.d/pm2.sh'
source /etc/profile.d/pm2.sh

# 4. Install the PM2
# Check the npm prefix if fail:
#

[To see links please register here]

sudo npm install pm2 -g

# 5. Make startup script
sudo pm2 startup ubuntu -u pm2 --hp /opt/pm2

sudo systemctl enable pm2-pm2 && \
sudo systemctl start pm2-pm2 && \
sudo systemctl status pm2-pm2

# 6. Change permission of PM2_HOME
sudo chmod -v g+w /opt/pm2/.pm2

# 7. Check the PM2
pm2 status
```

I also have the need to use pm2 with multiple users and I found a solution seemed even better. Here is brief version from Piotr Sobuś's [medium article][1].

sudo groupadd pm2 # Create pm2 group for user who want manage pm2 together
sudo usermod -a -G pm2 user1 # add yourself to pm2 group
sudo usermod -a -G pm2 user2 # add as many user as you need to pm2 group
# you need to login again for new group to apply to user
sudo mkdir /etc/pm2daemon
sudo chgrp -R pm2 /etc/pm2daemon
sudo chmod -R 770 /etc/pm2daemon
sudo chmod g+s /etc/pm2daemon

Add following lines to ~/.bashrc for users that you want to share pm2 management.

# PM2 environment
export PM2_HOME=/etc/pm2daemon

If you install pm2 systemd service with pm2 startup. You also need to modify PIDFILE and PM2_HOME in systemd service confgiuration file:
`/etc/systemd/system/multi-user.target.wants/pm2-YOUR_USER_NAME.service`

from:

...
Environment=PM2_HOME=/home/YOUR_USER_NAME/.pm2
PIDFile=/home/YOUR_USER_NAME/.pm2/pm2.pid
...

to:

...
Environment=PM2_HOME=/etc/pm2daemon
PIDFile=/etc/pm2daemon/pm2.pid
...

After modification, you need to use `systemctl daemon-reload` to update systemd configuration. Now start the service with `sudo systemctl start pm2-YOUR_USER_NAME.service`.

Then you can now use pm2 across users that you shared.

PS. If you fail to start service with systemctl, kill current pm2 daemon process by `pm2 kill`. Now you should able to use systemctl to start pm2 daemon.


[1]:

[To see links please register here]