Clam AV Update Problem

I have just updated Clam AV via the VM repository . But now it won't start. I get:

May 25 09:09:46 systemd: Starting Socket for Clam AntiVirus userspace daemon.
May 25 09:09:46 systemd: Failed to chown socket at step USER: No such process
May 25 09:09:46 systemd: clamav-daemon.socket control process exited, code=exited status=217
May 25 09:09:46 systemd: Failed to listen on Socket for Clam AntiVirus userspace daemon.
May 25 09:09:46 systemd: Dependency failed for Clam AntiVirus userspace daemon.
May 25 09:09:46 systemd: Job clamav-daemon.service/start failed with result 'dependency'.
May 25 09:09:46 systemd: Unit clamav-daemon.socket entered failed state.



Assigned: » Unassigned
Category: Bug report » Support request
Status: Active » Closed (duplicate)
Status: Closed (duplicate) » Active

You may be missing some packages. What output do you get from the command :

rpm -qa | grep clam

I get these:

What output do you get if you run /etc/init.d/clamd.scan start ?

Joe's picture
Submitted by Joe on Fri, 05/27/2016 - 00:36 Pro Licensee

CentOS 7 is on systemd. So the command to start the scanner is:

# systemctl start clamd@scan
Joe's picture
Submitted by Joe on Fri, 05/27/2016 - 00:39 Pro Licensee

I'm rolling 0.99.2-3 to fix a couple of problems raised by folks; though there's something going on that I don't understand, as there's errors indicating clamav-daemon is trying to be started. clamd@scan works in the 0.99.2-2 packages, but clamav-daemon has some misconfiguration (clamav-daemon is a new service provided in the upstream tarball).

Anyway, new version may fix things. But, my systems are working fine using clamd@scan in the current packages. clamav-daemon keeps coming up, and I'm not sure what's calling that.

I think the update has helped. On the one hand "systemctl start clamd@scan" and "systemctl stop clamd@scan" seem to work. But the start/stop options on the Virtualmin status page do not work still.

Do you get any error message when you use the stop button?

Joe's picture
Submitted by Joe on Sat, 05/28/2016 - 01:25 Pro Licensee

Jamie, I'm seeing weirdness that I don't quite understand on the new package. I've forced installation of clamav-scanner and clamav-scanner-systemd (again, as I'm pretty sure we used to do this, but something regressed in virtualmin-base). But, I get the following error when enabling clamd:

ERROR: Could not lookup : Servname not supported for ai_socktype

----------- SCAN SUMMARY -----------
Infected files: 0
Time: 0.002 sec (0 m 0 s)

But, when I run it from the command line:

# clamdscan --config-file=/etc/clamd.d/scan.conf /etc/clamd.d/scan.conf
/etc/clamd.d/scan.conf: OK

----------- SCAN SUMMARY -----------
Infected files: 0
Time: 0.000 sec (0 m 0 s)

I see that there's code to handle adding the --config-file option when clamd@scan is used. But, maybe it's picking up some other configuration; these packages also have a clamav-daemon systemctl unit, which is shipped with the clamav upstream; I'm including it just in case folks want to follow the ClamAV docs to do other things with it. But, maybe it's confusing Virtualmin? I could pull it out of the packages, if necessary to resolve this issue.

I was also having this issued but a recent update appears to have fixed the issue. Oddly when I use the built in "enable clamAV server" key button it fails the first time but works the second. This gets it running in standalone mode.

Next I try to enable clamd and it errors the first time and works the second. Not sure if that helps.

I am running Debian 10 latest build.