Change nginx log directory owner to fix log rotation #8
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.
Prior to this change,
/var/log/nginx
was owned byroot
. This resulted in a broken log rotation where nginx worker processes would continue to write to a rotated fileaccess.log.1
with no further rotation until there's no disk space left. New log fileaccess.log.0
would remain empty.Changing the owner user to
www-data
so that it correlates with nginx and logrotate config files resolves the issue. Usually instances don't last long enough for this to be a problem, however it's been observed on fewmeter-points-service
instances.Tested with Vagrant, got no errors related to the change:
==> webhookserver: Notice: /Stage[main]/Octo_nginx/File[nginx log dir]/owner: owner changed 'root' to 'www-data'
Tested on an api-server instance on oegb-test after CIS hardening cron job kicks in: