[fix] MySQL server has gone away in nextcloud #1065
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
[Warning] Aborted connection 110060 to db: 'nextcloud' user: 'nextcloud' host: 'localhost' (Got a packet bigger than 'max_allowed_packet' bytes)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The problem
Nextcloud fail due to mysql queries refused with those message in log:
Solution
Update
max_allowed_packetto the default value inside maraidb 10.3 (16M)See https://mariadb.com/kb/en/server-system-variables/#max_allowed_packet
PR Status
Ready
How to test
I don't know how to reproduce exactly the bug with nextcloud, i think it could be reproduced with image bigger than 1M inside user profil, but it's hypothetical.
Change max_allowed_packet has fixed the issue in my impacted ynh setup.