Hi,
Brian Carpenter a écrit le 14/07/2020 à 12:54 :
On 7/14/20 6:49 AM, Gilles Filippini wrote:
Mailman Core logs: [2020-07-14 10:41:21 +0000] [36] [CRITICAL] WORKER TIMEOUT (pid:49) [2020-07-14 10:41:21 +0000] [49] [INFO] Worker exiting (pid: 49) [2020-07-14 10:41:22 +0000] [50] [INFO] Booting worker with pid: 50
I am pretty sure that timeout is related to gunicorn. If it is, then increasing the worker out timeout setting for gunicorn should work. You tend to get such errors when doing an export of a large membership roster. This is the first time I have seen it related to a held message.
I have this in my setup:
mailman.cfg:
[webservice] configuration: /opt/mailman/mm/gunicorn.cfg
gunicorn.cfg:
[gunicorn] workers = 4 timeout = 900
You will need to restart gunicorn after adjusting the timeout setting.
Sorry for the late answer, I was afk the last 24 hours.
I can confirm that this solution works. Thanks a lot! And thanks to Mark for the added details.
But it sounds weird that printing out the number of held messages could timeout because of these messages' size.
Best,
_g.