This repository has been archived by the owner on Dec 8, 2017. It is now read-only.
Fix logrotate issue with logs going to wrong file #46
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Noticed that there was a new `/var/log/18f-pages-server/pages.log` file, but that the logs were still going to an uncompressed `/var/log/18f-pages-server/pages.log.1`. The old `postrotate` script wasn't actually successfully restarting the server, and a manual restart also didn't allow the new process to write to the new log file. Found out about the `copytruncate` directive, which will work well enough for 18F Pages, though it's not completely ideal. For more information, this issue has a very helpful comment with a ton of technical background: foreversd/forever#106 (comment)
mbland
added a commit
that referenced
this pull request
Oct 1, 2015
Fix logrotate issue with logs going to wrong file
nihonjinrxs
pushed a commit
to nihonjinrxs/data-driven-government
that referenced
this pull request
Jul 2, 2016
Add CONTRIBUTING.md
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Noticed that there was a new
/var/log/18f-pages-server/pages.logfile, butthat the logs were still going to an uncompressed
/var/log/18f-pages-server/pages.log.1. The oldpostrotatescript wasn'tactually successfully restarting the server, and a manual restart also didn't
allow the new process to write to the new log file.
Found out about the
copytruncatedirective, which will work well enough for18F Pages, though it's not completely ideal. For more information, this issue
has a very helpful comment with a ton of technical background:
foreversd/forever#106 (comment)