Closed ksylvan closed 4 months ago
IMO you need more memory. What was in minimum spec some years ago is out of date. To wit: I think it's normal and there is nothing that can be done about it - I'm observing similar.
@AndrewSav With the new clamd.conf
configuration change, I'm not seeing the problem any more. See my PR.
@AndrewSav see my comments in PR #64 - I can now see my spam dashboard again. In the recent past, the rspamd page would often hang trying to render, and was very sluggish when it did render.
Ah alright that sounds good.
Ah alright that sounds good.
Can you approve the PR and I'll go ahead and merge it then? @AndrewSav
@ksylvan at the first opportunity!
@AndrewSav I merged the commit and closed this issue. Without setting CLAMD_MEORY_FIX, it was a no-op for existing installs, so basically there's zero risk of screwing up existing installations. And I ran it over the last few days on two production domains I have.
Classification
Reproducibility
Docker information
Description
The clamd process uses up so much memory on loading that it brings the system to a halt.
This is a known issue.
See https://betatim.github.io/posts/clamav-memory-usage/ for a possible workaround.
Steps to reproduce
My VPS has 2GB of RAM.
Expected results
Actual results
Debugging information
Configuration (docker-compose.yml, traefik.toml...etc)