Don't know if this info will help fix the bug, but here goes.
The below log entry must exist in freshclam.log for logwatch to be able
to decipher it:
"Fri Jul 12 11:38:56 2024 -> ClamAV update process started at Fri Jul 12
11:38:56 2024"
Tested this by manually editing and adding it to freshclam.log and then
running logwatch.
freshclam.log :
Fri Jul 12 12:32:24 2024 -> --------------------------------------
Fri Jul 12 11:38:56 2024 -> ClamAV update process started at Fri Jul 12
11:38:56 2024
Fri Jul 12 12:32:24 2024 -> daily.cld database is up-to-date (version: 27334,
sigs: 2064183, f-level: 90, builder: raynman)
Fri Jul 12 12:32:24 2024 -> main.cvd database is up-to-date (version: 62, sigs:
6647427, f-level: 90, builder: sigmgr)
Fri Jul 12 12:32:24 2024 -> bytecode.cvd database is up-to-date (version: 335,
sigs: 86, f-level: 90, builder: raynman)
Logwatch :
--------------------- clam-update Begin ------------------------
The following version(s) of the freshclam daemon were started
0.103.11 (OS: linux-gnu, ARCH: x86_64, CPU: x86_64): 1 Time(s)
The ClamAV update process was started 1 time(s)
Last ClamAV update process started at Fri Jul 12 11:38:56 2024
Last Status:
daily.cld database is up-to-date (version: 27334, sigs: 2064183, 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 -------------------------
--
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
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
