Mark Sapiro wrote:
First check to ensure there are no files in Mailman's var/templates/
On 12/10/24 07:44, pdw@mythic-beasts.com wrote: directory that are not readable by the Mailman user. That can cause this issue.
Checked, and I've also tried removing all templates for the affected list.
After multiple restarts trying to get some debug information, the hard loop seems to have stopped recurring, and the messages are sat in the "shunt" queue. They've not been delivered to recipients, but they are in the hyperkitty archive. The shunted messages should have a SHUNTING entry with an exception and traceback in mailman.log. If there were files unreadable by Mailman in Mailman's var/templates/ directory and you have corrected that, you can move the shunted messages back to their original queue with mailman unshunt.
I've now found the SHUNT entries and the exceptions seem related to restarting mailman (see below) so that much makes sense.
unshunting does indeed restore them, but unfortunately they're now back in the looping state.
Paul
Shunting exception:
File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 179, in _one_iteration self._process_one_file(msg, msgdata) File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 278, in _process_one_file self.switchboard.enqueue(msg, msgdata) File "/usr/lib/python3/dist-packages/mailman/core/switchboard.py", line 122, in enqueue filebase = now + '+' + hashlib.sha1(hashfood).hexdigest() ^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3/dist-packages/mailman/core/runner.py", line 117, in signal_handler raise RunnerInterrupt mailman.interfaces.runner.RunnerInterrupt Dec 17 21:25:51 2024 (1039773) SHUNTING: 1734470750.961038+b6946081a6c85ed7c03d221af87b87463eaf68e1 Dec 17 21:25:51 2024 (1039773) out runner exiting.