-
Notifications
You must be signed in to change notification settings - Fork 2.6k
pm2 logging takes free space on AWS EC2 instance #2997
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Is the problem applications logs or PM2 logs ? Because it should not output any log with your current configuration. |
Have you tried to disable the logs: http://pm2.keymetrics.io/docs/usage/application-declaration/#disabling-logs |
You can try the --disable-logs option:
|
Published on PM2 2.6.0: $ npm install pm2@latest -g
$ pm2 update
$ pm2 start xxx.js --disable-logs |
Hi ,
Thank you for addressing the issue. I will try your suggestion.
|
Tried to modify pm2 logging according to http://pm2.keymetrics.io/docs/usage/log-management/:
by running the app with the following scripts in package.json:
"start": "node ./node_modules/.bin/pm2 start index.js",
"poststart": "node ./node_modules/.bin/pm2 logs --output "/dev/null" --error "/dev/null"",
This did not help much - after a day 1.5GB of logging.
There is a section in this document named "JSON way", however it is not clear where (which file) this JSON should be used.
We need to disable logs, not manage via logrotate.
The text was updated successfully, but these errors were encountered: