Am 15.11.20 um 17:50 schrieb Stephen J. Turnbull:
That's good. Not the behavior, but the fact that it happens consistently in the same place. Didn't happen again. I would have expected that from a daily cron-job.
wrong script (not the one mentioned here) in cron job.
So that's fixed but the errors still happen, right? It happened just once after the fix. But then not again. The only interesting information from our point of view would be if it was happening *before* you updated, and if so, when it started. That might help to identify the particular code and what changed. But if that information isn't immediately available, don't worry about it, it's a minor data point that *might*, but might not, be useful at some point. Sadly I deleted the local mail file.
About the core logs:
Traceback (most recent call last): File "/opt/mailman/core/venv/lib/python3.6/site-packages/sqlalchemy/engine/result.py", line 779, in _getter getter = self._metadata._getter AttributeError: 'NoneType' object has no attribute '_getter'
[snip]
sqlalchemy.exc.ResourceClosedError: This result object does not return rows. It has been closed automatically. [15/Nov/2020:00:00:10 +0100] "GET /3.1/lists/<listid>@<listdomain>.de/config HTTP/1.1" 500 0 "-" "-"
This is weird. It seems like your list doesn't exist. :-( Well, it exists. I'm thinking of resource shortage. It's a 2 GB with several apps on it. One ist mailman3 consuming 600 MB, so the VM is always a little bit short on free RAM.