Brian,
Sorry for the delay, but I don't know what's going on here. Mark and Abhilash must both be traveling.
Brian Carpenter writes:
File "/usr/lib/python3.6/site-packages/django/http/cookie.py", line 1, in <module> from http import cookies File "<frozen importlib._bootstrap>", line 971, in _find_and_load File "<frozen importlib._bootstrap>", line 955, in _find_and_load_unlocked File "<frozen importlib._bootstrap>", line 665, in _load_unlocked File "<frozen importlib._bootstrap_external>", line 674, in exec_module File "<frozen importlib._bootstrap_external>", line 771, in get_code File "<frozen importlib._bootstrap_external>", line 482, in _validate_bytecode_header MemoryError DAMN ! worker 1 (pid: 20) died, killed by signal 9 :( trying respawn ...
It seems to be "Django all the way down" to here. There's nothing maintained by Mailman there, and I doubt our Django expertise extends to much of its internals.
Then a little while I see a whole bunch of the following lines:
Sun Oct 27 00:13:02 2019 - *** uWSGI listen queue of socket "0.0.0.0:8080" (fd: 8) full !!! (101/100) ***
And again, uswgi is a different project (and in Debian at least it depends on an ancient GNU package that is unmaintained which depends on an EOL'ed version of GNU Guile).
Would someone help me troubleshoot this? Thank you.
Sorry, but I have no idea what the actual trouble is. It doesn't seem to be in our code, it seems to be in the Django or uwsgi initialization before Mailman code gets started. You might try in the Django lists first, since the main problem seems to be Django exhausting memory.
The uswgi problem I believe may be a separate known bug. I seem to recall a report besides yours of uswgi falling down and being unable to get up this way without a system reboot.
I use Apache + mod_wsgi, Abhilash recommends gunicorn as the WSGI host. I'm not sure what Mark uses. Is it possible to change the WSGI host? If not, can you try a different version of uwsgi?
Steve