[MM3-users] Re: Held messages: Long time waiating for response of the Mailman API

On 1/26/22 00:11, Stephan Krinetzki wrote:

After we enabled the "slow query log", we got in the postgresql database the following output:

 2022-01-25 12:49:41.538 CET [16126] LOG:  unexpected EOF on client connection with an open transaction
 2022-01-25 15:34:36.047 CET [16864] LOG:  duration: 30760.028 ms  statement: DELETE FROM pendedkeyvalue WHERE pendedkeyvalue.id = XXX
2022-01-25 15:34:36.047 CET [3900] LOG:  duration: 9372.471 ms  statement: DELETE FROM pendedkeyvalue WHERE pendedkeyvalue.id = XXX
2022-01-25 16:42:07.243 CET [3900] LOG:  unexpected EOF on client connection with an open transaction

Pretty sounds like a database problem?

The unexpected EOF is because the gunicorn worker timed out and was killed.

There are two DELETE FROM pendedkeyvalue WHERE pendedkeyvalue.id = XXX transactions because the first one timed out. These came from https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/app/moderator.p...

The accept action is processed and ultimately we get to https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/app/moderator.p... and that in turn is doing the DELETE at https://gitlab.com/mailman/mailman/-/blob/master/src/mailman/model/pending.p...

There must be some kind of database locking causing this, but I have no clue as to what it might be. If you haven't done so, I would stop all the mailman services and the database server and then start them again. I don't know if that would help, but it might.

sometimes the log (mailmansuite.log) show us this error

That too is from the gunicorn worker timing out and being killed.

-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan