Some time ago, jacusy wrote: > Hello, > > this night my clamd-process terminated with an error. The reason was > that freshclam took too long to do its update, so that clamd could not > lock the database. So clamd exited. But this behaviour is very fatal > because the mail system (postfix with amavis) relys on clamd, so if it > is down, the whole mail traffic is blocked!! Caused of an error while > updating...... > > What to do against? >
this one question initiated a whole lot of replies, which I will not quote here. Now the question I have is: is this problem fixed in 0.90.3? Yesterday, this problem hit us on one small-volume mailserver: Thu Jun 7 06:25:54 2007 -> SelfCheck: Database status OK. Thu Jun 7 06:57:05 2007 -> SelfCheck: Database status OK. Thu Jun 7 07:29:34 2007 -> SelfCheck: Database status OK. Thu Jun 7 07:59:40 2007 -> SelfCheck: Database modification detected. Forcing reload. Thu Jun 7 07:59:40 2007 -> Reading databases from /opt/ClamAV/share/clamav Thu Jun 7 08:01:51 2007 -> ERROR: reload db failed: Unable to lock database directory (try 1) Thu Jun 7 08:04:01 2007 -> ERROR: reload db failed: Unable to lock database directory (try 2) Thu Jun 7 08:06:11 2007 -> ERROR: reload db failed: Unable to lock database directory (try 3) Thu Jun 7 08:06:11 2007 -> ERROR: reload db failed: Unable to lock database directory Thu Jun 7 08:06:11 2007 -> Terminating because of a fatal error.Thu Jun 7 08:06:11 2007 -> Socket file removed. Thu Jun 7 08:06:11 2007 -> --- Stopped at Thu Jun 7 08:06:11 2007 This caused no big problems, but I would like to know if it is fixed in 0.90.3 before I'm going to install 0.90.3; I can't find any reference to it in the changelog on the clamav site and maybe I have to wait for 0.91? Or should I file a bug report somewhere? I have tried to find this problem in the bugtracker, but couldn't find it there either. /rolf > The logs: > clamd.log > >> Wed Apr 11 01:53:40 2007 -> SelfCheck: Database status OK. >> Wed Apr 11 02:27:53 2007 -> SelfCheck: Database modification detected. >> Forcing reload. >> Wed Apr 11 02:28:07 2007 -> Reading databases from >> /usr/local/clamav/share/clamav >> Wed Apr 11 02:30:17 2007 -> ERROR: reload db failed: Unable to lock >> database directory (try 1) >> Wed Apr 11 02:32:27 2007 -> ERROR: reload db failed: Unable to lock >> database directory (try 2) >> Wed Apr 11 02:34:37 2007 -> ERROR: reload db failed: Unable to lock >> database directory (try 3) >> Wed Apr 11 02:34:37 2007 -> ERROR: reload db failed: Unable to lock >> database directory >> Wed Apr 11 02:34:37 2007 -> Terminating because of a fatal error.Wed >> Apr 11 02:34:37 2007 -> Socket file removed. >> Wed Apr 11 02:34:37 2007 -> Pid file removed. >> Wed Apr 11 02:34:37 2007 -> --- Stopped at Wed Apr 11 02:34:37 2007 >> > > > freshclam.log > >> ClamAV update process started at Wed Apr 11 02:23:01 2007 >> nonblock_connect: connect timing out (30 secs) >> Can't connect to port 80 of host db.de.clamav.net (IP: 62.26.160.3) >> Trying host db.de.clamav.net (85.25.252.58)... >> nonblock_connect: connect timing out (30 secs) >> Can't connect to port 80 of host db.de.clamav.net (IP: 85.25.252.58) >> Trying host db.de.clamav.net (85.199.169.78)... >> nonblock_connect: connect timing out (30 secs) >> Can't connect to port 80 of host db.de.clamav.net (IP: 85.199.169.78) >> Trying host db.de.clamav.net (85.214.44.186)... >> nonblock_connect: connect timing out (30 secs) >> Can't connect to port 80 of host db.de.clamav.net (IP: 85.214.44.186) >> Trying host db.de.clamav.net (88.198.17.100)... >> nonblock_connect: connect timing out (30 secs) >> Can't connect to port 80 of host db.de.clamav.net (IP: 88.198.17.100) >> Trying host db.de.clamav.net (88.198.104.251)... >> nonblock_connect: connect timing out (30 secs) >> Can't connect to port 80 of host db.de.clamav.net (IP: 88.198.104.251) >> Trying host db.de.clamav.net (89.149.194.18)... >> connect_error: getsockopt(SO_ERROR): fd=5 error=110: Connection timed out >> Can't connect to port 80 of host db.de.clamav.net (IP: 89.149.194.18) >> Trying host db.de.clamav.net (194.77.146.139)... >> nonblock_connect: connect(): fd=5 errno=103: Software caused >> connection abort >> Can't connect to port 80 of host db.de.clamav.net (IP: 194.77.146.139) >> Trying host db.de.clamav.net (195.246.234.199)... >> nonblock_connect: connect timing out (30 secs) >> Can't connect to port 80 of host db.de.clamav.net (IP: 195.246.234.199) >> Trying host db.de.clamav.net (213.174.32.130)... >> nonblock_connect: connect timing out (30 secs) >> Can't connect to port 80 of host db.de.clamav.net (IP: 213.174.32.130) >> Trying host db.de.clamav.net (217.115.136.166)... >> nonblock_connect: connect timing out (30 secs) >> Can't connect to port 80 of host db.de.clamav.net (IP: 217.115.136.166) >> Trying host db.de.clamav.net (217.160.141.39)... >> nonblock_connect: connect timing out (30 secs) >> Can't connect to port 80 of host db.de.clamav.net (IP: 217.160.141.39) >> ERROR: getpatch: Can't download main-43.cdiff from db.de.clamav.net >> nonblock_connect: connect timing out (30 secs) >> Can't connect to port 80 of host db.de.clamav.net (IP: 62.26.160.3) >> >> > (this goes on for some pages....) > >> Trying host database.clamav.net (194.77.146.139)... >> nonblock_connect: connect(): fd=9 errno=103: Software caused >> connection abort >> Can't connect to port 80 of host database.clamav.net (IP: 194.77.146.139) >> Ignoring mirror 195.246.234.199 (due to previous errors) >> Trying host database.clamav.net (213.174.32.130)... >> Downloading daily-3065.cdiff [0%] >> daily.inc updated (version: 3065, sigs: 3293, f-level: 14, builder: sven) >> Database updated (107793 signatures) from database.clamav.net (IP: >> 213.174.32.130) >> WARNING: Clamd was NOT notified: Can't connect to clamd through /tmp/clamd >> -------------------------------------- >> ClamAV update process started at Wed Apr 11 05:23:01 2007 >> main.inc is up to date (version: 43, sigs: 104500, f-level: 14, >> builder: sven) >> daily.inc is up to date (version: 3065, sigs: 3293, f-level: 14, >> builder: sven) >> > > > _______________________________________________ > Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net > http://lurker.clamav.net/list/clamav-users.html > _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
