debcrafters-packages team mailing list archive

[JUNG YING-REN <2067608@xxxxxxxxxxxxxxxxxx>]

Hi, Friends,

I find a new way to show logwatch result for clamav freshclam log in journalctl correctly.
I have removed apt package in UBUNTU, and I have switched to use logwatch-7.13 from opensource.


$ sudo nano /etc/logwatch/conf/services/clam-update.conf 
### Added by JIR 250830
LogFile =
LogFile = none
*JournalCtl = "--output=cat --unit=clamav-freshclam.service"


$ ls -al /etc/logwatch/scripts/services/clam-update
-rwxr-x--- 1 root root 224  8月 30 16:45 /etc/logwatch/scripts/services/clam-update
$ sudo nano /etc/logwatch/scripts/services/clam-update
#!/usr/bin/perl
### Added by JIR 250830
while (<STDIN>) {
    if (/ClamAV update process started/) {
        print $_;
    }
    elsif (/daily\.cld updated/) {
        print $_;
    }
    elsif (/Database test passed/) {
        print $_;


In this new configures, it may try this command:
$ sudo logwatch --output stdout --service clam-update
 ################### Logwatch 7.13 (07/22/25) #################### 
        Processing Initiated: Sat Aug 30 16:54:49 2025
        Date Range Processed: yesterday
                              ( 2025-Aug-29 )
                              Period is day.
        Detail Level of Output: 0
        Type of Output/Format: stdout / text
        Logfiles for Host: 
 ################################################################## 
 
 --------------------- clam-update Begin ------------------------ 

 ClamAV update process started at Fri Aug 29 00:00:33 2025
 Database test passed.
 Fri Aug 29 00:00:39 2025 -> daily.cld updated (version: 27746, sigs: 2076468, f-level: 90, builder: raynman)
 ClamAV update process started at Fri Aug 29 12:00:39 2025
 
 ---------------------- clam-update End ------------------------- 

 
 ###################### Logwatch End ######################### 


$ sudo logwatch --output stdout --service clam-update --range all
 ################### Logwatch 7.13 (07/22/25) #################### 
        Processing Initiated: Sat Aug 30 17:03:58 2025
        Date Range Processed: all
        Detail Level of Output: 0
        Type of Output/Format: stdout / text
        Logfiles for Host: 
 ################################################################## 
 
 --------------------- clam-update Begin ------------------------ 

 ClamAV update process started at Thu Aug  7 16:35:19 2025
 ClamAV update process started at Fri Aug  8 04:35:19 2025
 Database test passed.
 Fri Aug  8 04:35:26 2025 -> daily.cld updated (version: 27725, sigs: 2076396, f-level: 90, builder: raynman)
 ClamAV update process started at Fri Aug  8 16:35:26 2025
 ClamAV update process started at Sat Aug  9 04:35:26 2025
 Database test passed.
 Sat Aug  9 04:35:32 2025 -> daily.cld updated (version: 27726, sigs: 2076402, f-level: 90, builder: raynman)
.
... and so on ...
.
 ClamAV update process started at Thu Aug 28 12:00:33 2025
 ClamAV update process started at Fri Aug 29 00:00:33 2025
 Database test passed.
 Fri Aug 29 00:00:39 2025 -> daily.cld updated (version: 27746, sigs: 2076468, f-level: 90, builder: raynman)
 ClamAV update process started at Fri Aug 29 12:00:39 2025
 ClamAV update process started at Sat Aug 30 00:00:39 2025
 Database test passed.
 Sat Aug 30 00:00:46 2025 -> daily.cld updated (version: 27747, sigs: 2076429, f-level: 90, builder: raynman)
 ClamAV update process started at Sat Aug 30 12:00:46 2025
 
 ---------------------- clam-update End ------------------------- 

 
 ###################### Logwatch End ######################### 


The new call way is felt as same as my expected result:
$ sudo journalctl --unit=clamav-freshclam.service --since yesterday --output=cat | /etc/logwatch/scripts/services/clam-update
ClamAV update process started at Fri Aug 29 00:00:33 2025
Database test passed.
Fri Aug 29 00:00:39 2025 -> daily.cld updated (version: 27746, sigs: 2076468, f-level: 90, builder: raynman)
ClamAV update process started at Fri Aug 29 12:00:39 2025
ClamAV update process started at Sat Aug 30 00:00:39 2025
Database test passed.
Sat Aug 30 00:00:46 2025 -> daily.cld updated (version: 27747, sigs: 2076429, f-level: 90, builder: raynman)
ClamAV update process started at Sat Aug 30 12:00:46 2025

-- 
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:
  Triaged
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