Actions
tickets #112928
openmailman3 - when a runner dies, why isn't it just restarted?
Status:
New
Priority:
Normal
Assignee:
-
Category:
Mailing lists
Target version:
-
Start date:
2022-06-23
Due date:
% Done:
0%
Estimated time:
Description
Mostly logging this as a placeholder - today outbound deliveries stopped around 1040CET as the "out" runner abended.
We have also seen this with the archive runner, more than once. I don't understand why those runners can't be just automatically restarted, rather then waiting for someone to notice the problem. I guess it is more a question for upstream :-(
Updated by pjessen almost 2 years ago
Updated by pjessen almost 2 years ago
- Related to tickets #95242: Mailman - the 'archive' runner crashed. added
Updated by crameleon over 1 year ago
Is this still valid, now that gunicorn is in use?
Updated by pjessen over 1 year ago
crameleon wrote:
Is this still valid, now that gunicorn is in use?
As far as I can tell, uwsgi vs gunicorn does not affect the problem.
Actions