On 1/31/24 10:12, andrea.janna.unipd@gmail.com wrote:
From the database debug log I guess that mailman gatenews abruptly terminates the database connections. For instance this is the database debug log of a connection that doesn't trigger the mariadbd "[Warning] Aborted connection" log entry.
70759 Connect mailman3web@localhost on mailman3web using Socket 70759 Query SET sql_mode='STRICT_TRANS_TABLES'... 240131 18:54:34 70759 Quit
There is a "Quit" at the end. While the log entries of the connections that trigger the aborted connection warning (like the one I posted yesterday) do not have "Quit" at the end.
You could try the following in mailman shell
$ mailman shell
Welcome to the GNU Mailman shell
Use commit() to commit changes.
Use abort() to discard changes since the last commit.
Exit with ctrl+D does an implicit commit() but exit() does not.
>>> for mlist in getUtility(IListManager).mailing_lists:
... print(mlist.fqdn_listname)
...
(here should be a list of your mailing lists)
>>>
Does this produce the expected list of mailing lists and does it produce the error in the database debug log?
If it does produce the expected list of mailing lists and the error in the database debug log, I'd say this is some issue between SQLAlchemy and MariaDB, but it seems harmless.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan