#4 CentOS8: No dnf-rpm results reported

[Scott D-S]

Logwatch 7.5.4 (07/22/20)

Not receiving dnf results in the nighly summary E-mail on multiple CentOS 8 hosts, despite the existence of the /var/log/dnf.rpm.log file.

I have been using logwatch for years without having to ever do any special configuration, but didn't want to report this as a "bug" until I was sure I hadn't missed something in the setup.

[Scott D-S]

FYI, running logwatch interactively for just dnf-rpm produces no results:

logwatch --detail=Med --range=Yesterday --output stdout --service dnf-rpm
logwatch --detail=High --range=Yesterday --output stdout --service dnf-rpm

If I try calling the specific log file I get:

logwatch --detail=Med --range=Yesterday --output stdout --logfile /var/log/dnf.rpm.log
Logwatch is not configured to use logfile: /var/log/dnf.rpm.log

But according to /usr/share/logwatch/default.conf/logfiles/dnf-rpm.conf:
LogFile = dnf.rpm.log
Archive = dnf.rpm.log-*

I am happy to provide any additional debugging/testing/logging would be of assistance...

[Frank Crawford]

Scott, I'll have a look at this over the next few days, as it used to work, and I believe should still be working.

[Scott D-S]

I think I may have figured out where I did myself in.

CentOS 8 includes logwatch 7.4.3-9 in the base repositories, which I initially used for several installs. After discovering the yum/dnf issue, I moved to downloading the RPM directly from the project and performing a local install instead. This works when it's a new/clean installation.

It appears to be breaking down when I simply perform a local update over the older package. If I first remove the old version (and any stranded configuration files), then perform a local install of the new version everything works as expected.

I knew it had to be something dumb on my part. Hopefully this will help keep someone else out of the weeds...