ClamAV won't start

Phil.RRR · May 7, 2013, 3:17pm

I’ve just signed up for a new VPS (which uses Parallels Virtuozzo) today with Debian 6 on it, I’ve installed Virtualmin via the install.sh script and it all seems to have gone OK except for ClamAV - when I click ‘Enable ClamAV server’ I get the following:

Enable Virus Scanning Server
Configuring and enabling the ClamAV scanning server …
Starting ClamAV server and enabling at boot …
… failed to start : Starting ClamAV daemon: clamd /etc/init.d/clamav-daemon: line 327: 26672 Killed start-stop-daemon --start -o -c $User --exec $DAEMON failed!
… all done

I get something similar when trying to start it via the command line:

/etc/init.d/clamav-daemon start

Starting ClamAV daemon: clamd /etc/init.d/clamav-daemon: line 327: 30527 Killed start-stop-daemon --start -o -c $User --exec $DAEMON
failed!

Any ideas?

Thanks

Phil

Eric · May 7, 2013, 7:06pm

Howdy,

Do you see any errors in /var/log/mail.log when trying to start Clam?

Also, can you paste in the contents of /proc/user_beancounters?

-Eric

Phil.RRR · May 8, 2013, 7:23am

Hi Eric

The mail log doesn’t seem to show anything when I try and start ClamAV - I used ‘tail’ to look at the most recent entries both before and after trying to start it and it was the same.

The contents of user_beancounters is as follows:

cat /proc/user_beancounters

Version: 2.5
uid resource 7267898: kmemsize lockedpages 0 privvmpages 157140 shmpages 1082 dummy 0 numproc 67 physpages 76597 vmguarpages 0 oomguarpages 71833 numtcpsock 24 numflock 8 numpty 1 numsiginfo 0 tcpsndbuf 542952 tcprcvbuf 393216 othersockbuf 254320 dgramrcvbuf 0 numothersock 226 dcachesize 5519563 numfile 2295 dummy 0 dummy 0 dummy 0 numiptent 18 held maxheld barrier limit failcnt
17801974 20029440 9223372036854775807 9223372036854775807 0
0 117964 117964 0
160124 9223372036854775807 9223372036854775807 0
1082 9223372036854775807 9223372036854775807 0
0 9223372036854775807 9223372036854775807 0
117 9223372036854775807 9223372036854775807 0
82440 117964 117964 4
0 117964 117964 0
71833 117964 117964 4
24 9223372036854775807 9223372036854775807 0
8 9223372036854775807 9223372036854775807 0
1 9223372036854775807 9223372036854775807 0
45 9223372036854775807 9223372036854775807 0
542952 9223372036854775807 9223372036854775807 0
393216 9223372036854775807 9223372036854775807 0
254320 9223372036854775807 9223372036854775807 0
0 9223372036854775807 9223372036854775807 0
226 9223372036854775807 9223372036854775807 0
5725216 9223372036854775807 9223372036854775807 0
2435 9223372036854775807 9223372036854775807 0
0 9223372036854775807 9223372036854775807 0
0 9223372036854775807 9223372036854775807 0
0 9223372036854775807 9223372036854775807 0
18 9223372036854775807 9223372036854775807 0

Eric · May 8, 2013, 12:36pm

Hmm, well, you don’t have too many, but you do have some failures listed in that user_beancounter output.

If you try to start ClamAV again, do any of the numbers in the “failcnt” field increase?

Also, which Linux distribution are you using?

-Eric

christophera · May 8, 2013, 9:40pm

If I hit “enable clamav server” in virtualmin, I get:


Configuring and enabling the ClamAV scanning server ..
Starting ClamAV server and enabling at boot .. failed to start : Starting Clam AntiVirus Daemon: [FAILED]
all done

No clamav errors in maillog.

I don’t have a /proc/user_beancounters file on my system, so can’t help there -

Mine’s a Centos 6.4 X64 on digitalocean’s vps cloud (using Linux KVM technology for virtualization).

On my original thread, http://www.virtualmin.com/node/26836 Macaba says the same thing happens on his Ubuntu 12.04 LTS. But we have heard back from Macaba with any more details.

Chris

Phil.RRR · May 10, 2013, 8:34am

Hi, yes if I try to start it again the counts for both oomguarpages and physpages go up by 1.

I’m thinking it’s because of the amount of memory my VPS has, 256MB.

#cat /proc/meminfo shows I’ve got 114748 kB free.

The distribution is Debian 6

Eric · May 10, 2013, 1:41pm

Yeah, unfortunately, the ClamAV daemon is fairly large, it can be tricky to run that on systems without plenty of RAM.

You may want to stick to using the ClamAV command line scanner… though with 256MB of RAM, even that may be a little tricky.

-Eric

Phil.RRR · May 10, 2013, 2:01pm

OK thanks for the help anyway