Bug#471643: ERROR: reload db failed: Unable to lock database directory

1 view
Skip to first unread message

Markus Veltre

unread,
Mar 19, 2008, 5:50:09 AM3/19/08
to

Package: clamav-daemon
Version: 0.90.1dfsg-3etch10

hi,

I'm using clamav-deamon with freshclam to scan incoming
emails on my mail-server.

After the last clamav-update in debian etch, clamav stops
working sometimes after freshclam updated the signatures.
In the log-file it reads like this:

/var/log/clamav/clamav.log -->
>(..) 21:56:32 (..)SelfCheck: Database modification detected. Forcing reload.
>(..) 21:56:32 (..)Reading databases from /var/lib/clamav
>(..) 21:58:42 (..)ERROR: reload db failed: Unable to lock database directory (try 1)
>(..) 22:00:52 (..)ERROR: reload db failed: Unable to lock database directory (try 2)
>(..) 22:03:02 (..)ERROR: reload db failed: Unable to lock database directory (try 3)
>(..) 22:03:02 (..)ERROR: reload db failed: Unable to lock database directory
>(..) 22:03:02 (..)Terminating because of a fatal error.Wed Mar 12 22:03:02 2008 -> Socket file removed.
>(..) 22:03:02 (..)Pid file removed.
>(..) 22:03:02 (..)--- Stopped at Wed Mar 12 22:03:02 2008
<---

Both clamd.ctl and clamd.pid in /var/run/clamav will removed, and two
clamscan-processes (started by postfix) will use 99% of CPU.

A simple restart of clamd, freshclamd and postfix does not help, the only
one which helps is to restart the whole server.
~10mins after restart the log is looking like:

/var/log/clamav/clamav.log -->
>(..) 09:56:43 (..)+++ Started at Thu Mar 13 09:56:43 2008
>(..) 09:56:43 (..)clamd daemon 0.90.1 (OS: linux-gnu, ARCH: x86_64, CPU: x86_64)
>(..) 09:56:43 (..)Log file size limit disabled.
>(..) 09:56:43 (..)Reading databases from /var/lib/clamav
>(..) 10:12:13 (..)Loaded 312591 signatures.
>(..) 10:12:13 (..)Unix socket file /var/run/clamav/clamd.ctl
>(..) 10:12:13 (..)Setting connection queue length to 15
>(..) 10:12:13 (..)Archive: Archived file size limit set to 10485760 bytes.
>(..) 10:12:13 (..)Archive: Recursion level limit set to 5.
>(..) 10:12:13 (..)Archive: Files limit set to 1000.
>(..) 10:12:13 (..)Archive: Compression ratio limit set to 250.
>(..) 10:12:13 (..)Archive support enabled.
>(..) 10:12:13 (..)Algorithmic detection enabled.
>(..) 10:12:13 (..)Portable Executable support enabled.
>(..) 10:12:13 (..)ELF support enabled.
>(..) 10:12:13 (..)Mail files support enabled.
>(..) 10:12:13 (..)Mail: Recursion level limit set to 64.
>(..) 10:12:13 (..)OLE2 support enabled.
>(..) 10:12:13 (..)PDF support disabled.
>(..) 10:12:13 (..)HTML support enabled.
>(..) 10:12:13 (..)Self checking every 3600 seconds.
<---

Here are the debian-packets I use:
clamav 0.90.1dfsg-3etch10
clamav-freshclam 0.90.1dfsg-3etch10
clamav-daemon 0.90.1dfsg-3etch10
Kernel: 2.6.18-6-amd64
libc: libc6 2.3.6.ds1-13etch5
/var/lib/clamav is on an ext3-filesystem.

Has somebody an idea to solve it? Groups+Permissions
of the relevant files are looking OK. The clamav-mailinglist
told me that I'm using an old version of clamav, but I do
not believe we like to say "debian is using an old version,
thats why it's buggy" ;-)

Thanks,
Markus
_________________________________________________________________
Kostenlose Windows Live Services in einem Komplettpaket. Gleich downloaden!
http://get.live.com/

Stefan Hornburg

unread,
Mar 19, 2008, 6:20:14 AM3/19/08
to

Nevertheless it's highly recommended to upgrade to clamav from
Debian volatile.

Regards
Racke


--
LinuXia Systems => http://www.linuxia.de/
Expert Interchange Consulting and System Administration
ICDEVGROUP => http://www.icdevgroup.org/
Interchange Development Team


--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

Reply all
Reply to author
Forward
0 new messages