Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#51638 - [gitlab] logrotate permissions problem
Attached to Project:
Community Packages
Opened by Pavol Hluchý (Lopo) - Wednesday, 02 November 2016, 10:09 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Saturday, 05 November 2016, 17:15 GMT
Opened by Pavol Hluchý (Lopo) - Wednesday, 02 November 2016, 10:09 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Saturday, 05 November 2016, 17:15 GMT
|
DetailsDescription:
logrotate permissions problem logrotate[1289]: error: skipping "/var/log/gitlab/production.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. Solution: add line into gitlab.logrotate conf: su gitlab gitlab |
This task depends upon
Closed by Sven-Hendrik Haase (Svenstaro)
Saturday, 05 November 2016, 17:15 GMT
Reason for closing: Fixed
Saturday, 05 November 2016, 17:15 GMT
Reason for closing: Fixed
Comment by Sven-Hendrik Haase (Svenstaro) -
Saturday, 05 November 2016, 15:18 GMT
This should already be fixed for new installations because gitlab-shell creates that directory with gitlab:root so it should be good and this change shouldn't be necessary.