[BUG] mailman_web cron tasks now take up to 20 min while it used to be a few seconds

Hi,

Tag/version of Container Images
0.5

Our mailman instance has been running a few private mailing lists with very little traffic since 2020. Suddenly a few days ago mailman_web cron tasks started to take from about 10min to 20min.

Important note
It seems this behavior started after I upgraded the host from Debian 12 (bookworm) to Debian 13 (trixie). But I fail to see how it is related. Any help to pin that down appreciated.

Excerpt from the 26/01/2026 logs:

Mon Jan 26 16:00:00 2026 - [uwsgi-cron] running "./manage.py runjobs minutely" (pid 10499)
Mon Jan 26 16:00:00 2026 - [uwsgi-cron] running "./manage.py runjobs quarter_hourly" (pid 10500)
Mon Jan 26 16:00:00 2026 - [uwsgi-cron] running "./manage.py runjobs hourly" (pid 10501)
[uwsgi-cron] command "./manage.py runjobs minutely" running with pid 10499 exited after 16 second(s)
[uwsgi-cron] command "./manage.py runjobs quarter_hourly" running with pid 10500 exited after 16 second(s)
[uwsgi-cron] command "./manage.py runjobs hourly" running with pid 10501 exited after 209 second(s)

Excerpt from today's logs:

Tue Feb  3 16:00:00 2026 - [uwsgi-cron] running "./manage.py runjobs minutely" (pid 836)
Tue Feb  3 16:00:00 2026 - [uwsgi-cron] running "./manage.py runjobs quarter_hourly" (pid 837)
Tue Feb  3 16:00:00 2026 - [uwsgi-cron] running "./manage.py runjobs hourly" (pid 838)
[uwsgi-cron] command "./manage.py runjobs quarter_hourly" running with pid 837 exited after 914 second(s)
Tue Feb  3 16:15:14 2026 - [uwsgi-cron] running "./manage.py runjobs quarter_hourly" (pid 839)
[uwsgi-cron] command "./manage.py runjobs minutely" running with pid 836 exited after 956 second(s)
[uwsgi-cron] command "./manage.py runjobs hourly" running with pid 838 exited after 1140 second(s)
[uwsgi-cron] command "./manage.py runjobs quarter_hourly" running with pid 839 exited after 556 second(s)

Start with the 0.5 container's manage.py runjobs minutely, quarter_hourly, and hourly entry points, using the provided uwsgi-cron logs to identify which tasks are slow. Compare behavior around the Debian 12 to Debian 13 host upgrade and determine the cause; done means the regression is explained and the cron tasks return to their expected runtime.