PM2 can generate startup scripts and configure them in order to keep your process list intact across expected or unexpected machine restarts.
Make sure you upgrade to PM2 > 2.2.x
To get the automatically-configured startup script for your machine you need to type this command:
# Detect available init system, generate configuration and enable startup system pm2 startup
You can specify the platform you use by yourself if you want to (where platform can be either one of the cited above):
pm2 startup [ubuntu | ubuntu14 | ubuntu12 | centos | centos6 | arch | oracle | amazon | macos | darwin | freebsd | systemd | systemv | upstart | launchd | rcd | openrc]
The output of this command can be a recommendation of the line to copy/paste with all environment variables and options configured for you.
[PM2] You have to run this command as root. Execute the following command: sudo su -c "env PATH=$PATH:/home/unitech/.nvm/versions/node/v4.3/bin pm2 startup <distribution> -u <user> --hp <home-path>
You simply have to copy/paste the line PM2 gives you and the startup script will be configured for your OS.
NOTE : When updating nodejs, the
pm2 binary path might change (it will necessarily change if you are using nvm). Therefore, we would advise you to run the
startup command after any update.
NOTE2: You can customize the service name via the
--service-name <name> option (#3213)
Once you started all the applications you want to manage, you can save the list across expected/unexpected server restart by typing this command:
It will save the process list with the corresponding environments into the dump file
This brings back previously saved processes (via pm2 save):
The previous line code let PM2 detect your platform. Alternatively you can use another specified init system youself using:
pm2 unstartup [ubuntu | ubuntu14 | ubuntu12 | centos | centos6 | arch | oracle | amazon | macos | darwin | freebsd | systemd | systemv | upstart | launchd | rcd | openrc]
Let’s say you want the startup script to be executed under another user.
Just use the
-u <username> option and the
pm2 startup ubuntu -u www --hp /home/ubuntu
To update the startup script (in case you changed the Node.js version via NVM for example) run the following commands:
pm2 unstartup pm2 startup
# Check if pm2-<USER> service has been added $ systemctl list-units # Check logs $ journalctl -u pm2-<USER> # Cat systemd configuration file $ systemctl cat pm2-<USER> # Analyze startup $ systemd-analyze plot > output.svg
To wait efficiently that machine is online for PM2 to run:
[Unit] Wants=network-online.target After=network.target network-online.target [....] [Install] WantedBy=multi-user.target network-online.target