On Mon, Jul 20, 2020 at 12:43 PM Mark Dadgar <mark@pdc-racing.net> wrote:
On Jul 19, 2020, at 5:11 PM, Dave Clements <clements@galaxyproject.org> wrote:
Thanks for the insight and fixes. We (we being Nate who is also on this list) think it was a lack of virtual memory on the server. This crashed ClamAV and it could not restart.
My fresh new mailman3 install (3.3.1, Django 2.x, nginx, Postgres, memcashd, etc) is very clearly leaking memory and has eaten all the swap I set up as a safety net. Maybe yours is, too?
It seems that after running for a few months without restart, Django (which we run two instances of, for two domains on the same Mailman server) was consuming quite a bit more memory than it does on startup.
We were also out of space on the filesystem where ClamAV stores its database, causing corruption, so both issues had to be fixed before ClamAV could start.
Thanks, --nate
I am in the process of gathering data and will start a separate thread when I have enough to present.
- Mark
mark@pdc-racing.net | 408-348-2878
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/