Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ClamAV can be a resource hog, and doesn't need to be running if it's not configured. #49

Closed
patch0 opened this issue Jun 13, 2017 · 5 comments
Labels

Comments

@patch0
Copy link
Contributor

patch0 commented Jun 13, 2017

We've had a few Symbiosis users recently (with otherwise pretty quiet machines who are seeing issues with clamav hogging resources - CPU, disk and RAM.

This seems to be down to a memory leak in clamd, which after 150+ days of uptime chews up a significant amount of RAM, which can then cause freshclam to have problems allocating memory, leading to it cheaing up CPU time and disk space as it writes WARNING: [LibClamAV] mpool_malloc(): Can't allocate memory ([0-9]* bytes). to freshclam.log over and over until the disk is full, then starts consuming all the CPU time on the box.

Really, clamd doesn't need to even be running if its not configured to be used, and provides users a false sense of security if they see it running on the box but its not configured, however it may be worth an extra daily/weekly forced restart/reload of the service if it is being used, to clear out any memory leak issues.

Originally reported on Bytemark's Gitlab by @pcammish on 2016-12-14T12:17:25.897Z

@patch0
Copy link
Contributor Author

patch0 commented Jun 13, 2017

Customers are repeatedly hitting this and running out of memory.

Can we not fix in the current release?

Originally posted by @steveu on 2017-05-25T08:59:54.968Z

@patch0
Copy link
Contributor Author

patch0 commented Jun 13, 2017

I concur. This really needs fixing in the current release (not just for stretch).

Originally posted by @jamielinux on 2017-04-05T15:52:29.757Z

@patch0
Copy link
Contributor Author

patch0 commented Jun 13, 2017

We should fix this urgently. The default cloud server (1GB, Symbiosis) is effectively broken.

Originally posted by @steveu on 2017-04-05T15:16:08.401Z

@patch0
Copy link
Contributor Author

patch0 commented Jun 13, 2017

The footprint for ClamAV is now up to 486 MB (from just under 400 MB a few months ago) on a machine doing nothing, and we're starting to see customers who have it enabled on 1 GB machines have issues with the VMs OOMing.

At present a clean fresh Symbiosis image on a 1 GB cloud server now reports 50.6% of the RAM used by clamd and freshclam, leaving scarce little for Apache, MySQL and the typical stuff a user would run.

This probably needs to be bumped up.

Originally posted by @pcammish on 2017-03-20T10:33:20.845Z

@patch0
Copy link
Contributor Author

patch0 commented Jun 13, 2017

This is already supposed the be the case!

Originally posted by @patch0 on 2017-01-25T08:55:49.555Z

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant