On 2/9/21 5:25 PM, Mark Sapiro wrote:

On 2/9/21 2:03 PM, Brian Carpenter wrote:

...

Is there a way to determine why a message keeps ending up in the shunt queue?

Look in mailman.log for the SHUNTING message and the traceback that immediately preceeds it.

Thanks Mark. The reason was:

Feb 09 16:40:11 2021 (2614) Uncaught runner exception: Multiple rows were found for one_or_none()

sqlalchemy.orm.exc.MultipleResultsFound: Multiple rows were found for one_or_none()

Feb 09 16:40:11 2021 (2614) SHUNTING: 1612906811.2642436+cd8e97a66b6d0c2b73c2adde71a4914108c3e673

I have no idea what that means.

--

Brian Carpenter Harmonylists.com Emwd.com

On 2/9/21 6:37 PM, Mark Sapiro wrote:

On 2/9/21 2:57 PM, Brian Carpenter wrote:

...

On 2/9/21 5:25 PM, Mark Sapiro wrote:

...

On 2/9/21 2:03 PM, Brian Carpenter wrote:

...

Is there a way to determine why a message keeps ending up in the shunt queue?

Look in mailman.log for the SHUNTING message and the traceback that immediately preceeds it.

Thanks Mark. The reason was:

Feb 09 16:40:11 2021 (2614) Uncaught runner exception: Multiple rows were found for one_or_none()

sqlalchemy.orm.exc.MultipleResultsFound: Multiple rows were found for one_or_none()

Feb 09 16:40:11 2021 (2614) SHUNTING: 1612906811.2642436+cd8e97a66b6d0c2b73c2adde71a4914108c3e673

I have no idea what that means.

See <https://lists.mailman3.org/archives/list/mailman-users@mailman3.org/thread/P...> and <https://gitlab.com/mailman/mailman/-/issues/657>

Thanks Mark, that fixed it. In my case the list had duplicate entries for all 4 archivers in the Mailman database.

-- Brian Carpenter Harmonylists.com Emwd.com