I’d seen this happen occasionally over the last couple of months, but it seemed to get really bad on Friday.
Fri Mar 21 21:31:45 2008 -> SelfCheck: Database modification detected. Forcing reload.
Reading databases from /var/lib/clamav
ERROR: reload db failed: Unable to lock database directory (try 1)
ERROR: reload db failed: Unable to lock database directory (try 2)
ERROR: reload db failed: Unable to lock database directory (try 3)
ERROR: reload db failed: Unable to lock database directory
Terminating because of a fatal error.
Socket file removed.
Pid file removed.
--- Stopped at Fri Mar 21 21:38:16 2008
Not entirely sure what the problem is, but it seems like clamav is choking on recent updates from freshclam.
And apparently I’m not the only one. Took advice from this thread and updated clamav to the version in debian-volatile. The official ClamAV documentation also recommends using the volatile repositories.
I’m new to Debian and almost took this to mean that I should use etch. Good to know that Debian maintains a volatile repository. To pull packages from volatile, just add:
deb http://volatile.debian.net/debian-volatile etch/volatile main contrib non-free
(though preferably use a mirror)
/etc/apt/sources.list. Running a simple
apt-get update clamav or
aptitude update clamav will find and install the appropriate volatile updates. Nice.