I have also experienced the failure of clamav-daemon a couple of weeks back.
In older qmailtoaster installations clamd was run under supervise, not the case anymore. Don’t know when and why the change happened. Biju Jose From: Jeff Koch [mailto:jeffk...@intersessions.com] Sent: 19 November 2019 07:24 To: qmailtoaster-list@qmailtoaster.com; Eric Broch <ebr...@whitehorsetc.com> Subject: [qmailtoaster] Solved - Re: [qmailtoaster] update soft-reject - clamd won't start I added swap memory to the server and the following line will restart clamd systemctl start clamav-daemon to control clamd Still don't know why after running for a month the mailserver should run our of memory. Jeff On 11/18/2019 8:30 PM, Jeff Koch wrote: I found this in the /var/log/messages/ - 3:10pm is about when clamd stopped Could there be a memory leak? Jeff Nov 18 15:09:59 vidar clamd: Mon Nov 18 15:09:59 2019 -> ~/var/qmail/simscan/1574107789.220621.20708/im age001.png: OK Nov 18 15:10:12 vidar kernel: [ 798] 46 798 21123 365 45 0 0 fres hclam Nov 18 15:10:12 vidar kernel: [ 803] 46 803 433606 330432 784 0 0 clam d Nov 18 15:10:13 vidar kernel: [20682] 89 20682 10154 136 24 0 0 clam dscan Nov 18 15:10:13 vidar kernel: [20756] 89 20756 10154 137 25 0 0 clam dscan Nov 18 15:10:13 vidar kernel: Out of memory: Kill process 803 (clamd) score 165 or sacrifice child Nov 18 15:10:13 vidar kernel: Killed process 803 (clamd), UID 46, total-vm:1734424kB, anon-rss:1321804k B, file-rss:0kB, shmem-rss:0kB Nov 18 15:10:13 vidar systemd: clamav-daemon.service: main process exited, code=killed, status=9/KILL Nov 18 15:10:13 vidar systemd: Unit clamav-daemon.service entered failed state. Nov 18 15:10:13 vidar systemd: clamav-daemon.service failed.
