Bug 122534 - security/ClamAV stops working if it's database directory is locked.
Summary: security/ClamAV stops working if it's database directory is locked.
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: Renato Botelho
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-04-07 16:10 UTC by Sebastian Inacker
Modified: 2008-04-16 17:11 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sebastian Inacker 2008-04-07 16:10:01 UTC
When the database directory of ClamAV is locked, clamav is terminating.

It seems to me, that this is because of freshclam, which is not able to reach any listed mirrors at this moment.

IMO: ClamAV should not force a reload, if the directory is locked and ClamAV can not proceed because of this reason. (Why force a reload, which will fail?)

Looks like a "negative feature" to me.      

/var/log/clamav/clamd.log

Mon Apr  7 01:33:41 2008 -> SelfCheck: Database status OK.
Mon Apr  7 02:04:15 2008 -> SelfCheck: Database modification detected. Forcing reload.
Mon Apr  7 02:04:15 2008 -> Reading databases from /var/db/clamav
Mon Apr  7 02:06:25 2008 -> ERROR: reload db failed: Unable to lock database directory (try 1)
Mon Apr  7 02:08:35 2008 -> ERROR: reload db failed: Unable to lock database directory (try 2)
Mon Apr  7 02:10:45 2008 -> ERROR: reload db failed: Unable to lock database directory (try 3)
Mon Apr  7 02:10:45 2008 -> ERROR: reload db failed: Unable to lock database directory
Mon Apr  7 02:10:45 2008 -> Terminating because of a fatal error.
Mon Apr  7 02:10:45 2008 -> Shutting down the main socket.
Mon Apr  7 02:10:45 2008 -> Closing the main socket.
Mon Apr  7 02:10:45 2008 -> Socket file removed.
Mon Apr  7 02:10:45 2008 -> Pid file removed.
Mon Apr  7 02:10:45 2008 -> --- Stopped at Mon Apr  7 02:10:45 2008

Seems, that the directory is stil locked by freshclam, which had problems to reach any mirror at this time:

/var/log/clamav/freshclam.log

[...]
Can't connect to port 80 of host database.clamav.net (IP: 62.26.160.3)
Trying host database.clamav.net (62.201.161.84)...
nonblock_connect: connect timing out (30 secs)
Can't connect to port 80 of host database.clamav.net (IP: 62.201.161.84)
Trying host database.clamav.net (85.10.242.82)...
nonblock_connect: connect timing out (30 secs)
Can't connect to port 80 of host database.clamav.net (IP: 85.10.242.82)
Trying host database.clamav.net (85.199.169.78)...
nonblock_recv: recv timing out (30 secs)
ERROR: getfile: Error while reading database from database.clamav.net (IP: 85.199.169.78)
ERROR: Can't download daily.cvd from database.clamav.net
Giving up on database.clamav.net...
Update failed. Your network may be down or none of the mirrors listed in freshclam.conf is working. Check http://www.clamav.net/support/mirror-problem for possible reasons.

I'm useing ClamAV from ports. I haven't seen something releated in /usr/ports/UPDATING

# pkg_info | grep clamav
clamav-0.92.1_1     Command line virus scanner written entirely in C

I'm contacting FreeBSD, not ClamAV because of:
"Please do not report any bug affecting software derived from ClamAV and distributed by a third party (i.e. ports we do not maintain directly) because we have no control over them. Contact their developers instead." (http://www.clamav.org/bugs/)

Status critical because virus scanning/delivery of email stops working...
Comment 1 Rong-En Fan freebsd_committer freebsd_triage 2008-04-07 17:13:52 UTC
Responsible Changed
From-To: freebsd-ports-bugs->garga

Over to maintainer.
Comment 2 Renato Botelho freebsd_committer freebsd_triage 2008-04-16 17:11:13 UTC
State Changed
From-To: open->closed

Problem fixed on clamav-0.93. Thanks