Topic: Logwatch clam-update no output
==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 1.3.2
- Deployed with iRedMail Easy or the downloadable installer? Downloadable Installer
- Linux/BSD distribution name and version: Debian GNU/Linux 10 (buster) [x86_64]
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL/MariaDB
- Web server (Apache or Nginx): Nginx
- Manage mail accounts with iRedAdmin-Pro? No
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====
There ist no output of clam-update in the logwatch mail.
Even with --detail high nothing is to see:
logwatch --service clam-update --detail high
The output is nothing no error message none.
Last entries in file /var/log/clamav/fresh-clam.log are:
Sun Nov 8 19:00:15 2020 -> Received signal: wake up
Sun Nov 8 19:00:15 2020 -> ClamAV update process started at Sun Nov 8 19:00:15 2020
Sun Nov 8 19:00:15 2020 -> daily.cld database is up to date (version: 25982, sigs: 4339785, f-level: 63, builder: raynman)
Sun Nov 8 19:00:15 2020 -> main.cvd database is up to date (version: 59, sigs: 4564902, f-level: 60, builder: sigmgr)
Sun Nov 8 19:00:15 2020 -> bytecode.cvd database is up to date (version: 331, sigs: 94, f-level: 63, builder: anvilleg)
Sun Nov 8 19:00:15 2020 -> --------------------------------------
/var/log/clamav/fresh-clam.log is found in /usr/share/logwatch/
# What actual file? Defaults to LogPath if not absolute path.... (suppose LogPath is /var/log/)
LogFile = clam-update
LogFile = freshclam.log
LogFile = clamav/freshclam.log
----
Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.