On Nov 19, 2021, at 11:20 AM, Mark Dadgar <mark@pdc-racing.net> wrote:
On Nov 19, 2021, at 5:47 AM, Andrew Hodgson <andrew@hodgson.io> wrote:
Thanks for this it was due to changing cloud providers. My old provider I installed Debian from an ISO file which created the swap partition but on the new provider I used their cloud image with no swap. Swap now created and everything is back to normal. Its running on an instance with 2GB of RAM and based on how I am seeing the usage running I would see this as an absolute minimum for a standard Mailman 3 stack.
I had this same experience on Digital Ocean. The short-term fix was enabling swap and the long-term fix was upping my service level to something with more memory. Without swap, I don’t think 2GB is realistically sufficient to run a full mm3 instance.
I'm running a Linode VM with 2 cores and 4 GB ram with 9 lists that are not high traffic most of the time. I would say this is the very minimum of power. (Yes, I'm using Docker containers which may be adding some overhead.) I'll need to increase my service when the list traffic increases post-pandemic.
Seth