[ZendTo] ClamAV issue

[Dale E. Qualls]

Disregard, I dumped it and build a new server from scratch.






[http://images.pattishall.com/images/pattishalllogo.jpg]




Dale E. Qualls
Director of Information Technology
Pattishall, McAuliffe, Newbury, Hilliard & Geraldson LLP
200 South Wacker Drive, Suite 2900
Chicago, IL 60606-5896
Direct: (312) 554-7979 Main: (312) 554-8000 Fax: (312) 554-8015
deq at pattishall.com<mailto:deq at pattishall.com> www.pattishall.com<http://www.pattishall.com>





________________________________

The preceding message and any attachments may contain confidential information protected by the attorney-client or other privilege. You may not forward this message or any attachments without the permission of the sender. If you believe that it has been sent to you in error, please reply to the sender that you received the message in error and then delete it. Nothing in this email message, including the typed name of the sender and/or this signature block, is intended to constitute an electronic signature unless a specific statement to the contrary is included in the message.

________________________________


From: ZendTo <zendto-bounces at zend.to> On Behalf Of Dale E. Qualls via ZendTo
Sent: Monday, January 1, 2024 6:42 PM
To: 'zendto at zend.to' <zendto at zend.to>
Cc: Dale E. Qualls <deq at pattishall.com>
Subject: [ZendTo] ClamAV issue

Howdy!

ZendTo 5.03 on CentOS7.

I had an error reported to me today that showed the following after the file was uploaded and the AV scanning was attempted:

The attempt to virus-scan your drop-off failed.  Please notify the system administrator.

I tried several drop-offs with the same result.  I then started trouble shooting and found that ClamAV is outdated.  Running a freshclam shows this:

ClamAV 0.99.4/26096/Tue Mar  2 05:59:11 2021
[root at files log]# freshclam
ClamAV update process started at Mon Jan  1 18:23:09 2024
WARNING: Your ClamAV installation is OUTDATED!
WARNING: Local version: 0.99.4 Recommended version: 0.103.11

I’ve tried everything I can to fix this, including the following:
Used YUM to remove clamav
Tried installing with YUM with this command: yum -y install clamav-server clamav-data clamav-update clamav-filesystem clamav clamav-scanner-systemd clamav-devel clamav-lib clamav-server-systemd
Updated the repository that kept failing with this (all I could find is the Fedora stuff, I’m running CentOS 7:
yum erase ius-release
rm /etc/yum.repos.d/ius*.repo*
yum install https://repo.ius.io/ius-release-el7.rpm<https://repo.ius.io/ius-release-el7.rpm> https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm<https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm>

I was then able to install the new ClamAV with this:
yum -y install clamav-server clamav-data clamav-update clamav-filesystem clamav clamav-scanner-systemd clamav-devel clamav-lib clamav-server-systemd

Tried fixing the install with 3-clamav.sh<http://3-clamav.sh> installer script
No dice.  Restored from snapshot and tried running the full installer script and it too couldn’t update ClamAV.

I restored the VM from backup to a copy of the server from 20 days ago.  Worked fine.

Went back to the original VM and now (at least for now) it is working just fine.

I was hoping to just do an in-place upgrade to the latest version (either using the installer or YUM) but those don’t seem to be doing me any good either as far as fixing the ClamAV issue (again, which as of right now is working for some reason).

Thoughts/suggestions??

Thanks!




[http://images.pattishall.com/images/pattishalllogo.jpg]

Dale E. Qualls
Director of Information Technology
Pattishall, McAuliffe, Newbury, Hilliard & Geraldson LLP
200 South Wacker Drive, Suite 2900
Chicago, IL 60606-5896
Direct: (312) 554-7979 Main: (312) 554-8000 Fax: (312) 554-8015
deq at pattishall.com<mailto:deq at pattishall.com> www.pattishall.com<http://www.pattishall.com>



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jul.es/pipermail/zendto/attachments/20240104/f209f57a/attachment-0001.html>