![image.png](https://ipfs.busy.org/ipfs/QmPrmnVXjv3Q1QaT2BND98QgRC2hXJeKisxUrW6oi8uDsd)

Process Manager 2 (aka PM2) is one of my favorite apps that allows me to manage my scripts.  It is easy to use and extremely powerful.

# What PM2 offers:

* Restart scripts automatically upon failure
* Restart scripts automatically upon boot
* Log management
* Easy Monitoring
* Watch Dog Support
* Cluster & Scaling Support
* Cross platform
* Easy to use

# Why use PM2?

Many people use screen & tmux to run scripts on Linux and keep them running when you exit your SSH terminal.  While these are both very useful for scripts you will be watching frequently or interacting with, it is not ideal for more than one or two apps or automatically handling failures.

PM2 will auto-detect if a script has quit and will automatically restart it.  This is really handy for automatically handling rare exceptions and extremely powerful if your scripts are able to auto-resume.

# How to install PM2

PM2 is a NodeJS application and requires NodeJS to be installed.  While it was designed to manage NodeJS applications it supports Python and Ruby as well.  In fact, I mostly use it to run Python scripts.

You will first need to install NodeJS and I highly recommend using Node Version Manager (nvm).

### Install Node Version Manager

Installing nvm is really simple, and you can see the instructions on their [Github Page](https://github.com/nvm-sh/nvm).

It's is just this one line:

`curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.34.0/install.sh | bash`

After you install it though, you need to exit your SSH session and log back in. 

Finally, you need to install a version of NodeJS, you have two options here.  You can install the latest version of node (my preference) or you can install the latest **Long Term Support** (lts) release.  The LTS release a bit further back and considered the **production** supported release.

#### Install latest NodeJS

`nvm install node`
`nvm use node`

#### Install LTS release of NodeJS

`nvm install --lts`
`nvm use --lts`

Regardless of your choice, you can check the version you have installed by running `node -v`.

### Install PM2 Module

Installing PM2 is real easy, just run `npm install -g pm2`

This will install PM2 as a global module.  NodeJS modules are typically installed locally to the app you are developing, but since pm2 is a tool you use system-wide you want to have it installed globally (-g option).

Once installed you can just type `pm2 ls` to see all running process.  At this point, you won't have anything.

You can now use PM2 to run your scripts and keep an eye on them.

### Start a script with PM2

To start a script you just need to type `pm2 start myscript.js --name myscript`

If you type `pm2 ls` you will see the script running and some details about memory usage, how many restarts, the pid, and cpu usage.

If you want the script to run automatically at bootup, you will need to type `pm2 save` every time you add or remove a script.  This will tell PM2 to save the state of your scripts and recover that state upon reboot.

You can log out of SSH at this point and your script will continue to run, will be restarted if it fails, and will automatically start upon reboots.

#### Stop, restart, or remove a script

There are a few commands you will want to know to manage your scripts.

`pm2 stop myscript`

This command will stop the script called myscript.  Keep in mind, you use the name you specified with the --name argument and not the file name.

`pm2 restart myscript`

This will restart the script nicknamed myscript.

You can also `pm2 restart all` to restart all scripts or stop them all with `pm2 stop all`.

If you ever want to see the current status of your scripts, you can use `pm2 ls` or `pm2 monit`.

Monit is a more detailed view and generally is used as a "tv mode" type of display.

If you need to remove a script (this stops the script and no longer manages it) you can use `pm2 delete myscript`.

# Logging

PM2 will automatically log the output of your scripts to a file.  This is one of the best features of PM2.  Your quick and dirty scripts don't need to manage logging to the screen and to a log file, PM2 can do this automatically.

You can view logs for your script by typing `pm2 logs myscript` or view all logs at once using `pm2 logs`.

You can also look at the raw log files in `~/.pm2/logs`

# Conclusion

This is enough to handle 90% of the functionality you need to take advantage of PM2.  PM2 can do so much more and is far more powerful than the ease of use makes it appear.

If your script needs environment variables, command-line arguments, or you are having problems with Python buffering output, I recommend you check out the page on [Eco System Files](http://pm2.keymetrics.io/docs/usage/application-declaration/).    

https://i.imgur.com/yBNfG0R.png

You can also check out the [Clustering Docs](http://pm2.keymetrics.io/docs/usage/cluster-mode/) if you plan on having it manage multiple instances and scaling of your app.

There is a web interface to PM2 that shows far more detail about your applications.

![image.png](https://ipfs.busy.org/ipfs/QmfLwPqsWXBivYXAMHkQBMGLshmf2wnEQowDwzL9XgAwny)

![image.png](https://ipfs.busy.org/ipfs/QmYqJ4VQum3KhRN4e9twibGZnzWtZE5btvjaWZuUaQ4eaU)

![image.png](https://ipfs.busy.org/ipfs/QmTqXxYBbXX3vLWACbh2Ax1KapWwhJsbvdJGfAYh9LNJLB)

There is also a paid version you can read about on https://pm2.io that has more advanced features like Machine Learning Error Detection.

<sub>Images: [1](https://medium.com/tech-tajawal/process-manager-pm2-performance-optimization-part-ii-6ca8e431a578) [2](http://pm2.keymetrics.io/docs/usage/application-declaration/) [3](https://pm2.io/) [4](https://pm2.io/) [5](https://pm2.io/)</sub>