In the process of rolling out the new 0.95.3 upgrade, we noticed several error messages about the virus DB's being out of date. This was odd as our clam engines update from a local mirror that pulls updates from the clamav infrastructure approx. every hour. Upon further investigation, the outdated DB showed up in our monitoring system and clamdtop. It appears that .cld files left over from before the switch to a local mirror took precedence over the newer .cvd files. We set up our local mirror according to the faq in addition to getting some clarification on this list.
This was a definite fail as follows. 1. Our clam engines ran for almost a month with outdated virus DB's. 2. We failed to notice. 3. The clam engines failed to notify us until manually restarted. Recommendations 1. At the least update the faq on local mirrors to say that .cld's should be manually removed. 2. Modify the freshclam software to delete main.cld & daily.cld if ScriptedUpdates is off. 3. Modify the clam engine to not load .cld's if a newer .cvd is present. Has anybody else run into this when switching to a local mirror? -- But there's no sense crying over every mistake. You just keep on trying till you run out of cake. And the Science gets done. And you make an income. For the people who are still alive.
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
