On 03/17/2017 03:59 AM, Anders Nilsson wrote:
I do have problems with some lists occasionally going into some kind of shunt mode, where alla mails sent to them gets shunted. In the Mailman log I get entries for each shunted email:
Mar 17 11:54:11 2017 (6217) Uncaught runner exception: Multiple rows were found for one_or_none()
...
File "/usr/lib/python3.4/site-packages/mailman/handlers/rfc_2369.py", line 70, in process archiver_set = IListArchiverSet(mlist)
mailman/handlers/rfc_2369.py is adding the List-* headers. Here it is looking up all the archivers that are enabled for this list.
...
File "/usr/lib/python3.4/site-packages/mailman/model/mailinglist.py", line 607, in __init__ ListArchiver.name == archiver_name).one_or_none()
and here we are in code that is trying to see if there are any system enabled archivers that are not already associated with this mailing list and if so, add them to the archivers enabled for this list.
The above is the last line of
exists = store.query(ListArchiver).filter(
ListArchiver.mailing_list == mailing_list,
ListArchiver.name == archiver_name).one_or_none()which is querying the archivers enabled for this list for the name of a system enabled archiver and expects to find at most one entry
File "/usr/lib64/python3.4/site-packages/sqlalchemy/orm/query.py", line 2733, in one_or_none "Multiple rows were found for one_or_none()")
but finds more than one.
sqlalchemy.orm.exc.MultipleResultsFound: Multiple rows were found for one_or_none() Mar 17 11:54:11 2017 (6217) SHUNTING: 1489748051.1949184+7a59df19c81493cb419306d620376efc0e381819
So the cause is there appear to be multiple database entries for this list and some archiver name, but I don't know how that can happen.
I have not seen this error.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan