[Pkg-clamav-devel] Bug#1019361: clamav-daemon: cron job fails

[Sebastian Andrzej Siewior]

On 2022-09-07 15:26:44 [-0500], Tim McConnell wrote:
> --log="$HOME/.clamtk/history/$(date +\%b-\%d-\%Y).log" 2>/dev/null # clamtk-
> scan"
>      Loaded: loaded (/var/spool/cron/crontabs/tmick; generated)
>      Active: failed (Result: exit-code) since Wed 2022-09-07 04:39:26 CDT; 1s
> ago
> TriggeredBy: ● cron-tmick-tmick-0.timer
>        Docs: man:systemd-crontab-generator(8)
>     Process: 25146 ExecStart=/bin/sh /run/systemd/generator/cron-tmick-
> tmick-0.sh (code=exited, status=1/FAILURE)
>    Main PID: 25146 (code=exited, status=1/FAILURE)
>         CPU: 3h 52min 16.894s
> 
> Sep 07 04:39:25 DebianTim sh[25149]: Data scanned: 56848.61 MB
> Sep 07 04:39:25 DebianTim sh[25149]: Data read: 375263.33 MB (ratio 0.15:1)
> Sep 07 04:39:25 DebianTim sh[25149]: Time: 16825.735 sec (280 m 25 s)
> Sep 07 04:39:25 DebianTim sh[25149]: Start Date: 2022:09:06 23:59:00
> Sep 07 04:39:25 DebianTim sh[25149]: End Date:   2022:09:07 04:39:25
> Sep 07 04:39:26 DebianTim systemd[1]: cron-tmick-tmick-0.service: Main process
> exited, code=exited, status=1/FAILURE
> Sep 07 04:39:26 DebianTim systemd[1]: cron-tmick-tmick-0.service: Failed with
> result 'exit-code'.
…
> How do I fix the report/ cron job??

This does not appear be a clamav/clamscan problem. It run for almost
four hours and then quit. Please consult the logfile for the results.
clamscan should exit with 2 on error, 1 if infected files were found and
0 on success (everything was fine, nothing found).
Systemd assumes exitcode != 0 is an error.

Sebastian