You’re almost there, use node_args instead of args: args are your script arguments node_args are arguments that are passed to node executable { “name”: “myName”, “script”: “app.js”, “node_args”: [“–debug=7000”] } PM2 json schema. If someone still has problems with the debug setting after this, in some case you have to disable the cluster mode for … Read more
Not by default, but PM2 can do so using a startup script: PM2 can generate startup scripts and configure them in order to keep your process list intact across expected or unexpected machine restarts. After generating your startup script (read also this comment), take a look at pm2 save: Once you started all the applications … Read more
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 … Read more
You can use an environment variable. For example: NODE_PORT=3002 pm2 start -i 0 app.js Here is how to read the value in app: console.log(process.env.NODE_PORT); Or, if you are building an Express app: PORT=3002 pm2 start -i 0 ./bin/www Express loads PORT automatically when the application starts.
Yes, it does this by default. For more information see Restart strategies. If the app repeatedly fails to start over a short period of time, pm2 may cease restarting. See configuration, min_uptime and max_restarts.
Use the –cron option: -c –cron <cron_pattern> For example: pm2 start sendMail.js –cron “*/15 * * * *” Pm2 will now restart the sendMail.js script on the hour, and at 15, 30 and 45 minutes past the hour
It was a bug in pm2. I submitted an issue and they fixed it. To solve it on your side, run these commands: $ npm install pm2@latest -g $ pm2 update And it should work with the latest release.
pm2 saves logs to $HOME/.pm2/logs/XXX-err.log by default, where XXX is your pm2 app name
I believe you can also see the stdout and stderr of a process that is running daemonized by the command pm2 logs or pm2 logs [app-name].
pm2 save takes a snapshot of your currently running Node applications. You can then restore these applications using pm2 resurrect. This is useful because it means you don’t have to manually restart each application when you restart pm2 (such as a machine reboot). Instead, you can just have a script that calls pm2 resurrect and … Read more