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

Steve McIntyre steve.mcintyre at linaro.org
Tue Mar 26 15:56:30 GMT 2019

Hi Andreas,

On Sat, Mar 23, 2019 at 05:04:56PM +0100, Andreas Beckmann wrote:
>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

That sounds like a weird way to fix what's claimed to be a permissions
problem in the log. Or is this just a bad error message from logrotate?

And checking - the logrotate file in question already has 'missingok'

>*) 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.

I appreciate that you won't have this session around now to be able to
look directly, but for future reports it would be very helpful if
piuparts could show the logfiles and directories look like at this point.

Steve McIntyre                                steve.mcintyre at linaro.org
<http://www.linaro.org/> Linaro.org | Open source software for ARM SoCs

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