Pardon me for digging up an old thread, but im running into an issue with freshclam. Every hour i get an alert that freshclam is not running; while it show it's PID just fine in the service monitor. So it seems it cannot write the PID to /var/run/clamd/freshclam.pid.
freshclam.service - ClamAV updater daemon
Loaded: loaded (/etc/systemd/system/freshclam.service; enabled; vendor preset: disabled)
Active: failed (Result: timeout) since Fri 2019-03-08 12:29:51 CET; 9s ago
Process: 4365 ExecStart=/usr/local/bin/freshclam -d (code=exited, status=0/SUCCESS)
Process: 4362 ExecStartPre=/bin/chown -R clamav:clamav /var/run/clamd (code=exited, status=0/SUCCESS)
Process: 4361 ExecStartPre=/bin/mkdir -p /var/run/clamd (code=exited, status=0/SUCCESS)
Mar 08 12:28:20 mars.goadvised.com systemd[1]: Starting ClamAV updater daemon...
Mar 08 12:28:20 mars.goadvised.com systemd[1]: PID file /var/run/clamd/freshclam.pid not readable (yet?) after start.
Mar 08 12:29:51 mars.goadvised.com systemd[1]: freshclam.service start operation timed out. Terminating.
Mar 08 12:29:51 mars.goadvised.com systemd[1]: Failed to start ClamAV updater daemon.
Mar 08 12:29:51 mars.goadvised.com systemd[1]: Unit freshclam.service entered failed state.
Mar 08 12:29:51 mars.goadvised.com systemd[1]: freshclam.service failed.
The rights on the folder /var/run/clamd are clamav:clamav 0770, so it should be able to write there just fine. If i manually create a freshclam.pid, chown it with clamav:clamav and restart the freshclam service the file gets removed and throws the not readable error again. So i tried moving the file to /var/run/freshclam.pid in freshclam.conf and /etc/systemd/system/freshclam.service, all to no avail.
I an act of desperation i went and removed clamav altogether (./build set clamav no), update, rebuild, but it keeps throwing the same error.
i'm running out of ideas what to try here... any thoughts?
Kind regards, John.