debcrafters-packages team mailing list archive
-
debcrafters-packages team
-
Mailing list archive
-
Message #09463
[Bug 2067608] Re: clamav-freshclam 1.0.5 and logwatch 7.7-1 fails to report
So the fix for this bug would be reinserting the line back in freshclam.log, at least on stable releases.
The curious thing is that the message appears in version 0.103.12+dfsg-0ubuntu0.20.04.1 on Focal (a backport), but does not appear in version 0.103.5+dfsg-1 on Jammy, which is older :|
I suspect something else changed from 20.04 to 22.04, not necessarily with the clamav package itself. Still under investigation.
--
You received this bug notification because you are a member of
Debcrafters packages, which is subscribed to logwatch in Ubuntu.
https://bugs.launchpad.net/bugs/2067608
Title:
clamav-freshclam 1.0.5 and logwatch 7.7-1 fails to report
Status in clamav package in Ubuntu:
Triaged
Status in logwatch package in Ubuntu:
Confirmed
Status in clamav source package in Noble:
Confirmed
Status in logwatch source package in Noble:
Confirmed
Status in clamav source package in Oracular:
Won't Fix
Status in logwatch source package in Oracular:
Won't Fix
Status in clamav source package in Plucky:
Confirmed
Status in logwatch source package in Plucky:
Confirmed
Status in clamav source package in Questing:
In Progress
Status in logwatch source package in Questing:
Confirmed
Bug description:
$ lsb_release -rd
No LSB modules are available.
Description: Ubuntu 24.04 LTS
Release: 24.04
$ apt-cache policy clamav-freshclam
clamav-freshclam:
Installed: 1.0.5+dfsg-1.1ubuntu3
Candidate: 1.0.5+dfsg-1.1ubuntu3
Version table:
*** 1.0.5+dfsg-1.1ubuntu3 500
500 http://us.archive.ubuntu.com/ubuntu noble/main amd64 Packages
100 /var/lib/dpkg/status
$ apt-cache policy logwatch
logwatch:
Installed: 7.7-1ubuntu1
Candidate: 7.7-1ubuntu1
Version table:
*** 7.7-1ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu noble/main amd64 Packages
500 http://us.archive.ubuntu.com/ubuntu noble/main i386 Packages
100 /var/lib/dpkg/status
Expect that daily logwatch emails properly show clamav update
information.
I believe that this problem started around the time clamav went to
version 1.0.x.
Excerpt from daily logwatch email report...
--------------------- 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 -------------------------
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: clamav-freshclam 1.0.5+dfsg-1.1ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu May 30 05:54:37 2024
InstallationDate: Installed on 2021-09-25 (978 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
SourcePackage: clamav
UpgradeStatus: Upgraded to noble on 2024-05-25 (5 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/2067608/+subscriptions