I was going through my logs and this kept on popping up.  It seems every 4-5 hours clamav-demon crashes or stops working. After doing some looking around I found a number of websites mention there is a bug in clamav-demon that hasn't been resolved yet.  I'm wondering if simply setting up a cron to restart clamav every few hours would be a temp fix until a fix is released.

I'm on Debian 9

May 15 18:02:00 cetus amavis[13242]: (13242-08) (!)connect to /var/run/clamav/clamd.ctl failed, attempt #1: Can't connect to a UNIX socket /var/run/clamav/clamd.ctl: Connection refused May 15 18:02:01 cetus amavis[13242]: (13242-08) (!)connect to /var/run/clamav/clamd.ctl failed, attempt #1: Can't connect to a UNIX socket /var/run/clamav/clamd.ctl: Connection refused May 15 18:02:01 cetus amavis[13242]: (13242-08) (!)ClamAV-clamd: All attempts (1) failed connecting to /var/run/clamav/clamd.ctl, retrying (2) May 15 18:02:07 cetus amavis[13242]: (13242-08) (!)connect to /var/run/clamav/clamd.ctl failed, attempt #1: Can't connect to a UNIX socket /var/run/clamav/clamd.ctl: Connection refused May 15 18:02:07 cetus amavis[13242]: (13242-08) (!)ClamAV-clamd av-scanner FAILED: run_av error: Too many retries to talk to /var/run/clamav/clamd.ctl (All attempts (1) failed connecting to /var/run/clamav/clamd.ctl) at (eval 98) line 613.\n May 15 18:02:07 cetus amavis[13242]: (13242-08) (!)WARN: all primary virus scanners failed, considering backups

Phil

Reply via email to