On 07/04/2016 06:09 PM, Sebastian Andrzej Siewior wrote:
and you remained on Jessie, correct?
Yes, all three of my Debian servers are running Debian 8.5 as per the
/etc/debian_version files.
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
Yes, here are the results from one of my servers and which are
essentially the same as yours:
|$ mount|grep "run "
|tmpfs on /run type tmpfs (rw,nosuid,relatime,size=1632120k,mode=755)
|
|ls -l /var/ | grep "run "
|lrwxrwxrwx 1 root root 4 Jun 11 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
|
Yes, I have both of these service files and I previously posted the
"systemctl status" results for both services in my initial bug report.
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.
Exactly! The socket is not being started on either of my three debian
machines. Here is the contents of my clamav-daemon.socket file:
|cat /lib/systemd/system/clamav-daemon.socket
|[Unit]
|Description=Socket for Clam AntiVirus userspace daemon
|Documentation=man:clamd(8) man:clamd.conf(5)
http://www.clamav.net/lang/en/doc/
|# Check for database existence
|ConditionPathExistsGlob=/var/lib/clamav/main.{c[vl]d,inc}
|ConditionPathExistsGlob=/var/lib/clamav/daily.{c[vl]d,inc}
|
|[Socket]
|ListenStream=/run/clamav/clamd.ctl
|#ListenStream=127.0.0.1:1024
|SocketUser=clamav
|SocketGroup=clamav
|RemoveOnStop=True
|
|[Install]
|WantedBy=sockets.target
Please advise........
Gordon
