[Pkg-clamav-devel] Bug#829597: Bug#829597: clamav-daemon: LocalSocket not created.
Sebastian Andrzej Siewior
sebastian at breakpoint.cc
Mon Jul 4 22:09:54 UTC 2016
On 2016-07-04 10:37:01 [-0400], Gordon Dickens wrote:
> Dear Maintainer,
Hi Gordon,
> I just upgraded three Debian exim mail servers from clamav 0.99 to clamav 0.99.2 and now all three mail servers are broken. That is, I have LocalSocket defined in /etc/clamav/clamd.conf as follows:
and you remained on Jessie, correct?
> LocalSocket /var/run/clamav/clamd.ctl
>
> However, the /var/run/clamav/clamd.ctl socket is never created on any of the three systems. Furthermore, the /var/run/clamav directory is never created at boot time either. So, could this be a systemd issue? The bottom line is that clamav is now totally broken which has subsequently broken exim's virus checking as well. freshclam reports the following in /var/log/freshclam.log:
You should have /run which is a tmpfs:
|$ mount|grep "run "
|tmpfs on /run type tmpfs (rw,nosuid,relatime,size=1607508k,mode=755)
and /var/run should be a symlink:
|$ ls -l /var/ | grep "run "
|lrwxrwxrwx 1 root root 4 Aug 3 2013 run -> /run
and since you run systemd there should be two service files:
|# systemctl status clamav-daemon.socket
|● clamav-daemon.socket - Socket for Clam AntiVirus userspace daemon
| Loaded: loaded (/lib/systemd/system/clamav-daemon.socket; enabled)
| Drop-In: /etc/systemd/system/clamav-daemon.socket.d
| └─extend.conf
| Active: active (running) since Thu 2016-05-26 22:35:00 CEST; 1 months 8 days ago
| Docs: man:clamd(8)
| man:clamd.conf(5)
| http://www.clamav.net/lang/en/doc/
| Listen: /var/run/clamav/clamd.ctl (Stream)
|
|Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
|# systemctl status clamav-daemon.service
|● clamav-daemon.service - Clam AntiVirus userspace daemon
| Loaded: loaded (/lib/systemd/system/clamav-daemon.service; enabled)
| Active: active (running) since Thu 2016-05-26 22:35:00 CEST; 1 months 8 days ago
| Docs: man:clamd(8)
| man:clamd.conf(5)
| http://www.clamav.net/lang/en/doc/
| Main PID: 11021 (clamd)
| CGroup: /system.slice/clamav-daemon.service
| └─11021 /usr/sbin/clamd --foreground=true
|
If you read the .socket file then you will see that one creates the
socket and the .service file depends on it. Uppon start, systemd passes
the socket to clamd then. I *assume* that the socket part is not started
for some reason on your machines.
Sebastian
More information about the Pkg-clamav-devel
mailing list