On 4/5/2019 12:16 PM, David Raynor wrote: > I can recreate that same issue with daily cvd 25410, using ClamAV > 0.100.1. That was the first 0.100.X I had handy to do a quick test. > The problem is something specific to sigtool and only the list-sigs > feature. It does not affect clamscan or clamd, and does not affect the > --find-sigs option of sigtool. > We do ongoing signature load testing with several different versions > of ClamAV, but focus on scan testing. > > It does still happen with the latest release so I'll talk with the > team about opening this as a bug. > > Thanks for the report.
Hi David, I wanted to add to this that we started having issues with this today where freshclam is also saying the signatures are invalid as well as clamd. So 25410 with 0.100.3 appears to be quite non-functional. For example, if I run /usr/local/clamav/bin/freshclam --datadir=/tmp/3 with 0.100.3, it downloads, says it's invalid, waits 5 seconds and downloads again eventually giving up after a few minutes: Fri Apr 5 14:17:59 2019 -> *Current working dir is /tmp/3 Fri Apr 5 14:17:59 2019 -> *Max retries == 3 Fri Apr 5 14:17:59 2019 -> ClamAV update process started at Fri Apr 5 14:17:59 2019 Fri Apr 5 14:17:59 2019 -> *Using IPv6 aware code Fri Apr 5 14:17:59 2019 -> *Querying current.cvd.clamav.net Fri Apr 5 14:17:59 2019 -> *TTL: 1298 Fri Apr 5 14:17:59 2019 -> *Software version from DNS: 0.101.2 Fri Apr 5 14:17:59 2019 -> ^Your ClamAV installation is OUTDATED! Fri Apr 5 14:17:59 2019 -> ^Local version: 0.100.3 Recommended version: 0.101.2 Fri Apr 5 14:17:59 2019 -> DON'T PANIC! Read https://www.clamav.net/documents/upgrading-clamav Fri Apr 5 14:17:59 2019 -> *Retrieving http://db.US.clamav.net/main.cvd Fri Apr 5 14:17:59 2019 -> *Trying to download http://db.US.clamav.net/main.cvd (IP: 104.16.219.84) Fri Apr 5 14:18:12 2019 -> Downloading main.cvd [100%] Fri Apr 5 14:18:12 2019 -> ^[LibClamAV] cli_cvdload: Corrupted CVD header Fri Apr 5 14:18:12 2019 -> !Verification: Malformed database Fri Apr 5 14:18:13 2019 -> *Querying main.0.93.0.0.6810DB54.ping.clamav.net Fri Apr 5 14:18:13 2019 -> Trying again in 5 secs... Fri Apr 5 14:18:18 2019 -> ClamAV update process started at Fri Apr 5 14:18:18 2019 ... Is there a way to go back to daily-25409, for example, other than using backups? I looked at the FAQ, https://www.clamav.net/documents/clamav-virus-database-faq and didn't have any thoughts on it. Regards, KAM _______________________________________________ clamav-users mailing list clamav-users@lists.clamav.net https://lists.clamav.net/mailman/listinfo/clamav-users Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
