logwatch --version
Logwatch 7.7 (released 07/22/22)
clamscan --version
ClamAV 1.0.5/27336/Sun Jul 14 08:33:25 2024
Ubuntu 24.04
The log snippet that I inserted (below line) was copied from an Ubuntu
22.04 server running ClamAV 0.103.11
"Fri Jul 12 11:38:56 2024 -> ClamAV update process started at Fri Jul 12
11:38:56 2024"
Looks like logwatch in my previous comment showed 0.103.11 because in
one of the tests I did, I may have previously included a line "Mon Jul
15 06:28:54 2024 -> freshclam daemon 0.103.11 (OS: ....", before
narrowing down to which line is actually required.
Replicated the bad "fix" again.
Steps:
1. nano /var/log/clamav/freshclam.log
2. Insert "Mon Jul 15 06:28:54 2024 -> ClamAV update process started at
Mon Jul 15 06:28:54 2024" so your log file looks like:
Mon Jul 15 06:35:59 2024 -> --------------------------------------
Mon Jul 15 06:28:54 2024 -> ClamAV update process started at Mon Jul 15
06:28:54 2024
Mon Jul 15 06:35:59 2024 -> daily.cld database is up-to-date (version: 27336,
sigs: 2064262, f-level: 90, builder: raynman)
Mon Jul 15 06:35:59 2024 -> main.cvd database is up-to-date (version: 62, sigs:
6647427, f-level: 90, builder: sigmgr)
Mon Jul 15 06:35:59 2024 -> bytecode.cvd database is up-to-date (version: 335,
sigs: 86, f-level: 90, builder: raynman)
3. Run logwatch with high detail
logwatch --detail high --range today | less
--------------------- clam-update Begin ------------------------
The ClamAV update process was started 1 time(s)
Last ClamAV update process started at Mon Jul 15 06:28:54 2024
Last Status:
daily.cld database is up-to-date (version: 27336, sigs: 2064262, f-level:
90, builder: raynman)
main.cvd database is up-to-date (version: 62, sigs: 6647427, f-level: 90,
builder: sigmgr)
bytecode.cvd database is up-to-date (version: 335, sigs: 86, f-level: 90,
builder: raynman)
---------------------- clam-update End -------------------------
4. Extra test: Remove the "ClamAV update process started" line from
freshclam.log and run logwatch again
logwatch --detail high --range today | less
--------------------- clam-update Begin ------------------------
No updates detected in the log for the freshclam daemon (the
ClamAV update process). If the freshclam daemon is not running,
you may need to restart it. Other options:
A. If you no longer wish to run freshclam, deleting the log file
(configured is /var/log/clamav/freshclam.log ) will suppress this error
message.
B. If you use a different log file, update the appropriate
configuration file. For example:
echo "LogFile = log_file" >> /etc/logwatch/conf/logfiles/clam-update.conf
where log_file is the filename of the freshclam log file.
C. If you are logging using syslog, you need to indicate that your
log file uses the syslog format. For example:
echo "*OnlyService = freshclam" >>
/etc/logwatch/conf/logfiles/clam-update.conf
echo "*RemoveHeaders" >> /etc/logwatch/conf/logfiles/clam-update.conf
---------------------- clam-update End -------------------------
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2067608
Title:
clamav-freshclam 1.0.5 and logwatch 7.7-1 fails to report
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/2067608/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
