Package: logrotate
Version: 3.14.0-4
Severity: important
Tags: patch
Dear Maintainer,
the logrotate.service failed when started by the systemd under the following
conditions:
- There is no graphical target but the system runs to multi-user.target,
- The system was not started for a few days,
- The logrotate service was started at boot time, maybe triggered by the
stand still period,
- The /var directory is separated to a dedicated md device.
There was no error after manually starting the service at the command line
when the system was up.
If you don't wish that users will be faced by error messages at boot time it
would be help to complete the unit description in the file
/lib/systemd/system/logrotate.service by simply add the following statement
to the unit section: After=local-fs.target.
This statement is also missing in the unstable package
logrotate_3.16.0-3_amd64.deb.
Best Regards
T. Heinrich
-- Package-specific info:
Contents of /etc/logrotate.d
total 28
-rw-r--r-- 1 root root 120 Apr 19 2019 alternatives
-rw-r--r-- 1 root root 173 May 28 2019 apt
-rw-r--r-- 1 root root 130 Aug 29 2018 btmp
-rw-r--r-- 1 root root 112 Apr 19 2019 dpkg
-rw-r--r-- 1 root root 501 Feb 26 2019 rsyslog
-rw-r--r-- 1 root root 340 Jul 24 2019 squid
-rw-r--r-- 1 root root 145 Feb 19 2018 wtmp
-- System Information:
Debian Release: 10.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages logrotate depends on:
ii cron [cron-daemon] 3.0pl1-134+deb10u1
ii libacl1 2.2.53-4
ii libc6 2.28-10
ii libpopt0 1.16-12
ii libselinux1 2.8-1+b1
ii systemd-sysv 241-7~deb10u4
Versions of packages logrotate recommends:
pn bsd-mailx | mailx <none>
logrotate suggests no packages.
-- no debconf information
