Package: fail2ban
Version: 0.10.2-2.1
Severity: important
Tags: patch
Control: affects -1 logrotate
Hi,
Some times (observed on slow virtual hardware) logrotate.service fails to start
during boot, because the fail2ban logrotate configuration calls fail2ban-client
flushlogs and that fails because fail2ban is not yet started.
Prpoposed fixes:
* make fail2ban service start before logrotate by putting
WantedBy=logrotate.service
in the [Install] section of fail2ban.service
* make the fail2ban-client failure non-fatal by adding "|| true"
I am currently implementing the first suggestion, because the second feels like
hiding problems.
Thanks for considering,
Damyan
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'oldoldstable'), (500,
'unstable'), (500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.2.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=bg_BG.UTF-8, LC_CTYPE=bg_BG.UTF-8 (charmap=UTF-8),
LANGUAGE=bg_BG.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages fail2ban depends on:
ii lsb-base 11.1.0
ii python3 3.7.3-1
Versions of packages fail2ban recommends:
ii iptables 1.8.3-2
ii nftables 0.9.1-3
ii python 2.7.16-1
ii python3-pyinotify 0.9.6-1.2
pn python3-systemd <none>
ii whois 5.5.1
Versions of packages fail2ban suggests:
ii bsd-mailx [mailx] 8.1.2-0.20180807cvs-1+b1
pn monit <none>
ii rsyslog [system-log-daemon] 8.1908.0-1
ii sqlite3 3.29.0-2
-- debconf-show failed
