We have a new cvd building now. We do have an alert system, but the alert system, for some reason didn’t email us the alert. We’re looking into that.
Sent from my iPhone > On Mar 18, 2018, at 12:07, Andy Schmidt <andy_schm...@hm-software.com> wrote: > > This has become a regular occurrence - but since no one else has mentioned > it... according to the automated alerts I am receiving for MY server, the > signature updating seems to be stuck again. > > The "up to date daily.cld" is now 40 hours old. > > Sun Mar 18 11:42:02 2018 -> ClamAV update process started at Sun Mar 18 > 11:42:02 2018 > Sun Mar 18 11:42:02 2018 -> main.cld is up to date (version: 58, sigs: > 4566249, f-level: 60, builder: sigmgr) > Sun Mar 18 11:42:02 2018 -> daily.cld is up to date (version: 24397, sigs: > 1879834, f-level: 63, builder: neo) > Sun Mar 18 11:42:02 2018 -> safebrowsing.cld is up to date (version: 47149, > sigs: 2950093, f-level: 63, builder: google) > Sun Mar 18 11:42:02 2018 -> bytecode.cld is up to date (version: 319, sigs: > 75, f-level: 63, builder: neo) > > It's trivial to have an automated script that reports when the file dates > are older than the "expected" replacement periods and then alert the project > owners to a potential problem. > > > > _______________________________________________ > clamav-users mailing list > clamav-users@lists.clamav.net > http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users > > > Help us build a comprehensive ClamAV guide: > https://github.com/vrtadmin/clamav-faq > > http://www.clamav.net/contact.html#ml _______________________________________________ clamav-users mailing list clamav-users@lists.clamav.net http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
