Are the messages getting stuck in the spool directory? Check the log in /opt/mailman/var/logs/mailman.log. You can also check the spool message with the command $ mailman qfile. It appears this issue can occur if there's insufficient memory. A quick solution is to just add more swap memory.[1]
If anything, you can always set up a cron job to periodically restart the mail services and databases, though this would be a hacky solution.
Hope this helps.
[1] https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/I... -- Kind regards, Mohamad
On Sat, Oct 22, 2022 at 1:17 PM Jeremy Newman jnewman@codeweavers.com wrote:
I tweaked a few mariadb settings, restarted the db, and restarted the mailman services. That seems to have kicked it into gear again. Nothing was lost, looks like things just got stuck.
-N
On 10/22/22 11:07 AM, Jeremy Newman wrote:
On 10/22/22 10:08 AM, Francois Gouget wrote:
The wine-gitlab mailing list archive shows no new message since last Tuesday (2022-10-18). Yet I did receive emails on that list since then.
https://www.winehq.org/mailman3/hyperkitty/list/wine-gitlab@winehq.org/
What's going on?
Don't know. Hyperkitty is not adding them to the archive. This new version of mailman is not making me very happy. I've tried rebuilding the search index a few times, but the script always crashes.
It seems to be affecting all the lists. I think it is because MariaDB is overloaded and timing out.
-N