Your best bet would be to have freshclam running on one machine and have the rest use the Ansible playbook to pull from that “freshclam machine”.
Or, if you want to keep it all Ansible, have the playbook pull the definitions vis freshclam on one machine and then copy to all the others. -Maarten Sent from a tiny keyboard > On Jul 30, 2024, at 19:00, Arlo Hill via clamav-users > <clamav-users@lists.clamav.net> wrote: > > > Hello, > > We are using Ansible to update the ClamAV databases automatically, I know > there is freshclam, however, with our current setup with multiple servers, it > makes sense to use this alternative especially as we like to backup. I am now > having an issue with a 403 error when grabbing each file from their download > links. I am 100% sure this is due to IP blocking and being rate-limited and I > wanted some advice on what to do next. Once this code is working properly it > will run once a day to ensure that the databases are up to date. These, are > the links we are using: > > - "https://database.clamav.net/daily.cvd"; > - "https://database.clamav.net/bytecode.cvd"; > - "https://database.clamav.net/main.cvd"; > > thanks > > > <Outlook-bktyimlf.gif> > Arlo Hill > IT Support Engineer > Allied Press Limited > A: 52 Stuart Street, PO Box 517, Dunedin 9016, New Zealand > M: 02102302148 > > _______________________________________________ > > Manage your clamav-users mailing list subscription / unsubscribe: > https://lists.clamav.net/mailman/listinfo/clamav-users > > > Help us build a comprehensive ClamAV guide: > https://github.com/Cisco-Talos/clamav-documentation > > https://docs.clamav.net/#mailing-lists-and-chat
_______________________________________________ Manage your clamav-users mailing list subscription / unsubscribe: https://lists.clamav.net/mailman/listinfo/clamav-users Help us build a comprehensive ClamAV guide: https://github.com/Cisco-Talos/clamav-documentation https://docs.clamav.net/#mailing-lists-and-chat
