Atomicorp

Posted: **Wed Nov 03, 2010 1:29 pm**

After updating to clamav-0.9.4-2.el5.art yesterday, we have been getting the following error every hour on the cron task. Any ideas what could be wrong? This was'nt happening the day before when the intial 9.4 was released.

Code: Select all

/etc/cron.hourly/freshclam:

ERROR: Problem with internal logger (UpdateLogFile = /var/log/clamav/freshclam.log).
ERROR: /var/log/clamav/freshclam.log is locked by another process

Also does'nt fix the issue after restarting the deamon.

Code: Select all

[xxxxx@xxxxx ~]# freshclam
ERROR: /var/log/clamav/freshclam.log is locked by another process
ERROR: Problem with internal logger (UpdateLogFile = /var/log/clamav/freshclam.log).
[xxxxx@xxxxx ~]# rpm -q clamav
clamav-0.96.4-2.el5.art
[xxxxx@xxxxx ~]# service clamd restart
Stopping Clam AntiVirus Daemon:                            [  OK  ]
Starting Clam AntiVirus Daemon:                            [  OK  ]
[xxxxx@xxxxx ~]# freshclam
ERROR: /var/log/clamav/freshclam.log is locked by another process
ERROR: Problem with internal logger (UpdateLogFile = /var/log/clamav/freshclam.log).
[xxxxx@xxxxx ~]#

Posted: **Wed Nov 03, 2010 4:09 pm**

The "locked by another process" just means that freshclam is already running (I think). Maybe it would be worth checking to see if there might not be a freshclam process that's hung somehow?

I've just updated it on 4 systems and one of them issued that error but only once - it was fine moments later. And I had run it immediately after updating....I think it was just slow to update automatically.

Faris.

Posted: **Wed Nov 03, 2010 6:01 pm**

The updated packages replace the configuration files, which specify the user clamd runs as. Supposedly, running 'asl -s -f' fixes this (only on ASL servers of course), but I tend to just manually set 'User root' in /etc/clamd.conf ('qscand' on non-ASL qmail-scanner server) and I recursively chown /var/clamav and /var/log/clamav to root:root (or qscand:qscand on non-ASL qmail-scanner servers) and then restart clamd.

Run 'freshclam' afterwards to verify you get no more errors.

I think the clam* packages could do a better job of not messing with a working setup.

Posted: **Thu Nov 04, 2010 12:05 pm**

Thanks guys,
I rebooted a couple times and retarted clamd also a couple times and it seems to have went away.

Atomicorp

Freshclam Cron error after Clamav Update

Freshclam Cron error after Clamav Update

Re: Freshclam Cron error after Clamav Update

Re: Freshclam Cron error after Clamav Update

Re: Freshclam Cron error after Clamav Update