On Thu, 17 Feb 2022 at 01:02, Mark Sapiro <mark@msapiro.net> wrote:
On 2/16/22 00:18, Philip Colmer wrote:
Thank you for the replies from Mark and Stephen.
One of the reasons why Prasanth & I are concerned with this specific system is because the first time memory usage crept up, it got to the point where oomkiller stepped in and, as is usual for that particular mechanism, one of the processes it killed was sshd, thus removing access to the system :(. I know that oomkiller can be tuned to stop it killing processes like sshd but it will, nevertheless, start killing *some* processes if it sees an out of memory situation.
It sounds like there is a memory leak somewhere. This is an issue with some versions of Python. I know both Python 3.10.2 and 3.9.10 were released ahead of schedule to fix this. See https://bugs.python.org/issue46347
Thanks, Mark. We're using Python 3.8; I've looked at the open issues and don't immediately see any that might be memory-leak related in a way that would affect Mailman 3.
That said, there are quite a few libraries and other "moving parts" involved in this project so we're going to try and track memory usage over time by process or similar to see if we can see whether or not this is a leak and, if it is, what the likeliest culprit might be.
Philip