![]() Because of the memory leak clamscan really isn't a valuable tool. Is there anything I should be doing or researching at this point. In the cases I've read, all the repliers told original posters to purchase more RAM - however in this case I have 64GB of total RAM and so this recommendation isn't really applicable. With google fu I've seen problems with memory leaks with ClamAV however honestly these reports are from the 2014-2017 era so I'm not sure if they are relevant, but by what is described its very similar behavior. I can't access logs or htop since system is effectively frozen. When the I receive the error about lack of swapspace the entire FreeNAS system is brought to its knees - I have to reboot via the BMC since the machine is totally not responsive. I run your scripts within iocage jail and the system has 64 Gb of ram with 2048 Mib of RAM allocated to 3 VM's - so in theory I have plenty of RAM available. ![]() On about the 3rd or 4th run of the scan, I'll keep receiving messages that I have no available swap space. ![]() The clamscan takes about 2-3 days to actually complete. I run clamscan once a week - full system scan using your script triggered by cron job. Hey thanks again for the support however I'm having some issues with Clamscan - and I believe its a memory link. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |