Author Topic: Latest ClamAV Update from today messes up ClamAV  (Read 1030 times)

0 Members and 1 Guest are viewing this topic.

Offline
**
Latest ClamAV Update from today messes up ClamAV
« on: November 07, 2023, 10:36:04 PM »
today a new update of ClamAV shows up in CWP yum.

So i updated it and after this CPU goes up for the Clam process, i checked the logs and saw, clam wasn't able to start normally and complained about duplicate database files.

after removing them manually like the log says it was complaining about the sock is used by another process.

solution was do delete the sock file so it could create a new one.

Problem, i need to do this after every reboot.

i tried a yum history rollback but this failed for those packages so i rolled back my server using the veeam backup.


Can anyone confirm this problem, so maybe to bring out a fix before everyone is updating the clam packages

thanks

Offline
**
Re: Latest ClamAV Update from today messes up ClamAV
« Reply #1 on: November 07, 2023, 11:14:02 PM »
The following Packages came with the update, these packages make the problems:

clamav-data.noarch   0.103.11-1.el7
clamav-filesystem.noarch   0.103.11-1.el7
clamav-lib.x86_64   0.103.11-1.el7
clamav-update.x86_64   0.103.11-1.el7
clamav.x86_64   0.103.11-1.el7
clamd.x86_64   0.103.11-1.el7

Offline
*
Re: Latest ClamAV Update from today messes up ClamAV
« Reply #2 on: November 09, 2023, 10:34:53 AM »
Hello,

Did You managed to resolve the issue?

Offline
**
Re: Latest ClamAV Update from today messes up ClamAV
« Reply #3 on: November 09, 2023, 01:43:39 PM »
no i didn't.

I made a new check after restoring my machine from a Veeam backup, i really tried to update those packages again, and it happened the same.

So again, restore from veeam and now i excluded those package versions from the update.

But i wonder, why not more people are complaining about this problem.

Offline
*
Re: Latest ClamAV Update from today messes up ClamAV
« Reply #4 on: November 09, 2023, 06:14:30 PM »
I updated a few minutes after your first post, and everything went without any issues.
I've noticed that Clam was at 100% CPU in first minute, or two after update, but after that, everything was ok.