Email warning in cron logrotate

[lupo112]

I am still getting this email every day:

/etc/cron.daily/logrotate:
error: stat of /var/log/clamav/clamav.log failed: No such file or directory
run-parts: /etc/cron.daily/logrotate exited with return code 1

[bekce]

Hello, how do you get that error as an email? I use it in production but I dont receive any emails about server logs.

[lupo112]

Sender is root@mail.{my-domain} and recipient also root@mail.{my-domain}.

It started when i switched to your image instead of official poste.io docker image.

[ymarillet]

same "error" here

[danielj23]

Same here on the latest free version. I even have clamavdisabled=true configured

Sat Mar 14 00:17:14 2020 -> ClamAV update process started at Sat Mar 14 00:17:14 2020
Sat Mar 14 00:17:14 2020 -> daily database available for update (local version: 25738, remote version: 25750)
Sat Mar 14 00:17:19 2020 -> Testing database: '/data/var/clamav/tmp.4b732/clamav-7ee833e2f614438cde4ae4547785d5bb.tmp-daily.cld' ...
Sat Mar 14 00:17:25 2020 -> ^[LibClamAV] mpool_malloc(): Can't allocate memory (262144 bytes).
Sat Mar 14 00:17:25 2020 -> ^[LibClamAV] cli_ac_addpatt: Can't allocate memory for new->trans
Sat Mar 14 00:17:25 2020 -> ^[LibClamAV] cli_parse_add(): Problem adding signature (3).
Sat Mar 14 00:17:25 2020 -> ^[LibClamAV] Problem parsing database at line 98387
Sat Mar 14 00:17:25 2020 -> ^[LibClamAV] Can't load daily.ldb: Can't allocate memory
Sat Mar 14 00:17:25 2020 -> ^[LibClamAV] cli_tgzload: Can't load daily.ldb
Sat Mar 14 00:17:25 2020 -> ^[LibClamAV] Can't load /data/var/clamav/tmp.4b732/clamav-7ee833e2f614438cde4ae4547785d5bb.tmp-daily.cld: Malformed database
Sat Mar 14 00:17:25 2020 -> !Failed to load new database: Malformed database
Sat Mar 14 00:17:25 2020 -> !Database load killed by signal 11
Sat Mar 14 00:17:25 2020 -> !Database test FAILED.
Sat Mar 14 00:17:25 2020 -> !Unexpected error when attempting to update database: daily
Sat Mar 14 00:17:25 2020 -> ^fc_update_databases: fc_update_database failed: Test failed (8)
Sat Mar 14 00:17:25 2020 -> !Database update process failed: Test failed (8)
Sat Mar 14 00:17:25 2020 -> !Update failed.