Bug 583298 – net-analyzer/icinga2-2.4.4-r1: logrotate ALERT exited abnormally with [1]

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description WOLfgang Schricker 2016-05-17 14:19:01 UTC]

My fcron runs and /var/log/message brings:

2016-05-16T03:10:00+00:00 myhost run-crons[9575]: (root) CMD (/etc/cron.daily/logrotate)
2016-05-16T03:10:00+00:00 myhost logrotate[9578]: ALERT exited abnormally with [1]


Reproducible: Always

Steps to Reproduce:
Run as root:

# /etc/cron.daily/logrotate
error: skipping "/var/log/icinga2/icinga2.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.
error: skipping "/var/log/icinga2/debug.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.
error: skipping "/var/log/icinga2/error.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.
Actual Results:  
I don't know the way from /var/tmp/portage/net-analyzer/icinga2-2.4.4-r1/work/icinga2-2.4.4/etc/logrotate.d/icinga2.cmake to /etc/logrotate.d/icinga2.


I attach a patch but >=logrotate-3.8.0 is required.
See the "su option" in https://svn.fedorahosted.org/svn/logrotate/tags/r3-8-0/CHANGES

[Comment 1 WOLfgang Schricker 2016-05-17 14:20:41 UTC]

Created attachment 434538 [details, diff]
icinga2-logrotate-su.patch

>=logrotate-3.8.0 required

[Comment 2 Matthew Thode ( prometheanfire ) 2016-05-22 22:59:30 UTC]

fixed as 2.4.10-r1