On 2011-10-10 19:29, Alex wrote: > Hi, > >>>> Is there a way to have it automatically restarted when something like >>>> this happens or be more tolerant of database problems, with >>>> notifications of those problems, in the future? >> >> If bug 2727 is any indication, don't bet on it. > > I don't think it's that bug, since I have a version greater than > 0.97.0.2, and this bug was resolved in April. > >>> Restarting won't help if the database is corrupted, or is there is some >>> problem parsing the database. >> >> Correct, if you mess up a sig DB on a system, you've messed up the >> ClamAV on the system. >> And most of the time it doesn't log a thing, it just dies. >> Lots of fun. :-) > > In my case, restarting does fix the problem. > > Is there anything I should watch for, or do when it happens again? How > can I manually check the integrity of all the databases when it fails?
Run clamscan /dev/null (or any file), and it will print an error if any database is wrong. Official databases have digital signatures, and clamscan (and freshclam) checks it. Best regards, --Edwin _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
