NodeJS applications are used in backends all over the web to perform various tasks. But unlike most web software, NodeJS scripts run in the foreground, rather than in the background as a daemon process, which inconveniently requires an open terminal window using a program such as screen or tmux to run on the server.<\/p>\n
However, it is possible to convert a NodeJS application to run as a daemon process. PM2 is a production process manager for NodeJS that can be used for this purpose.<\/p>\n
To complete this guide, you will need the following: You will first need to install PM2 globally via NPM.<\/p>\n Now you can run your NodeJS application using PM2.<\/p>\n Here is a sample of what the expected output should look like:<\/p>\n PM2 is now keeping track of your application. If it crashes, PM2 will restart it and keep a log of any errors.<\/p>\n PM2 has another feature whereby when the server reboots, PM2 can make sure to start up any applications it manages.<\/p>\n First, let’s configure the PM2 utility to boot up automatically with your system. Generate and install the PM2 init scripts.<\/p>\n Take note of the command that this outputs. In order for the PM2 utility to start automatically, you will need to run this command as root.<\/p>\n Afterwards, verify the status of PM2, and make sure that it has been added to the init portion of your operating system.<\/p>\n This is the output that you should see.<\/p>\n Enable PM2 to boot automatically.<\/p>\n If you see the following output, then it should be the case that the symlink has been created and that PM2 will load upon system boot.<\/p>\n Now you will be able to use PM2 to easily manage and automatically restart your NodeJS applications. If this guide was helpful to you, kindly share it with others who may also be interested. <\/p>\n Below are a few useful commands that you can use with PM2 to manage the status of an application. For the purpose of example, we are using an application named nodetest.<\/p>\n List applications<\/p>\n Output:<\/p>\n Stop your application<\/p>\n Output:<\/p>\n Restart your application<\/p>\n Output:<\/p>\n PM2 Monitor (similar to the top program for Linux)<\/p>\n Output:<\/p>\n Install and use the PM2 NodeJS to deploy apps in production on Ubuntu 16 NodeJS applications are used in backends all over the web to perform various tasks. But unlike most web software, NodeJS scripts run in the foreground, rather than in the background as a daemon process, which inconveniently requires an open terminal window<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[71],"tags":[],"class_list":["post-2194","post","type-post","status-publish","format-standard","hentry","category-applications","operating_system-ubuntu-16-04"],"yoast_head":"\n
\n\u2022 1 Node (Cloud Server<\/b><\/a> or Dedicated Server<\/b><\/a>) running Ubuntu 16.
\n\u2022 All commands should be run as the root user
\n\u2022 Do not run NodeJS applications as root in production. To increase security, create a new user specifically for running NodeJS applications.
\n\u2022 NodeJS\/NPM must be installed.
\n\u2022 You should have a pre-existing NodeJS application to daemonize.<\/p>\nTutorial<\/h2>\n
npm install -g pm2<\/code><\/p>\ncd \/home\/nodeapp
\npm2 start nodetest.js<\/code><\/p>\nroot@nodejs:\/home\/nodeapp# pm2 start nodetest.js
\n[PM2] Spawning PM2 daemon
\n[PM2] PM2 Successfully daemonized
\n[PM2] Starting nodetest.js in fork_mode (1 instance)
\n[PM2] Done.
\n???????????????????????????????????????????????????????????????????????????????? ?????
\n? App name ? id ? mode ? pid ? status ? restart ? uptime ? memory ? watch ing ?
\n???????????????????????????????????????????????????????????????????????????????? ?????
\n? nodetest ? 0 ? fork ? 26935 ? online ? 0 ? 0s ? 21.680 MB ? disab led ?
\n???????????????????????????????????????????????????????????????????????????????? ?????
\n Use `pm2 show pm2 startup ubuntu<\/code><\/p>\nroot@nodejs:\/home\/nodeapp# pm2 startup ubuntu
\n[PM2] Generating system init script in \/etc\/init.d\/pm2-init.sh
\n[PM2] Making script booting at startup...
\n[PM2] -enabled- Using the command:
\n su -c \"chmod +x \/etc\/init.d\/pm2-init.sh && update-rc.d pm2-init.sh defaults\"
\n[PM2] Done.Make the PM2 utility boot automatically with your system<\/code><\/p>\nsu -c \"chmod +x \/etc\/init.d\/pm2-init.sh && update-rc.d pm2-init.sh defaults\"<\/code><\/p>\nsystemctl status pm2<\/code><\/p>\n? pm2.service - PM2 next gen process manager for Node.js
\n Loaded: loaded (\/etc\/systemd\/system\/pm2.service; disabled; vendor preset: enabled)
\n Active: inactive (dead)<\/code><\/p>\nsystemctl enable pm2<\/code><\/p>\nCreated symlink from \/etc\/systemd\/system\/multi-user.target.wants\/pm2.service to \/etc\/systemd\/system\/pm2.service.<\/code><\/p>\nConclusion<\/h2>\n
Quick reference<\/h2>\n
pm2 list<\/code><\/p>\nroot@nodejs:\/home\/nodeapp# pm2 list
\n?????????????????????????????????????????????????????????????????????????????????????
\n? App name ? id ? mode ? pid ? status ? restart ? uptime ? memory ? watching ?
\n?????????????????????????????????????????????????????????????????????????????????????
\n? nodetest ? 0 ? fork ? 26935 ? online ? 0 ? 24m ? 31.672 MB ? disabled ?
\n?????????????????????????????????????????????????????????????????????????????????????
\n Use `pm2 show pm2 info nodetest<\/code><\/p>\nroot@nodejs:\/home\/nodeapp# pm2 info nodetest
\n Describing process with id 0 - name nodetest
\n????????????????????????????????????????????????????????????
\n? status ? online ?
\n? name ? nodetest ?
\n? restarts ? 0 ?
\n? uptime ? 25m ?
\n? script path ? \/home\/nodeapp\/nodetest.js ?
\n? script args ? N\/A ?
\n? error log path ? \/root\/.pm2\/logs\/nodetest-error-0.log ?
\n? out log path ? \/root\/.pm2\/logs\/nodetest-out-0.log ?
\n? pid path ? \/root\/.pm2\/pids\/nodetest-0.pid ?
\n? interpreter ? node ?
\n? interpreter args ? N\/A ?
\n? script id ? 0 ?
\n? exec cwd ? \/home\/nodeapp ?
\n? exec mode ? fork_mode ?
\n? node.js version ? 6.2.2 ?
\n? watch & reload ? ? ?
\n? unstable restarts ? 0 ?
\n? created at ? 2016-07-01T06:27:55.763Z ?
\n????????????????????????????????????????????????????????????
\n Code metrics value
\n???????????????????????
\n? Loop delay ? 0.62ms ?
\n???????????????????????
\n Add your own code metrics: http:\/\/bit.ly\/code-metrics
\n Use `pm2 logs nodetest (--lines 1000)` to display logs
\n Use `pm2 monit` to monitor CPU and Memory usage nodetest<\/code><\/p>\npm2 restart nodetest<\/code><\/p>\nroot@nodejs:\/home\/nodeapp# pm2 restart nodetest
\n[PM2] Applying action restartProcessId on app [nodetest](ids: 0)
\n[PM2] [nodetest](0) ?
\n?????????????????????????????????????????????????????????????????????????????????????
\n? App name ? id ? mode ? pid ? status ? restart ? uptime ? memory ? watching ?
\n?????????????????????????????????????????????????????????????????????????????????????
\n? nodetest ? 0 ? fork ? 27341 ? online ? 1 ? 0s ? 15.570 MB ? disabled ?
\n?????????????????????????????????????????????????????????????????????????????????????
\n Use `pm2 show pm2 monit<\/code><\/p>\nroot@nodejs:\/home\/nodeapp# pm2 monit
\n? PM2 monitoring (To go further check out https:\/\/app.keymetrics.io)
\n ? nodetest [ ] 0 %
\n[0] [fork_mode] [|||||||||||||||||||||||||| ] 35.691 MB<\/code><\/p>\n","protected":false},"excerpt":{"rendered":"