I'm seeing similar messages in both our prod instance and the test instance I run on my desktop.
Production:
"2022-11-09T18:37:49.106105Z 19100868 [Note] Aborted connection 19100868 to db: 'mailman3_prod' user: 'mailman' host: '10.6.5.187' (Got an error reading communication packets)"
Test:
"2022-11-09 18:46:07 52 [Warning] Aborted connection 52 to db: 'mailman3_prod' user: 'mailman' host: '172.18.0.3' (Got an error reading communication packets)"
I had previously increased the default value for "max_allowed_packet" to 12MB in our production db. The test db has that set to 16MB by default. When we first set this up we were getting errors based on larger than average messages not making it into the database due to that setting. Once I bumped it up those problems were resolved.
Any thoughts on what could be causing these error messages? We run Mailman on a container so is it possible that its related to the Python environment somehow?
Thanks.
-- Dan