![]() Monitored freshclam CPU usage and the freshclam logfile /var/log/clamav/freshclam.log.Removed all the files in the folder /var/lib/clamav by executing sudo rm /var/lib/clamav/*.This suggested that a more drastic steps might be needed than just deleting mirrors.dat. The same applied to the foreground process sudo freshclam -v.Īnd both would get stuck on the same file daily-22474.cdiff at. Tried the steps given above for case #1 first, hoping they would solve the problem this time, too.Īs soon as sudo /etc/init.d/clamav-freshclam start had been executed, the freshclam daemon process would quickly start consuming 100% CPU again.Noticed that both, the freshclam process which I had started in the terminal and the freshclam daemon which gets started on system startup, both used 100% CPU each. This time, however, it got stuck downloading the file daily-22474.cdiff at. Normally this will succeed within less than a minute. I had manually run sudo freshclam in a terminal window. Update of the daily definition file finished within half a minute.Ĭase #2: solved by deleting /var/lib/clamav/*.Executed sudo freshclam -v (used option -v to make freshclam a bit more verbose.).Started the freshclam daemon process by executing sudo /etc/init.d/clamav-freshclam start.Removed the file mirrors.dat by executing sudo rm /var/lib/clamav/mirrors.dat.Stopped the freshclam daemon process by executing sudo /etc/init.d/clamav-freshclam stop.Interrupted the running freshclam by pressing c.This time, however, it kept on downloading the same daily.cvd over and over again. Maybe it is going to help you in case the problem re-occurs and maybe it is going to help someone else who encounters the same problem.Īs a matter of fact it happened on 2 different Mint systems to me only recently, i.e. Nonetheless I would like to explain a different approach. And I know you followed administrollaattori's advice of completely purging and then re-installing clamav. I realize this thread has been marked solved. I'll leave an attachment of dmesg just in case.Īnother symptom was file manager was really slow, I'm assuming only because clamav was using a lot of resources. ![]() I just killed freshclam/clamav so don't know if that would matter. I wonder if dmesg log would be good for this type of thing, and how to do it properly. I also ran a fsck and included the text in an Attachment, although just noticed the date is wrong. Was going to do some testing without swap before I point it to the 4GB I created for Mate 18. And, I deleted swap for the KDE side to setup the 18 install.why, swap was at the end of drive. One thing to note, this is a 17-18mo old install and gets a lot of me. I didn't create an account and have read about how to keep it locked down. I also installed Teamviewer recently, but just to test it out for some future work. I don't really know the best diagnostics to provide, so if needed just fire away. It all seemed okay until today, so it's been just a day or so since install. This is on the HP Laptop in signature.ĭon't know if any of this matters but just made this single boot KDE 17.1 a Dual Boot with Mate 18. Hey guys! Freshclam/Clamav is running 50% of CPU, 100% of No.1 Core and 1.50 of RAM, all on it's own. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |