Hi there, On Tue-Wed, 12-13 Dec 2006 Edward Dam wrote:
> > > Intermittently, freshclam would die with an MD5 verification error > > > > Does this very recent thread help at all? > > Error (Cannot connect to 'localhost:3310': IO::Socket::INET: connect:... > > It's similar, but not quite the same, in that the problems I have are with > the main and daily cvd files. I am not a scripter... > Is there someway I could do the same with main.cvd and daily.cvd? Yes. But if you haven't already done it, first of all I would suggest that you enable LogVerbose in your freshclam.conf to see if that sheds any light on the problem. Also have a look around in your system logs, especially for things like bad disc accesses. (NB: I haven't tested the following armchair theories. :) If things didn't become clearer, I'd probably run another freshclam (perhaps from cron) which maintains a separate copy of the problem databases. These copies are simply files for your delight and aren't used by the scanner. This might help to eliminate conflicts with processes actually using the databases for scanning. Log verbosely for both real and copy databases, and inspect the logs carefully. If the copies don't suffer from the same problems, then the simplest thing might be to do something like this in the same cron job: /bin/rm -rf /var/lib/clamav_old/ /bin/mv /var/lib/clamav/ /var/lib/clamav_old/ /bin/mv /var/lib/clamav_copy/ /var/lib/clamav/ /bin/mkdir /var/lib/clamav_copy/ This moves all the files at the same instant. Any process which has files in /var/lib/clamav/ open at the time of the move will still have the same files open but they will then be in /var/lib/clamav_old. To get the processes to use the new files you have to either restart them or send them the appropriate signal. Don't forget that you'll need a full set of the files in the copy database, not just the ones you're having problems with, or the procedure will fail. You can be creative and only do the operations above if a test in a cron job or script succeeds. See the earlier thread for examples or look at a shell scripting tutorial. It's easy. Don't overlook the "OnUpdateExecute" and "OnErrorExecute" options in the config file. Of course the copy databases might suffer from the same problem, in which case I guess we'll be hearing from you again. And of course the simplest thing might not be the best thing. I think I'd want to know exactly what the problem is, and fix it. :) I agree from your description of other software that hardware is probably not to blame, but the fact that the problem has become worse is suspicious. Would it be silly to ask if you've checked that you're not running into swap? Tried adding some more ram? Did the deterioration coincide with something like installing your new kernel? -- 73, Ged. _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://lurker.clamav.net/list/clamav-users.html
