package: logrotate version: 3.7.8-6 x-debbugs-cc: 566...@bugs.debian.org, evg...@debian.org
Hi, piuparts.debian.org since some time tests for failing logrotate runs of packages, the results are at http://piuparts.debian.org/sid/logrotate_error_after_removal_error.html Looking at http://piuparts.debian.org/sid/fail/munge_0.5.9-2.log the relevant lines are: 0m10.8s DEBUG: Starting command: ['chroot', '/org/piuparts.debian.org/tmp/tmpk8ojpT', '/usr/sbin/logrotate', '/etc/logrotate.d/munge'] 0m10.8s DUMP: error: error accessing /var/log/munge: No such file or directory error: /etc/logrotate.d/munge:1 glob failed for /var/log/munge/*.log error: found error in /var/log/munge/*.log , skipping Now let's look at munges logrotate file: $ cat /etc/logrotate.d/munge /var/log/munge/*.log { rotate 12 weekly compress missingok postrotate /usr/sbin/invoke-rc.d --quiet munge force-reload >/dev/null endscript } So when piuparts tests the package it doesn't run munge (in this example) and thus /var/log/munge/ never gets created... I have come to think this is a bug in logrotate as the config file specifies "missingok" and the log file is missing. Do you agree? cheers, Holger
signature.asc
Description: This is a digitally signed message part.
