Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Containers make DB queries that trigger communication errors #690

Open
Encephala opened this issue Mar 10, 2024 · 2 comments
Open
Labels

Comments

@Encephala
Copy link
Contributor

Tag/version of Container Images
Choose from: 0.4.*

When having the mailman containers running (using just the mailman-core and mailman-web containers from the docker-compose- postorius.yml), our database keeps outputting the following errors:

2024-03-10 15:59:04 334 [Warning] Aborted connection 334 to db: 'mailman' user: 'mailman' host: '...' (Got an error reading communication packets)

Our database is the official mariadb image, tag 11.2.3-jammy.

This does not seem to be the direct cause of any issues in mailman, but it doesn't seem right either.
I ran into this SO post: https://dba.stackexchange.com/questions/19135/mysql-error-reading-communication-packets,
but the proposed solution of setting max_allowed_packet to a large value does not get rid of this problem.

@Encephala Encephala added the bug label Mar 10, 2024
@barats
Copy link

barats commented Jul 29, 2024

Same problem here.

I even tried to use PostgreSQL instead of MySQL, failed as well due to the same problem, Database Connection.

Is there any upgrade for this?

@barats
Copy link

barats commented Jul 29, 2024

Same problem here.

I even tried to use PostgreSQL instead of MySQL, failed as well due to the same problem, Database Connection.

Is there any upgrade for this?

I could provide more details, if it's needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants