Public bug reported:
# lsb_release -rd
Description: Ubuntu 20.04 LTS
Release: 20.04
# apt-cache policy logwatch
logwatch:
Installed: 7.5.2-1ubuntu1
Candidate: 7.5.2-1ubuntu1
*** What I expected to happen:
Setting
logwatch: Archives = No
in /etc/logwatch/conf/override.conf would not stop the fail2ban logwatch
report from doing anything as the range is the default of 'yesterday'.
*** What happened instead:
Fail2ban isn't in the produced report.
*** Thoughts
The defaults in /usr/share/logwatch/default.conf/logwatch.conf say
# Use archives? If set to 'Yes', the archives of logfiles
# (i.e. /var/log/messages.1 or /var/log/messages.1.gz) will
# be searched in addition to the /var/log/messages file.
# This usually will not do much if your range is set to just
# 'Yesterday' or 'Today'... it is probably best used with Range = All
# By default this is now set to Yes. To turn off Archives uncomment this.
#Archives = No
# The default time range for the report...
# The current choices are All, Today, Yesterday
Range = yesterday
..and it's been fine overriding the Archives setting in Debian Stable,
right up to Debian Buster. But not in Ubuntu Focal.
ls -lha /var/log/fail* produces:
-rw-r----- 1 root adm 397K May 10 17:19 /var/log/fail2ban.log
-rw-r----- 1 root adm 2.5M May 9 23:56 /var/log/fail2ban.log.1
.. so there *is* a non-archived file in /var/log, but unless I do not
override the Archives setting, the fail2ban section does not appear in
the report.
I've no idea why not.
** Affects: logwatch (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877880
Title:
Setting 'Archives = No' breaks fail2ban service somehow
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1877880/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
