-
Notifications
You must be signed in to change notification settings - Fork 152
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
Don't log service logs to ~/.pm2/logs/ #376
Labels
Comments
matthew-white
added
help wanted
good first issue
ops
Docker, ops to deploy Central
labels
Jan 6, 2023
As of #422, pm2.config.js can be found in the central-backend repo. |
Hi @matthew-white , Please review the PR for changes to this issue. |
venkatsaid
added a commit
to venkatsaid/getodk_central-backend
that referenced
this issue
Oct 20, 2024
venkatsaid
added a commit
to venkatsaid/getodk_central-backend
that referenced
this issue
Oct 20, 2024
Update pm2.config.js for Don't log service logs pm2_logs getodk/central/issues/376
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In #293, we stopped pm2 from double-logging to stdout/stderr. However, it logs like pm2 is now logging to ~/.pm2/logs/ in the service container in addition to stdout/stderr. We don't use the logs in ~/.pm2/logs/, so those logs end up taking up space they don't need to.
From a quick look, it looks like we can stop the logging to ~/.pm2/logs/ by setting
out_file
anderror_file
to /dev/null: see the "Disable logging" section here. This page similarly indicates that the default ofout_file
anderror_file
is logging to ~/.pm2/logs/.The text was updated successfully, but these errors were encountered: