I get an email every day with the following:

 

error: skipping "/var/log/docker.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/syslog" 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/vsftpd.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/wtmp" 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/btmp" 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.

 

Also reported many times elsewhere:

 

http://lime-technology.com/forum/index.php?topic=36527.msg339961#msg339961

http://lime-technology.com/forum/index.php?topic=36527.msg339963#msg339963

http://lime-technology.com/forum/index.php?topic=36527.msg339973#msg339973

http://lime-technology.com/forum/index.php?topic=36527.msg339985#msg339985

http://lime-technology.com/forum/index.php?topic=36527.msg341657#msg341657

http://lime-technology.com/forum/index.php?topic=37201.msg343880#msg343880

 

Help? Advice?

 

[update]

How to fix:

https://linuxslut.net/logrotate-parent-directory-has-insecure-permissions/

https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1278193

https://www.novell.com/support/kb/doc.php?id=7005219

 

I added “su root root” to the bottom of of each file in /etc/logrotate.d.  Example in attached image.

 

I think it is also possible to address this via “/etc/logrotate.conf” and possibly that is the only file that needs editing.  I just didn’t want to break everything. 

 

Of course the changes are lost if you reboot. 

I'm getting the exact same email - would like to know if there is a neater way to solve rather than copying each logrotate.d entry over via the go script.

I hope another beta is due soon with the fix included.  Seems like it's been a good while since the last one.