I want to start node with pm2 and environment variables like --nouse-idle-notification or --max-old-space-size=2048.
However, whatever I do, it is not passing the node variables. I start my app with pm2 and a configuration file. The configuration file looks like:
{
"apps" : [{
"env": {
"NODE_PATH": "/usr/bin/node",
"interpreter_args": "--max-old-space-size=2048 --nouse-idle-notification"
},
"env_development": {
"NODE_ENV": "development"
},
"env_production" : {
"NODE_ENV": "production",
"APP_TYPE": "web"
},
"exec_mode" : "fork",
"name" : "MyApp",
"script" : "/opt/myapp/app.js",
"watch" : false,
"out_file" : "/var/log/app.log",
"error_file" : "/var/log/app.log",
"combine_logs": true,
"node_args": "--max-old-space-size=2048 --nouse-idle-notification",
"args": "--max-old-space-size=2048 --nouse-idle-notification"
}]
}
(as you can see I try to pass in the node variables in multiple ways)
I then start the app with:
pm2 restart pathtojsonfile --env production
Everything is starting up properly and I see variables like "MY_APP" in my code. However, now when I look at the process with "top" I only see:
node /opt/myapp/app.js
When I start the app with forever or manually I can see the process like:
node --max-old-space-size=2048 --nouse-idle-notification /opt/myapp/app.js
Is pm2 just not showing those node arguments or are they really not passed in? (The pm2 started process uses less memory)
Below is extact command to start pm2 with node-args
pm2 start app.js --node-args="--max-old-space-size=4096"
By using "node_args": "--max-old-space-size=2048 --nouse-idle-notification" you did the right thing and these arguments are taken into account.
PM2 renames the process and drop the specified node argument in the process title.
Related
Running my app with pm2 start index.js --watch functions as expected. I would like to use the config to ignore_watch.
ecosystem.config.js
module.exports = {
apps : [{
name : "appname",
script : "./index.js",
watch : true,
max_mamory_restart : "1G",
ignore_watch : "\.bash(rc|_(history|logout)),\.(cache|config|gitignore|lesshst|local|npm|pm2|profile|sudo_as_admin_successful|vscode_server),.*swp,snap,.*config.js,package-lock.json,node_modules,jira,logs"
}]
}
When I run pm2 start ecosystem.config.js, my app runs, but constantly restarts with Change detected on path .pm2/.......
I thought that maybe I am not writing the ignore_watch correctly, so I tried
ignore_watch : [
".pm2",
"\.bash(rc|_(history|logout))",
"\.cache|config|gitignore|lesshst|local|npm|pm2|profile|sudo_as_admin_successful|vscode_server)",
".*swp",
"snap",
".*config.js,package-lock.json,node_modules,jira,logs"
]
which then gives me constant restarts with Change detected on path .vscode_server/.......
I then tried the same thing by editing ignore_watch to:
ignore_watch : [
".vscode_server",
".pm2",
but this still restarts with with Change detected on path .vscode_server/.......
I don't understand how the ignore_watch is working, especially where the original pm2 start index.js --watch doesn't appear to watch these folders and its not constantly restarting.
How would I start a pm2 process with the —max-http-header-size node option, as well as name the process.
I have a server with multiple micro-services, one of the services is a web scraper.
This web scraper accepts requests with headers over the nodejs default 8kb limit. So, to run my app locally have to add the --max-http-header-size node option.
I've cloned my app to the server, but don't know how to set --max-http-header-size, nor do I know how to name the process within the pm2 start command.
So far my attempts have looked like this.
// this sets the name, but I don't know how to add the option `--max-http-header-size`
pm2 start npm --name "{REPONAME}" -- start
pm2 start node --name "scraper" --max-http-header-size 15000 app.js
pm2 start node --max-http-header-size 15000 app.js -- --name "scraper"
The accepted answer by David Harvey did not work for me as of Node 16. Instead, I had to use node_args, something like this:
{
"apps" : [{
"name" : "myapp",
"script" : "./app.js",
"node_args": "--max-http-header-size=256000",
"env": {
"NODE_ENV": "production",
}
}]
}
What you're looking for is called environment variables! You can pass environment variables to pm2 using a file that loads your server like this:
module.exports = {
apps : [
{
name: "myapp",
script: "./app.js",
watch: true,
node_args: "--max-http-header-size=16000"
}
]
}
Here's more about it too:
https://pm2.keymetrics.io/docs/usage/environment/
I am facing a peculiar issue. I am trying to start my application with pm2 . Without the json file , it works perfectly fine , but when I add a json file and try to start it , it does not hit my application in the first start , but works well if I stop and start the instance again.Also , when the instance is first started if I do pm2 list , the PID number keeps changing continually. Any help on this please?
PM2 json file :
{
"apps" : [{
"name" : "ABC",
"script" : "./bin/www",
"watch" : true,
"env": {
"NODE_ENV": "development",
"PORT":8443
},
"env_production" : {
"NODE_ENV": "production",
"PORT":4000
},
"error_file" : "err.log",
"out_file" : "out.log",
"merge_logs" : false
}]
}
Command to start the application with pm2 json file : pm2 start sample.json
Command to stop the application with pm2 json file : pm2 stop ABC
to kill : pm2 kill
Thanks in advance.
You might try setting your exec_mode to fork. If I had to guess, it's starting up with a default mode of cluster and it spins up the number of instances equivalent to the number of processors as detected by the system. While this is typically fine for webapps, it's not always suitable for all situations.
You could also try setting instances to 1 in cluster mode
Your PM2-JSON-File looks good but how looks like your
package.json
....
"scripts": {
"start": "node start -p 8443 /bin/www"
"test": "echo \"Error: no test specified\" && exit 1"
},
.....
In a PM2 JSON configuration, is there a way to choose cluster vs. fork mode based on the environment?
Also, it seems like putting watch inside the development environment doesn't actualy restart on changes, even though pm2 status shows watch is enabled?
I've tried this configuration but don't get the expected results:
"env_production": {
"NODE_ENV": "production",
"watch": false,
"exec_mode": "cluster",
"instances": "max"
},
"env": {
"watch": ["files/to/watch/*"],
"ignore_watch" : ["files/to/watch/not/*"],
"exec_mode": "fork"
},
When I run pm2 start app.json it results in mode = cluster but I expect mode = fork
When I kill and re-run pm2 start app.json --env production it results in mode = cluster as expected but the number of workers does not equal number of cores.
I solved it by splitting out each environment into its own "app" within the JSON configuration file.
I have a simple command that works fine when run:
parse-dashboard --config /home/ubuntu/dash/config.json
However, when running it with pm2, it doesn't work:
pm2 start parse-dashboard -- --config=/home/ubuntu/dash/config.json
looking at the logs, i get the error:
node: bad option: --config=/home/ubuntu/dash/config.json
What am I doing wrong?
Use a process file where you specify the arguments. Create the following file and name it for example ecosystem.json (make sure the 'script' and 'cwd' (where the app will be launched) locations are correct for you))
{
"apps" : [{
"name" : "parse-dashboard-wrapper",
"script" : "/usr/bin/parse-dashboard",
"watch" : true,
"cwd" : "/home/parse/parse-dashboard",
"args" : "--config /home/ubuntu/dash/config.json"
}]
}
And run it with
pm2 start ecosystem.json