[Pkg-linaro-lava-devel] Bug#925353: lava-server: logrotate complains about "parent directory has insecure permissions"

Andreas Beckmann anbe at debian.org
Sat Mar 23 16:04:56 GMT 2019

Package: lava-server
Version: 2019.01-4
Severity: serious
User: debian-qa at lists.debian.org
Usertags: piuparts
Control: found -1 2014.09.1-1+deb8u1


during a test with piuparts I noticed your package's logrotate
configuration causes logrotate to exit with an error after the package
has been removed (*) or when logrote is run but no logfile exists.

Usually the solution is to specify 'missingok' in the logrotate

*) logrotate configuration files remain installed and executed after a
package has been removed, they only get removed when the package is

>From the attached log (scroll to the bottom...):

6m50.2s ERROR: Command failed (status=1): ['chroot', '/srv/piuparts/tmp/tmpML5ulV', '/usr/sbin/logrotate', '/etc/logrotate.d/lava-server-uwsgi-log']
  error: skipping "/var/log/lava-server/lava-uwsgi.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.

This was observed on an upgrade test from jessie to stretch to buster.
It does not seem to happen on just stretch->buster upgrades.



More information about the Pkg-linaro-lava-devel mailing list